|
From: | Richard Frith-Macdonald |
Subject: | Re: GNUstep base version number |
Date: | Mon, 24 Nov 2008 22:34:39 +0000 |
On 23 Nov 2008, at 12:03, Fred Kiefer wrote:
Perhaps that sentence was buried down to low in my last mail: Fred Kiefer wrote:Looks like somebody downgraded GNUstep base from 1.17 to 1.15.4. Was this done on purpose?
I temporarily took it back to 1.15.4 to make a release on the unstable branch because we just haven't done the development work to produce a new unstable branch yet (ie the big, breaking binary compatibility significantly, changes listed as 'to do' in the 1.15.3 release haven't been done :-( ). We're working towards a 1.17.0 release again now ... I'd really like it if people contributed what we need to go into that release.
This unexpected release number change is causing problems to everbody compiling GNUstep from SVN trunk. Of course it is always best torecompile everything at once, but at least somebody could have send outa warning that this was needed. Perhaps we really should redefine the release number handling in GNUstep. As I see it, we did not use release number according to our definition on the wiki for the last releases. There was no unstable release for gui/back and for base we just used an unstable releasenumber 1.15 and treated it as a stable one, while bumping up the releasenumber for the next unstable release to 1.17, but never doing the 1.16 stable and now even skipping the 1.17 release.
Not sure what you mean here ... with base the latest stable release is 1.16.5 and the latest unstable release is 1.15.4 (ie still on the 1.15 branch) because we haven't moved to a new branch yet.
[Prev in Thread] | Current Thread | [Next in Thread] |