new release?

[alexmyczko]

Is there a plan to tag a new release? Ubuntu 22.04 LTS will release soon, and their archive sync deadline from Debian is around mid of Feb 2022...

[tueda]

Indeed, I think it is a good idea to consider a patch release 4.2.2 from the current code, if others are fine.

[alexmyczko]

what does it look like? 4 months left for a release. if you know you will not do one, i'd rather do an artifical master release called 4.2.1+git2022MMDD early, than late in case users report problems, please tell so.

that is already the case with https://packages.debian.org/search?keywords=form with the current stable, and experimental having a much newer one, never sent to sid (thus not moved to testing)

there's these optional metrics from users: https://qa.debian.org/popcon.php?package=form (they absolutely don't count distributions inheriting from debian (ubuntu, raspberry, devuan etc), and unfortunately we don't have any other metrics

[benruijl]

I want to release a new version this month. @tueda are there any issues that need to be resolved before the new release?

[vermaseren]

I have a number of things that should go in this new version. Unfortunately, on my new computer I did not get the git to go properly. I will try to solve that the coming few days. If I cannot I may need some help. It did not want to make proper connection with the github.

Jos

On 1 Nov 2022, at 16:31, Ben Ruijl @.***> wrote:

I want to release a new version this month. @tueda https://github.com/tueda are there any issues that need to be resolved before the new release?

— Reply to this email directly, view it on GitHub https://github.com/vermaseren/form/issues/404#issuecomment-1298709756, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABJPCESTKDDC6POQLRAA3J3WGEZVTANCNFSM5LOU3X2Q. You are receiving this because you are subscribed to this thread.

[tueda]

@benruijl At least, some easy stuff can be resolved, like #389. I think #400 is almost(?) resolved.

We may also use this occasion to enable/start GitHub Discussions, which would be the place where people can ask any questions more frankly (with the "Q & A" category). For this, the bottom lines in README should be updated.

[tueda]

I will fix #389: the last line of p.211 of the manual should be

-/+  d_(mu,mu)*g_(1,m1,m2,...,mj,mn)

instead of

-/+2*d_(mu,mu)*g_(1,m1,m2,...,mj,mn)

[tueda]

We have released v4.3.0. This is a minor release with some additional features and bug fixes. In this sense, it might be appropriate to call it version 4.2.2 (compared to what was done in v4.2.1). But 3 years and 9 months since the previous release are long enough to make us sentimental, so 4.3.0. :-)