need for release?

Boriss Mejias boris.mejias at uclouvain.be
Tue Feb 5 00:14:45 CET 2008


Pavel wrote:
> Considering the number of fixes maybe a 1.3.2.1 is more appropriate than 
> 1.3.3?

Since we don't release often enough, I don't see the benefit of having a forth 
number. The third number is for minor releases: bug fixes, and maybe a few new 
features. The second one is for mayor releases, meaning that there is no 
backward compatibility guaranteed. First name would mean a complete new 
implementation... meaning I don't think we will ever have a version 2.0...

cheers
Boriss

> /pavel
> 
> On Mon, 28 Jan 2008 10:15:42 +0100, Boriss Mejias 
> <boris.mejias at uclouvain.be> wrote:
> 
>> Dear Hackers,
>>
>> We had a discussion here at UCL about future releases of Mozart, and 
>> we would
>> like to have your opinion in order to take some decisions.
>>
>> First, there are two main projects that will produces releases 1.4.0 and
>> 1.5.0. These are MozDSS and GeOz. The numbers will depend on which one
>> releases first.
>>
>> But, since we haven't released since July 2006 (version 1.3.2), we 
>> wonder if
>> it is worthy to release 1.3.3 before MozDSS and-or GeOz. The point is 
>> that no
>> major bug fixes has been added to the 1-3-0-fixes branch, but here 
>> there are
>> some reasons in favour of doing the release:
>>
>> - There is now support for windoze Vista. This is a very small fix 
>> that is
>> already included in a new 1.3.2 installer for windowze, but it would 
>> be good
>> to uniform the packages.
>> - The small fix in the oz script that calls the emulator, and that 
>> concerns
>> spaces in files names, seems to have fixed an annoying bug for some time.
>> - The was an issue concerning the default behaviour of the OPI, where
>> different threads where launched with every "declare" statement. This fix
>> might be interesting mainly for students.
>> - A 1.3.3 release would be a would opportunity to close the 
>> 1-3-0-fixes branch
>> - Releasing is good to show that the community is still working on 
>> Mozart/Oz
>> - Having a deadline for a release may force us to try to fix some 
>> extra-small bugs
>>
>> The strongest argument against the release would be that the amount of 
>> fixes
>> is very small, and it might be enough to not release, but I'm not sure of
>> that. This is why I would like to discuss this in order to take a 
>> decision.
>>
>> Best,
>> Boriss
>>
>>
>>
>>
> 
> 
> 


More information about the mozart-hackers mailing list