Version 4.2.1?

[tueda]

More than a half year has passed after the release of version 4.2.0. Maybe it would be good to start to consider a possible next version slowly.

Questions are:

1. Do we need a bug-fix release 4.2.1? Or wait for 4.3?
2. For 4.2.1, should more fixes and some small additions be included? Which ones?

The current changes are summarized in https://github.com/vermaseren/form/wiki/Recent-ChangeLog, if I don't miss anything. It includes annoying gzip bugs and polynomial GCD bugs.

Ubuntu 18.04 LTS (Bionic Beaver) will appear on 26 April 2018 (and will be supported until April 2023), may be shipped with the FORM 4.2 (Sep 14 2017) anyway: https://packages.ubuntu.com/bionic/form.
(They dropped .0 of 4.2.0 from form -v.)

[jodavies]

If a version 4.2.1 is released, it could be useful to provide a SUBSUBVERSION_ preprocessor variable. One could use this to enforce a certain level of bug-fixing in a script.

[alexmyczko]

Early 2019, Debian will ship a new stable release, maybe it'd be great to have a new release short before of that for them to deliver?

[benruijl]

That sounds like a good idea!

[tueda]

I think even the current one (+ possibly some bugfixes + extra) would be OK for 4.2.1 or 4.3.0, once Jos is satisfied with the version. Here is the list of changes from 4.2: https://github.com/vermaseren/form/wiki/Recent-ChangeLog.

[vermaseren]

Would a date in early Januari be fine, or is there more of a hurry. Potentially we might get in the namespaces in that case. Some of the outstanding bugfixes are rather hard, but I can try. Version 4.3.0 would be fine. Specially if we get the namespaces. Jos

…

On 8 Nov 2018, at 20:03, Takahiro Ueda ***@***.***> wrote: I think even the current one (+ possibly some bugfixes + extra) would be OK for 4.2.1 or 4.3.0, once Jos is satisfied with the version. Here is the changes from 4.2: https://github.com/vermaseren/form/wiki/Recent-ChangeLog <https://github.com/vermaseren/form/wiki/Recent-ChangeLog>. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#263 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFLxElYYvKTc1Gb_gNx7MUsjZLcO1ol9ks5utA-RgaJpZM4R_zm7>.

[alexmyczko]

Summary from https://release.debian.org/buster/freeze_policy.html
2019-01-12 - Transition freeze
2019-02-12 - Soft-freeze
2019-03-12 - Full-freeze

I'd go for earlier so some people can already test it, it takes 5 days from unstable to wander into testing (which will become stable after the freeze)

[alexmyczko]

any news here? happy new year! GREAT!

so looking forward for

1. the new release
2. examples
3. benchmarks with gcc, tcc (interpreted, built-at-run-time), clang (maybe icc)
4. tests with/without zram

[benruijl]

Form 4.2.1 has been released!

[tueda]

You failed. The build script can't recognize the version because it must be v4.2.1; I think the configure script still says FORM 4.2.0 in your build (you need to rerun autoreconf -ifv). See:
https://github.com/vermaseren/form/blob/eaf85a757a9f7bb69c9bdc4bf6ec07e48f5769ac/scripts/git-version-gen.sh#L99-L103
Another problem was the Github token to deploy files to the release page was somehow expired(?) I don't remember whose token was used, but for now I put my token. Can you put the correct tag and remake the release?

Maybe copyrights should be updated (to 2019), but this is a minor release and we may skip it...

[tueda]

By the way, why do you spell Form instead of FORM while you spell reFORM for your software :-)

[tueda]

Another thing: are we happy to have "undocumented" changes documented in the release notes?

[benruijl]

Ah yes, you are totally right. I should push a version bump and then move the tag. I can do that tomorrow. For now, I've tagged the release as a pre-release.

Maybe we can move the undocumented change out of the release notes and just keep it in the global changelog that you made.

[tueda]

Thanks! Now the tarball gives

FORM 4.2.1 (Nov 21 2018, v4.2.1) 64-bits         Run: Mon Feb  4 21:45:30 2019

Ben, can you also update the AUR package? I will update the Homebrew one and the installation page.

[tueda]

For undocumented changes, yes, we could just keep them in the change log, and they would be officially not supported in 4.2.1. But for the setup parameters, now the manual is wrong...

[benruijl]

Yes that is unfortunate... I don't know what the best course of action is. In the future we should document in the same commit.