Randy McMurchy wrote these words on 01/31/07 18:56 CST: > Not having done a BLFS release before, and there appears to be no > information in the Editor's Guide or elsewhere (I realize Bruce > has a personal checklist), I'm sort of winging it as I go. Because > the 6.2.0 release will be (hopefully) updated to a 6.2.1 release, > I'm thinking the best way to go is as follows:
I've realized that there are a few other minor details required. Justin's help is critical. 1) Justin needs to create and populate a 6.2.0 version on the master package server. I'll use this for all the rc-1 versions as well. It may mean duplicate updates for Justin for the next couple of weeks, but since there's package freeze, perhaps there won't be anything for Justin to do other than create the 6.2.0 dir structure and populate it one time. 2) Need to populate a 6.2.0 patches repo on quantum.* 3) Need to create an Errata page (even if it is empty, we need the placeholder). 4) Need to create the "Download" area for 6.2.0.* * I need to look and see why we have separate "download" and "patches" directories identified in general.ent and see if they can't be consolidated. I didn't look, but I remember the "download" area contains the patches, so why do we need a separate (and redundant) place for the patches. -- Randy rmlscsi: [bogomips 1003.26] [GNU ld version 2.16.1] [gcc (GCC) 4.0.3] [GNU C Library stable release version 2.3.6] [Linux 2.6.14.3 i686] 20:29:00 up 21 days, 20:43, 1 user, load average: 0.01, 0.04, 0.05 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
