Future 6.x release schedule?
Glad 6.3 is out, and I notice there are approximately more than 60 patches get into 6.3 release. Though I don't know how many of these fixed issues are critical, it raises the question to me that do we want to review release schedule for 6.x? I know it's been discussed before, but can we reconsider it, especially given that 7.x release is pushed out to maybe mid 2009? If my understanding is correct, current policy or practice on old rev release is not until a security bug surfaces. It works okay when release cycles are relatively short (I think 5.0 was release 10.5 months after 4.7). But sometimes, I still, guilty as it is, can't wait to see some security bugs are found, not only because drupal is safer but more to the fact that other critical patches get a chance to get into the official release. But even so, without a release schedule, it's sort of hard to plan my time or soliciting help on certain critical 6.x issues. So what do you think if we have some sort of flexible but known schedule for future 6.x release, by either set a tentative target date, like Nov 1th or every 4-6 months or when critical bug fixes have accumulated to a certain number, then 6.4 will be released?
In this particular case many people will be happy about the release, because the latest release candidates of views 2 and cck 2 do not work with Drupal 6.2. But I don't think it makes any sense to have a schedule for bug fix releases. This would somehow implicate that you know in advance when critical bugs get detected.
Glad 6.3 is out, and I notice there are approximately more than 60 patches get into 6.3 release. --
Ramiro Gómez Software-Entwickler und IT-Berater mit den Schwerpunkten Content-Management-Systeme, SEO und Open Source. ------------------------------------------------------------ Software developer with focus on content management systems, SEO, and open source. E-Mail: web@ramiro.org Phone: +49-30-46065288 (Berlin, Germany) Websites: www.ramiro.org www.seo-expert-blog.com www.torlaune.de
On Thu, 10 Jul 2008 22:35:18 +0200 Ramiro Gómez <web@ramiro.org> wrote:
In this particular case many people will be happy about the release, because the latest release candidates of views 2 and cck 2 do not work with Drupal 6.2. But I don't think it makes any sense to have a schedule for bug fix releases. This would somehow implicate that you know in advance when critical bugs get detected.
http://en.wikipedia.org/wiki/Patch_Tuesday#Exploit_Wednesday The "Exploit Wednesday" theory is questionable. If it is true that good sysadmin (shops with more resources) will patch ASAP, it is equally true that good cracker will exploit a vulnerability ASAP. On the other side shop with less resources will find easier to know when a patch will be available (preferably not on Saturday night[1]) On the down side a weakness may stay on the wild longer if you wait the scheduled release of patches. I think avoiding to release patches at Saturday or during important holidays, but still ASAP, should be enough to make every respectable shop happy. After all even if some people may deserve it, no one will really enjoy an army of p0wned Drupal sites... or even if they were not Drupal... an army of cracked sites is not going to make any good to anyone, unless you enjoy spam. [1] somewhere in the world will always be night, but at least you could avoid Saturday. -- Ivan Sergio Borgonovo http://www.webthatworks.it
On Thu, 10 Jul 2008 23:49:15 +0200, Ivan Sergio Borgonovo <mail@webthatworks.it> wrote:
On Thu, 10 Jul 2008 22:35:18 +0200 Ramiro Gómez <web@ramiro.org> wrote:
http://en.wikipedia.org/wiki/Patch_Tuesday#Exploit_Wednesday [snip] I think avoiding to release patches at Saturday or during important holidays, but still ASAP, should be enough to make every respectable shop happy.. [snip] [1] somewhere in the world will always be night, but at least you could avoid Saturday.
I'm sure we are going off on a tangent here. However, scheduled security releases are on Wednesdays only. Regards, Heine Deelstra -- http://heine.familiedeelstra.com/about
On Jul 10, 2008, at 1:10 PM, Jim Li wrote:
But even so, without a release schedule, it's sort of hard to plan my time or soliciting help on certain critical 6.x issues.
I would have to recommend that if you are aware of critical issues in Drupal 6 that the time to fix, or help is always now. An issue won't take more time to fix now or later, and it does help people that follow 6.x-dev. I have always wondered if when a branch is closed out, such as 5 will be when Drupal 7 is released, if a final release will be made made wrapping up any unreleased commits to that branch. For a while I assumed that would be the case, but I realized that I've never found that documented anywhere. -Mike _________________ Michael Prasuhn mike@mikeyp.net http://mikeyp.net
participants (5)
-
Heine Deelstra -
Ivan Sergio Borgonovo -
Jim Li -
Michael Prasuhn -
Ramiro Gómez