[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Octave 5.2.0 release

From: Kai Torben Ohlhus
Subject: Re: Octave 5.2.0 release
Date: Wed, 15 Jan 2020 00:22:59 +0900
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.3.0

On 1/15/20 12:01 AM, John W. Eaton wrote:
> On 1/14/20 8:31 AM, Kai Torben Ohlhus wrote:
>> On 12/12/19 11:43 PM, John W. Eaton wrote:
>>> On 12/12/19 8:38 AM, Kai Torben Ohlhus wrote:
>>>> By "release candidate" you mean 5.1.90 before 5.2.0?
>>> Yes, I think it makes sense to do that even for a stable bug-fixing
>>> release as a final check that "make dist" and the Windows builds work as
>>> expected.
>>> jwe
>> jwe and all,
>> currently I am uploading fresh builds of the stable branch 5.1.90,
>> including all 3x3 flavors of MXE and build logs to
>>     https://octave.space/stable_56dd7419d7aa/
>> This might take some time, but the most important ones
>>     octave-5.1.90-w64-*
>> are already there.  Was it possible to publish that release on
>>     https://alpha.gnu.org/gnu/octave/  ?
>> I would be happy to announce a final regression test period from January
>> 15 to 31 followed by a minor Octave 5.2.0 release, if no bad regressions
>> were discovered in that time.  Then all focus goes back to Octave 6.
>> A final note about the year 2020 change:  Basically, on Octave 5.2.0
>> there was no development in 2020.  Thus we might skip touching all
>> headers and just adapt the date in the most important places indicating
>> the year of the 5.2.0 release.
> It looks like in the past we only uploaded the w64 build to
> alpha.gnu.org, not the w32 or w64-64 builds.  Do you think all are
> needed there?
> For 5.1.0 on ftp.gnu.org we did upload all w32, w64,
> and w64-64 in installer exe, zip, and 7z formats.
> jwe

Maybe for alpha the w64 version is enough.  For the remaining versions,
one can consult https://octave.space/stable_56dd7419d7aa/.

I think especially the source tarball should be located at this more
official location.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]