Randy McMurchy wrote:
> Hi all,
>
> 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:
>
> 1. Copy trunk to a 6.2.0 tag
> 2. Copy trunk to a 6.2.1 branch
> 3. Make the appropriate edits in the 6.2.0 tag to reflect the changes
> from SVN-<Date> to 6.2.0 versioning
> 4. Render the book in HTML and install it on quantum
> 5. Render the book in PDF and install it on quantum
> 6. Make the appropriate messages on the BLFS web site to reflect the
> 6.2.0 release
> 7. Send out appropriate messages to the various mailing lists
> announcing the 6.2.0 release
> 8. After the 6.2.0 release, all changes will go to trunk, and all
> changes compatible with LFS-6.2 will be merged into the 6.2.1
> branch
>
> Of course, none of this really has anything to do with today's
> release of 6.2.0-rc1 which to me is nothing more than an svn copy
> from trunk to a 6.2.0-rc1 tag, and rendering the various formats
> of the book and installing them on quantum, updating the web site
> and sending out messages to the mailing lists.
>
> This message is more geared to the actual 6.2.0 release on 2/14.
>
> Please, anyone with experience or thoughts about the plan, jump
> in and provide your comments. Thanks.
>
That's not the way I'd do it. I looked for a checklist, but I couldn't
find it. Sorry. Here is what I'd do:
1. Update general.ent with the blfs-version as -rc1 (or would that be
-beta1. I wouldn't call it a -rc until all the current tickets for
6.2.0 are either fixed or moved to another milestone. ). It will be a
couple more days for me to get KDE in.
2. Make the *tag*:
svn copy svn://svn.linuxfromscratch.org/BLFS/trunk \
svn://svn.linuxfromscratch.org/BLFS/trunk/tags/BLFS-6.2.0-rc1 \
-m "Tagging 6.2.0-rc1"
We should not update a *tag*. Its just that, a snapshot of where we
were when the tag was made.
3. Render the html manually. I have a custom script on quantum called
render-blfs-book-6.1.sh that could be updated for 6.2 relatively easily.
I wouldn't bother to make a pdf for a -rc? release.
4. Update the web site.
5. Make an announcement on lfs-announce and other lists.
Continue to make changes on the trunk and repeat 1-5 for -rc2, -rc3, etc.
For final release, create a *branch* for 6.2.0 the same way and then
change the trunk blfs-version entity back to svn.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
