Randy McMurchy wrote: > 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.*
My script on quantum does that. > 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.* My script does that too. > * 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. They point to the same place now via a symbolic link: blfs/downloads/svn -> ../../patches/blfs/svn It came about as the automation of the patches was implemented. We could change the book. The only place the downloads-root entity is used is one place in general.ent. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
