Re: [Maxima-discuss] Maxima 5.38.0

[Wolfgang D. <wol...@da...>]

On 2016-03-31 07:50, Gunter Königsmann wrote:
> Since wxMaxima tries to make a simultaneous release with maxima and
> the windows installer (including both programs) usually is released
> only hours after the release takes part I have added a paragraph to 
> README.developers-howto asking for information about a date by which 
> we should have released the new code.

Dear Viktor, dear Maxima & wxMaxima-Team,

thank you very much for taking over the task - and for pre-announcing
the release.

Concerning the order of releases: I would find it better, if a wxMaxima
release would be made *before* a Maxima relase. (Reason: in
crosscompile-windows/CMakeLists.txt I set the used software versions -
e.g. "set(WXMAXIMAVERSION  15.08.2)" - and if the wxMaxima release is
done after the Maxima release, I have to modify the source to
crosscompile a Windows installer.
If someone would like to crosscompile it from the *released* Maxima
source, he would get a installer with an older wxMaxima version.


And concerning the creation of tarballs with "make dist-gzip":
sometimes files in the git repo did not get included, because they were
missing somewhere in the autoconf build system.
Git can also create tarballs, perhaps the following procedure should be
used instead of a "make dist-gzip"?

V=5.38
# create a changelog, update the list of contributors,
# tag the release, be sure to push your changes
# (and the new tag!) to the server!
git archive --format=tar --prefix=maxima-$V/
--remote=git://git.code.sf.net/p/maxima/code $V | tar xf -
cd maxima-$V
./bootstrap
cd ..
tar czf maxima-$V.tar.gz maxima-$V
rm -rf maxima-$V

That would create a tarball from the git tag $V (and create the required
./configure).

Best regards, Wolfgang