Hello, as mentioned earlier, I intend to package up CVS HEAD later this week (after today's bugfix party). The question is: should this be 'beta 4' or 'RC 1' (or 'RC' tout court)? I'm asking because some people approached me saying we should call it a RC. For fun's sake, I figured I'd ask you first before sharing my own opinion. When you answer, please provide some insight as why you think it should be 'beta 4' or 'RC 1' or 'RC'. No brainless answers please. Thanks! -- Dries Buytaert :: http://buytaert.net/
as mentioned earlier, I intend to package up CVS HEAD later this week (after today's bugfix party). The question is: should this be 'beta 4' or 'RC 1' (or 'RC' tout court)? I'm asking because some people approached me saying we should call it a RC. For fun's sake, I figured I'd ask you first before sharing my own opinion. When you answer, please provide some insight as why you think it should be 'beta 4' or 'RC 1' or 'RC'. No brainless answers please. Thanks!
Beta 4, in my opinion. We're still committing patches that require further patches before they work properly. -- Morbus Iff ( you are nothing without your robot car, NOTHING! ) Culture: http://www.disobey.com/ and http://www.gamegrene.com/ O'Reilly Author, Weblog, Cook: http://www.oreillynet.com/pub/au/779 icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
I think beta 4, the final beta, as well. Reason being, there are some *very* solid patches in the queue that *should* make it into the final release, but as Morbus points out, may require additional patches (but hopefully not). Some of these could be thought of as mini-features and really wouldn't fit in too well with an RC series, which should be predominantly bug and usability fixes. If there is anything we can do to better help the queue and get these in, please let us know. Many of these patches have been thoroughly reviewed and +1ed. Not to mention, if we roll a Beta 4 sometime next week, that gives everyone a chance at DrupalCon to chat, iron out any last 4.7 issues and we can post fixes which can go in before RC1 is shipped. That would really bring together 4.7 and get everyone on the same page before an RC1 ships. Cheers, ted On 1/25/06, Morbus Iff <morbus@disobey.com> wrote:
as mentioned earlier, I intend to package up CVS HEAD later this week (after today's bugfix party). The question is: should this be 'beta 4' or 'RC 1' (or 'RC' tout court)? I'm asking because some people approached me saying we should call it a RC. For fun's sake, I figured I'd ask you first before sharing my own opinion. When you answer, please provide some insight as why you think it should be 'beta 4' or 'RC 1' or 'RC'. No brainless answers please. Thanks!
Beta 4, in my opinion. We're still committing patches that require further patches before they work properly.
-- Morbus Iff ( you are nothing without your robot car, NOTHING! ) Culture: http://www.disobey.com/ and http://www.gamegrene.com/ O'Reilly Author, Weblog, Cook: http://www.oreillynet.com/pub/au/779 icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
Dries Buytaert wrote:
Hello,
as mentioned earlier, I intend to package up CVS HEAD later this week (after today's bugfix party). The question is: should this be 'beta 4' or 'RC 1' (or 'RC' tout court)? I'm asking because some people approached me saying we should call it a RC. For fun's sake, I figured I'd ask you first before sharing my own opinion. When you answer, please provide some insight as why you think it should be 'beta 4' or 'RC 1' or 'RC'. No brainless answers please. Thanks!
-- Dries Buytaert :: http://buytaert.net/
I have vigorously worked the 'ready to review' queue for 3 nights in a row. last night was 'ready to review, bug'. we have a long way to go. so i say beta4. folks - please work those queues.
Whether it is beta4 or rc1 depends on our definition of each. From what others said, it seems there are lots of bugs that need to be quashed. Dries (and perhaps chx and others): Can we come up with a list of bugs that are "release stoppers" for 4.7? One problem is that by default everything is "critical" in the project module. If we have the top 10 or 20 of those, those who cannot attend the IRC parties can work on them offline. Last week chx gave me a few of these, and 2 of them were "cannot reproduce". So, let us come with a list of "if those are fixed, we will release", and limit this to broken things, "not nice to have", or "I want this feature in".
Op woensdag 25 januari 2006 17:21, schreef Moshe Weitzman:
we have a long way to go. so i say beta4.
I say beta 4 too. A release candidate gives too hight expectations, IMO. * First: people will expect a real release soon after. We cannot guarantee it. In fact, I think we all have the same gut feeling that a real release is still rather uncertain, in a near future. * Second: A lot of rather big new patches went in. great! But untill we know if they did not introduce new issues (or actually really fixed them all), we cannot really esitmate the amout of time and effort needed for a stable release. After another betha, we should be more secure about all this. * Thirdly: I -personally- beleive there are really too much bugs still open to release. Eventhough they are no showstoppers, still the queue is very long. And consider those listed, to be the bugs that were actually contributed, and found. We all know that the amount of not-reported (or not yet found) issues, is probably a lot bigger. A beta will bring these issues to drupal.org; which is good. But it will also mean a lot of duplicate bugs, support issues and other (distracting) work. Ber -beta 4 - Kessels -- | Bèr Kessels | webschuur.com | website development | | Jabber & Google Talk: ber@jabber.webschuur.com | http://bler.webschuur.com | http://www.webschuur.com |
'beta 4' or 'RC 1' or 'RC'. No brainless answers please. Thanks!
RC. I do not see any showstopper bugs measured on my scale http://lists.drupal.org/archives/development/2006-01/msg00480.html . What's more we even have a patch waiting for inclusing for the very example of normal bugs -- those that I do not think of showstoppers. What's even more, all "hard" parts (comment edit, user edit) have been seriously patch recently and they work now. This being recent is important because as I said, the form conversion process was rather evolutionary and now we are much better with form API. Regards NK
What's even more, all "hard" parts (comment edit, user edit) have been seriously patch recently and they work now. This being recent is important because as I said, the form conversion process was rather evolutionary and now we are much better with form API.
Actually, comment creation doesn't work in PHP 5: http://drupal.org/node/43325#comment-68511 -- Morbus Iff ( you are nothing without your robot car, NOTHING! ) Culture: http://www.disobey.com/ and http://www.gamegrene.com/ O'Reilly Author, Weblog, Cook: http://www.oreillynet.com/pub/au/779 icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
Dries Buytaert wrote:
Hello,
as mentioned earlier, I intend to package up CVS HEAD later this week (after today's bugfix party). The question is: should this be 'beta 4' or 'RC 1' (or 'RC' tout court)? I'm asking because some people approached me saying we should call it a RC. For fun's sake, I figured I'd ask you first before sharing my own opinion. When you answer, please provide some insight as why you think it should be 'beta 4' or 'RC 1' or 'RC'. No brainless answers please. Thanks!
Personally I wouldn't call it an RC if it contains any known critical bugs that prevent functionality. If we can get all the existing critical bugs out of the way, and no new ones are found, then I would be comfortable calling it an RC. Actually, even some non-critical bugs could stop it from being an RC, really.
All bugs marked critical are considered to be release stoppers. These are all bugs that render certain functionality unusable in such a way you can no longer accomplish a certain task (no work arounds). There is little point in debating the term 'critical' or adding a second 'critical'. -- Dries Buytaert :: http://buytaert.net/
On Wed, 25 Jan 2006 17:51:16 +0100, Dries Buytaert <dries.buytaert@gmail.com> wrote:
All bugs marked critical are considered to be release stoppers. These are all bugs that render certain functionality unusable in such a way you can no longer accomplish a certain task (no work arounds). There is little point in debating the term 'critical' or adding a second 'critical'.
Since the issues default to 'critical' there are a lot of issues that are not critical at all.
All bugs marked critical are considered to be release stoppers. These are all bugs that render certain functionality unusable in such a way you can no longer accomplish a certain task (no work arounds). There is little point in debating the term 'critical' or adding a second 'critical'.
Since the issues default to 'critical' there are a lot of issues that are not critical at all.
Exactly what I meant to say.
Khalid B wrote:
All bugs marked critical are considered to be release stoppers. These are all bugs that render certain functionality unusable in such a way you can no longer accomplish a certain task (no work arounds). There is little point in debating the term 'critical' or adding a second 'critical'.
Since the issues default to 'critical' there are a lot of issues that are not critical at all.
Exactly what I meant to say.
They at least need to be evaluated and marked as not critical.
On 25 Jan 2006, at 18:14, Karoly Negyesi wrote:
On Wed, 25 Jan 2006 17:51:16 +0100, Dries Buytaert <dries.buytaert@gmail.com> wrote:
All bugs marked critical are considered to be release stoppers. These are all bugs that render certain functionality unusable in such a way you can no longer accomplish a certain task (no work arounds). There is little point in debating the term 'critical' or adding a second 'critical'.
Since the issues default to 'critical' there are a lot of issues that are not critical at all.
I just fixed it. It defaults to 'normal' now. -- Dries Buytaert :: http://www.buytaert.net/
On Wed, 25 Jan 2006 17:51:16 +0100, Dries Buytaert <dries.buytaert@gmail.com> wrote:
All bugs marked critical are considered to be release stoppers. These are all bugs that render certain functionality unusable in such a way you can no longer accomplish a certain task (no work arounds).
And to debate with this, when a release months away, I can put up with some "mere" critical bugs for days or even weeks, but those I deemed "extereme critical" are to be fixed instantly because even development is stopped by them. That's a big difference.
On Wed, January 25, 2006 10:51 am, Dries Buytaert said:
All bugs marked critical are considered to be release stoppers. These are all bugs that render certain functionality unusable in such a way you can no longer accomplish a certain task (no work arounds). There is little point in debating the term 'critical' or adding a second 'critical'.
Something else to consider: Would calling it RC instead of beta increase the number of people playing with it and testing it? Calling something a beta version scares off some potential users/testers/bugfinders. Lots of bugs just aren't found until hundreds of people use something rather than dozens. Of course, maybe we still want to scare off non-developers at the moment. I'll leave that decision to someone else; I'm just pointing out a likely side effect. --Larry Garfield
Hi, On Wed, Jan 25, 2006 at 05:03:03PM +0100, Dries Buytaert wrote:
(after today's bugfix party). The question is: should this be 'beta 4' or 'RC 1' (or 'RC' tout court)? I'm asking because some people
Beta. I've used my personal Drupal stability meter: "can I use vanilla Drupal without any patches on my small and simple webpage?" The answer is currently no. I run cvs from a couple of days ago, so some things could have changed, but http://drupal.org/node/43032 seems to be still not fixed. I'd say RC == no patches needed to run Drupal (patches that fix core bugs). -- Piotrek irc: #debian.pl Mors Drosophilis melanogastribus!
participants (11)
-
Bèr Kessels -
Dries Buytaert -
Dries Buytaert -
Earl Miles -
Karoly Negyesi -
Khalid B -
Larry Garfield -
Morbus Iff -
Moshe Weitzman -
piotr＠mallorn.ii.uj.edu.pl -
Theodore Serbinski