On Mar 16, 2005, at 3:03 AM, Stefan Urbanek wrote:

Hi,

What are the plans for the next GNUstep -bas and -gui releases?

Is it possible to make minor releases more often and to publish plans/todos for
next major and minor releases?


Moreover, can people who make releases describe the whole process on the new
wiki so others delegated developers can make the releases when official release
manager can not?



My plan so far:

binary compatible releases (by the end of March)
base 1.10.2 (based on CVS from Feb 22 2005)
gui 0.9.5
back 0.9.5

Actually, I'm ahead of things so I could make these releases even sooner if there is general interest.

binary incompatible release (a few weeks or month later):
base 1.11.0
gui 0.10.0
back 0.10.0

Really, the hard part is not 'making' the release. That's quite easy and almost fun. The part I really want help with is having people who know each library well to act as library managers - make up a list of release criteria and tell me when a good time to make a release is. GNUstep is to big and too much work for me to do this all by myself.

Steps for releasing the GNUstep core libraries (as well as others)

1. Make sure news.texi and ReleaseNotes.gsdoc files are updated
2. Update the 'Version' file with the new version
3. Update the documentation and release notes in the main directory:

        cd Documentation
        make clean; make; make regenerate

4. Commit the changed files (add a line in the ChangeLog, like
        '* Version 1.10.0' as well).

5. Tag the release

        make cvs-tag

6. Make a source distribution

        make cvs-dist

7. Administrative stuff (scripts that I use to make this easier are in
   brackets):
        Make RPMS or whatever [gstep-distribute]
        Sign the packages [gstep-sign]
        Upload packages to ftp.gnustep.org [gstep-update, gstep-upload]
        Install the documentation and copy it to the web repository
                [update_documentation]
        Update the index.html and resources/downloads.php pages with the news.
        Commit the web repository.
        Make an announcement on info-gnustep@gnu.org, etc


gstep-distribute, gstep-update: must be run as root/sudo

_______________________________________________
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Reply via email to