You've probably noticed the change it NetBeans 6.5 schedule already, right? However for those that haven't let me cite Jirka Kovalsky (NetBeans Technical Community Manager ).
Hello developers,
based on the current quality dashboard and feedback from community, a change to the NetBeans 6.5 release schedule [1] has been made. We went through all problematic areas and investigated how much time is needed to meet the FCS quality and according to our findings 4 more weeks will be required.
This in particular means that Code Freeze moves to October 13th and FCS to November 12th.
[1] http://wiki.netbeans.org/NB65Milestones
It is not easy to postpone the release date but we simply want to address recent community feedback coming for example via this mailing list or via bugs that were submitted at high rate of ~400 issues weekly.
However, we believe it will pay off in the end because quality is also a feature, isn't it? :-)
Thanks for your understanding and support!
And we all believe that it will help to release NetBeans 6.5 as more stable product. I will not repeat myself - listen to podcast ;)
Hello developers,
based on the current quality dashboard and feedback from community, a change to the NetBeans 6.5 release schedule [1] has been made. We went through all problematic areas and investigated how much time is needed to meet the FCS quality and according to our findings 4 more weeks will be required.
This in particular means that Code Freeze moves to October 13th and FCS to November 12th.
[1] http://wiki.netbeans.org/NB65Milestones
It is not easy to postpone the release date but we simply want to address recent community feedback coming for example via this mailing list or via bugs that were submitted at high rate of ~400 issues weekly.
However, we believe it will pay off in the end because quality is also a feature, isn't it? :-)
Thanks for your understanding and support!
And we all believe that it will help to release NetBeans 6.5 as more stable product. I will not repeat myself - listen to podcast ;)
Hi,
Yes by all means ship when it's done and not by some arbitrary deadline.
The latest Netbeans versions have been great to use and I look forward to many many hours of work using Netbeans 6.5
Thanks to all involved!
Posted by Barry on September 25, 2008 at 01:36 PM CEST #
I @Barry: I agree. Planning is a hard task. However there have to be a deadline (otherwise you would never release ;) )
Posted by Lukas on September 25, 2008 at 01:47 PM CEST #
Most developers have probably been in the position of having to release things before they're really ready. Those who have realize that it takes courage to miss a deadline when all the features are there but you recognize that improvements are needed. Furthermore, it takes consideration and respect for the people who use the product.
In a few months' time, people will have forgotten the date on which 6.5 was released but they will think about the quality of that release every day they use it.
Posted by Tom Wheeler on September 25, 2008 at 05:21 PM CEST #
Yes, moving the release date is definitely a good move.
But how about a second beta before RC1? The first beta is rather old and has tons of bugs that have been fixed.
Posted by mass on September 25, 2008 at 05:50 PM CEST #
@Tom: WOW, this is the nicest comment I've heard about a slip (ever).
@mass: There won't be any more Beta. The RC1 that should be available soon after Code Freeze. The main reason that there is no other Beta is that the slip wasn't planned at all. It isn't as easy to produce a Beta - it requires additional testing, bugfixing, cloning, branding, uploading, promoting, etc. The daily builds should be pretty stable these day (but you never know :( ). Please, wait for the RC1.
Posted by Lukas on September 25, 2008 at 05:55 PM CEST #