Randy McMurchy wrote these words on 10/21/06 12:45 CST: > I'd like to consider changing many of the Trac system tickets to post-6.2 > status so that we can concentrate on getting a release candidate out.
Using this thread as the BLFS 6.2 release notes thread, as the 'Subject' seems to fit. This release candidate mentioned above is the prelude to the new BLFS version to match the LFS-6.2 release. What should the new BLFS version be named? I'm leaning to 6.2.0. Here's why: I don't know how to increment from 6.2 and still be within the LFS-6.2 structure. BLFS-6.2.1 makes no sense if there wasn't a 6.2.0 version. And 6.21 is no good. BLFS-6.3 is risky as LFS trunk has now changed enough that there seems to be incompatibilities between trunk versions. Therefore, BLFS couldn't release a 6.3 until LFS does, and the LFS version will be incompatible. What else would be left? I'm mentioning this now because this release is going to have *many* packages at release levels less than the current production versions. I anticipate another release about two-three months after the upcoming release, with updated versions of packages, and not much else. Right now BLFS is in a bit of a stagnant point. I can't promise without new blood, we can commit to doing much. I'd like to think we can get a release candidate out by the end of the month, and a full release 2-3 weeks later. After that, I can commit to many package updates using the same LFS-6.2 based system. With some other Editor help (we may have additional help soon), we should be able to get most of the package updates tested. Then we can release an update to the BLFS-6.2 that should carry us for a while as the "stable" version matching stable LFS. Such as the "stable" BLFS-6.1 (gosh, how old that is now), is carrying us. Meanwhile, I'm going to create a branch for the release candidate and keep it current with trunk. All updates should be made to trunk until we actually cut a 6.2.0 release candidate. At the point we cut a branch, trunk can take off towards compatibility with current LFS trunk. I will ensure that the 6.2.x branch is updated with stuff put into trunk. Almost always, a package update to trunk can be backported into a 6.2.x branch. Comments are welcome. -- Randy rmlscsi: [bogomips 1003.25] [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:58:00 up 26 days, 5:56, 1 user, load average: 0.03, 0.09, 0.06 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
