Ken Moffat wrote:
> On Tue, Jun 26, 2012 at 04:02:05PM -0500, Bruce Dubbs wrote:
>> The only caveat is to consider the release plan. Right now, I'd
>> like to release a coordinated LFS/BLFS on 1 September. That means a
>> package freeze and an -rc1 for both about 1 August or slightly over one
>> month from now.
>>
>
> Someone might also want to think about some of the items at the
> bottom of longindex.html, Some of what is in section g ('Others')
> is reasonable, some doesn't necessarily belong there. Not sure if
> everything in the preceding Bootscripts section belongs there -
> maybe it all does! Certainly the subsequent 'L' and 'O' headings
> look as if their contents are in the wrong places. Indexing is
> easily broken ;)
Yes, the index entries are tedious, especially for a new package with
lots of items. That's one reason I think a whole month is needed. Even
that may not be enough.
There's a lot of things that could be done at that time like moving
packages to different sections, reviewing especially the Preface and the
first three chapters which have a lot of text, etc.
> If I'm around and not doing anything else after the package freeze,
> you could ping me - I suspect most editors don't really care about
> longindex. I tend to use it a lot, and have just been looking at
> it for some things I plan to (re)propose shortly.
>
> Beyond that, are we supposed to start tagging packages for 7.2 once
> the freeze starts ? If so, what happens if anything in LFS has to
> be revised during the -rc ?
If we freeze LFS, then I think we can mark BLFS with an entity like
&lfs_72_checked; and have it display -rc1 while we are in freeze and
then at release just change the definition.
I suspect that packages that must be changed during freeze would only be
due to bugs or security issues, not enhancements. Generally, if a
package is major.minor.patch and only the patch level changes, updating
does not affect other packages.
One thing to note is that my release proposal is just that, a proposal.
I'd like to get some agreement this is the right thing to do and the
approach is reasonable.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
