Fernando de Oliveira wrote:
On 03-08-2014 14:16, Bruce Dubbs wrote:
We need to do some planning for the upcoming release. Right now all
books are looking pretty good.
I would like to plan a coordinated release of LFS and BLFS for both
trunk and systemd on September 1. In preparation, we will need to do a
package freeze on August 15. At that time, we will release a -rc1 for
the both lfs versions.
After that, any updates to package versions in either lfs or blfs will
need to be coordinated on the respective mailing list. For blfs, I'll
add a new entity
"<para>This package is known to build and work
properly using an LFS-7.6 platform.</para>"
And ask all editors to methodically work through blfs to check all the
packages. As the packages are checked, we can update each section.
I didn't understand this sentence. Packages in one section deponds on
packages on other section.
Basically, the same as last time.
The August 15 date may slip. I am anticipating a new release of glibc
any time now and would like to get it into the books, but we won't know
the actual release date until it happens. I also anticipate version
3.16 of the kernel by that date, but I don't see that version as critical.
I have asked this before. I would like to have an rc1 for BLFS, so
packages could be updated in svn, during the freeze time of BLFS-rc1. It
took more than a month of intense work to catch up the lost time, for
7.5 release (IIRC).
I could do this, but it means that packages need to be updated in both
-rc1 and trunk. That is, if we mark a package that is tested for 7.6 in
-rc1, then we need to do it in svn too. Is that what would like to do?
Typically -rc releases don't change.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
