I agree it would be good to document it. Basically it's: 1) Update configure.in with the version # 2) Make sure make distcheck works 3) Commit; tag; then run distcheck (again) (note that for 2.3.x we only tag; no branch) 4) Upload tarball; commit htdocs NEWS entry.
I highly suggest creating the release schedule ahead of time. Say, a release every 2-3 weeks for the 2.3.x series with a proposed date for the 2.4.0 release. -derek Christian Stimming <[email protected]> writes: > I think at some point andi5 had compiled such a list, but I can't find it > anywhere. Documenting this in the wiki is most probably a very good idea. > > Christian > > Am Montag, 27. April 2009 21:51 schrieb Phil Longstaff: >> Is there a checklist anywhere of steps on how to perform various types of >> releases (unstable e.g. 2.3.0, stable e.g. 2.4.0, maintenance e.g. 2.4.1)? >> If not, I'll document on the wiki as I go. >> >> >> >> ________________________________ >> From: Christian Stimming <[email protected]> >> To: [email protected] >> Cc: Phil Longstaff <[email protected]> >> Sent: Monday, April 27, 2009 3:48:35 PM >> Subject: Re: 2.3.0 >> >> Am Montag, 27. April 2009 15:21 schrieb Phil Longstaff: >> > Other than coming up with a catchy name for the release, is there >> > anything in the way of me creating current trunk tarballs and releasing >> > them as 2.3.0? >> >> No, not really. However, I (as a translator) would appreciate an advance >> notice of about 5-10 days before the actual release date... maybe you can >> add your intended / proposed dates on >> http://wiki.gnucash.org/wiki/Release_Schedule >> >> Other than that, we would need to come up with a list of issue which are >> not (yet) working, and decide whether those need to be disabled or fixed. >> But this is something we can decide during the 2.3.x unstable releases, >> before we're heading towards a 2.4.0. So no, this is not in the way of >> 2.3.0. You can go right ahead! Thanks a lot! >> >> Regards, >> >> Christian > _______________________________________________ > gnucash-devel mailing list > [email protected] > https://lists.gnucash.org/mailman/listinfo/gnucash-devel > > -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH [email protected] PGP key available _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
