Addressing the current release problem
| Newsgroups | gmane.linux.lfs.beyond.devel,gmane.linux.lfs.devel |
|---|---|
| Message-ID | <[email protected]> |
First of all I want to thank everyone for their replies and suggestions about how to handle the current LFS/BLFS problems. Overall I think the majority are in favor of doing an lfs-12.3-rc2 release and retesting BLFS. That's something that I do not want to do, but I also think we do *need* to do it. The issues of the stable book being able to reasonably handle upgrades is important. Right now issues with the kernel, systemd, and other packages such as libxml2 are too complex. I do not want to release "stable" books and say, "By the way, you need the upgrade these packages for security reasons." on the day after the release. To this end I have built a new version of LFS with all the current LFS tickets incorporated. I will be releasing that as lfs-12.3-rc2 in the next few hours. After that I will revert all the lfs123 tags in BLFS to lfs122 and restart the tagging process. From experience, the second round of tagging goes faster than the first. I am hoping that we will be able to do the stable release by March 5th. -- Bruce -- http://lists.linuxfromscratch.org/sympa/info/blfs-dev Unsubscribe: See the above information page