On Fri, 25 Apr 2008, Akim Demaille wrote: > > Perhaps we can go ahead and start figuring this out, and Paul can chime in > > if he has time. Looking back at the 2.3a release, I gather that this is > > what needs to be done: > > > 1. Change 2.3a+ to 2.3b in NEWS and configure.ac, and set the release date > > in NEWS. > > > 2. make dist, get someone to generate a sig, and then post the tarball and > > sig to: > > > ftp://alpha.gnu.org/gnu/bison/ > > I don't remember either :( If he has some time, maybe Alexandre can > help here, he ran the procedure more recently than I did. I had a > quick look on Savannah.gnu.org, but I found nothing.
I found this: http://www.gnu.org/prep/maintain/maintain.html#Automated-FTP-Uploads My guess is that I am not in the list of people authorized to upload Bison releases. Might you be? > > 3. Send a message similar to: > > > http://lists.gnu.org/archive/html/bug-bison/2006-09/msg00012.html > > > to these lists: [EMAIL PROTECTED], [EMAIL PROTECTED], > > bison-patches@gnu.org, [EMAIL PROTECTED] > > > Sound right to you? > > Yes, perfect! Thanks for looking it over. > Have a close look at Makefile.maint, it contains quite some targets to > help releases. "make beta". I don't know how rusty this is :( It breaks for me. "make beta" seems to be about the same as "make alpha". Here's a message from Paul Eggert saying "make alpha" is not maintained: http://lists.gnu.org/archive/html/bison-patches/2006-12/msg00095.html I see no significant changes to Makefile.maint mentioned by cvs log since then.
