Bruce Dubbs wrote these words on 01/20/07 19:22 CST: > This is a bit aggressive for me. KDE-3.5.6 is due to be released on Jan > 23. There is no way I can get it into the book by Jan 24.
I already thought about that after I reviewed the original thread, and discovered that KDE is not due out until the 23rd. However, I have no problem releasing an alpha tarball that doesn't include the KDE update. I'm not sure that anyone could even properly test KDE (or provide meaningful input) in the one week of the alpha release anyway. > If you don't > mind delaying that package until after the alpha, its OK with me. Yes, this is the way we'd have to do it. I have no issues with this. Your build and test (of a very mature KDE-3.x version) should be adequate (and fully trusted) for the beta release. > I > could do koffice-1.6.1 now, but I really want to do that after I > installed KDE-3.5.6. I can commit to having all four of my tickets > completed by Jan 31. Good enough. Thanks for the commitment to this Bruce, it is appreciated. > BTW, the way I would do the release is to just tag the trunk for the > alpha/beta releases and then cut a branch for the full release. Then > changes could be made to the branch and trunk independently. Yes, exactly what I had in mind. Tag the alpha and beta versions, cut a branch for the 6.2.0 version and drive on. The only issue being that we will need to release a 6.2.1 version of BLFS ASAP. This version must still be compatible with LFS-6.2 and not necessarily LFS-SVN. This may mean that merging to the 6.2.0 branch will be selective. I am not in touch with LFS-SVN enough at the moment to provide any sort of positive comment on any possible incompatibilities. Other thoughts? -- Randy rmlscsi: [bogomips 1003.26] [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] 19:29:00 up 10 days, 19:43, 1 user, load average: 0.05, 0.32, 0.61 -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
