According to Dries, http://drupal.org/project/issues? projects=3060&versions=9902,9842,9753,9728,6487&categories=bug&priorities=1&states=1,8,13,14 has 49 entries. There are 749 members on this list. Let's assume that only 1 percent of them are core quality (that's nonsense). Even then, one bugfix a day will close all of them by early next week. Before you turn in, check whether you have fixed your critical 4.7 bug today. It takes usually half an hour at most. To heed my own advice, I just closed two. There are 47 now. Keep me posted in this thread. This week Dries is occupied with upgrading drupal.org. Next Monday I want to point him to an empty list and ask for a release candidate. We can do it. Just one patch every evening and a short note here that you did it. Go!
I looked into this http://drupal.org/node/48440 and cannot reproduce.
This one does not look critical to me http://drupal.org/node/49912 It is partially documentation as well. On 2/20/06, Khalid B <kb@2bits.com> wrote:
I looked into this http://drupal.org/node/48440 and cannot reproduce.
This one I cannot reproduce either. Setting to normal. http://drupal.org/node/49659 On 2/20/06, Khalid B <kb@2bits.com> wrote:
This one does not look critical to me http://drupal.org/node/49912 It is partially documentation as well.
On 2/20/06, Khalid B <kb@2bits.com> wrote:
I looked into this http://drupal.org/node/48440 and cannot reproduce.
This one has been in HEAD for ages, and we have been living with it since at least October 2004. http://drupal.org/node/11206 I am leaving this as is, but don't think this should hold the release. On 2/20/06, Khalid B <kb@2bits.com> wrote:
This one I cannot reproduce either. Setting to normal. http://drupal.org/node/49659
On 2/20/06, Khalid B <kb@2bits.com> wrote:
This one does not look critical to me http://drupal.org/node/49912 It is partially documentation as well.
On 2/20/06, Khalid B <kb@2bits.com> wrote:
I looked into this http://drupal.org/node/48440 and cannot reproduce.
This has a ready to commit patch http://drupal.org/node/41509 So, Dries could review and commit. Other testers welcome of course. On 2/20/06, Khalid B <kb@2bits.com> wrote:
This one has been in HEAD for ages, and we have been living with it since at least October 2004. http://drupal.org/node/11206
I am leaving this as is, but don't think this should hold the release.
On 2/20/06, Khalid B <kb@2bits.com> wrote:
This one I cannot reproduce either. Setting to normal. http://drupal.org/node/49659
On 2/20/06, Khalid B <kb@2bits.com> wrote:
This one does not look critical to me http://drupal.org/node/49912 It is partially documentation as well.
On 2/20/06, Khalid B <kb@2bits.com> wrote:
I looked into this http://drupal.org/node/48440 and cannot reproduce.
On 20-Feb-2006, at 6:48 PM, Khalid B wrote:
This one has been in HEAD for ages, and we have been living with it since at least October 2004. http://drupal.org/node/11206
I am leaving this as is, but don't think this should hold the release.
I have been working on this and expect to have a patch ready tomorrow. This issue is probably a little more critical since the introduction of the new book module permissions. These are likely to be disabled by admins, and will lead to screwy behaviour when users edit top level pages. Djun
This one does not look critical to me http://drupal.org/node/49912 It is partially documentation as well.
Regarding this one. I saw this support request http://drupal.org/node/30845 and I wonder if we shouldn't correct this at least in drupal.module as it's not a Drupal.org related bug. Also, all drupal is parsed wih www.drupal.org weblinks. There's no problem having these as browser will follow the redirect without noticing it. But XML-RPC won't and generate a warning in watchdog, so I think it worth moving it back to drupal.module and make a little patch (done) to change the default setting. But what about URLs in Drupal ? Should we let them as is, or change them all to drupal.org ?
Karoly Negyesi wrote:
According to Dries, http://drupal.org/project/issues? projects=3060&versions=9902,9842,9753,9728,6487&categories=bug&priorities=1&states=1,8,13,14
I downgraded a few that were not critical. I think there are more in that category.
Karoly Negyesi wrote:
According to Dries, http://drupal.org/project/issues? projects=3060&versions=9902,9842,9753,9728,6487&categories=bug&priorities=1&states=1,8,13,14
has 49 entries.
There are 749 members on this list. Let's assume that only 1 percent of them are core quality (that's nonsense). Even then, one bugfix a day will close all of them by early next week.
2 not critical and downgraded accordingly 1 dupe List is now down to 37, I think. jh PS chx: I think *you* need to look at http://drupal.org/node/34181 asap.
PS chx: I think *you* need to look at http://drupal.org/node/34181
See http://drupal.org/node/34002 please. -- Morbus Iff ( morbus == grumblestiltskin ) Technical: http://www.oreillynet.com/pub/au/779 Culture: http://www.disobey.com/ and http://www.gamegrene.com/ icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus
On 2/20/06, Morbus Iff <morbus@disobey.com> wrote:
PS chx: I think *you* need to look at http://drupal.org/node/34181
See http://drupal.org/node/34002 please.
34002 is a feature. My contention is that either issues need to be reviewed and re-assigned more properly as bug/task/feature or the list of issues should include tasks/features. Either way, I would +1 34002 as a blocker for a 4.7 RC. Greg
On 2/20/06, Greg Knaddison <greg.knaddison@gmail.com> wrote:
34002 is a feature. My contention is that either issues need to be reviewed and re-assigned more properly as bug/task/feature or the list of issues should include tasks/features.
Either way, I would +1 34002 as a blocker for a 4.7 RC.
Careful, new 'features' are not being considered ;-)
On 2/20/06, Chris Cook <beerfan@gmail.com> wrote:
On 2/20/06, Greg Knaddison <greg.knaddison@gmail.com> wrote:
34002 is a feature. My contention is that either issues need to be reviewed and re-assigned more properly as bug/task/feature or the list of issues should include tasks/features.
Either way, I would +1 34002 as a blocker for a 4.7 RC.
Careful, new 'features' are not being considered ;-)
The ;-) is because this is not a feature but a (security related) bug. That's my point about being sure to reclassify features into bugs if that is truly the case-as it is here. I don't want to assume with email being what it is and "assuming" doing what it does. For those without knowledge of this idiomatic phrase the quote goes "when you assume you make an _ass_ out of _u_ and _me_ " Greg
Before you turn in, check whether you have fixed your critical 4.7 bug today. It takes usually half an hour at most. To heed my own advice, I just closed two. There are 47 now. Keep me posted in this thread. This week Dries is occupied with upgrading drupal.org. Next Monday I want to point him to an empty list and ask for a release candidate.
Small note: no guarantees on being able to upgrade this week. More about this later this week. I'll give the patch queue some love this week. -- Dries Buytaert :: http://buytaert.net/
On 2/21/06, Karoly Negyesi <karoly@negyesi.net> wrote:
According to Dries, http://drupal.org/project/issues? projects=3060&versions=9902,9842,9753,9728,6487&categories=bug&priorities=1&states=1,8,13,14
has 49 entries.
Looks like we are down to 29 critical bugs now! :-) (I only had to commit 3 patches though.) -- Dries Buytaert :: http://buytaert.net/
We can do it. Just one patch every evening and a short note here that you did it.
Just posted a review and update of puregin's patch for enabling role-based block access, http://drupal.org/node/18018. This much-requested feature is close to ready, but could use at least one more set of eyes and testing, especially since I've introduced some changes.
Nedjo, you rock! Thanks... Djun On 21-Feb-2006, at 12:12 PM, Nedjo Rogers wrote:
We can do it. Just one patch every evening and a short note here that you did it.
Just posted a review and update of puregin's patch for enabling role-based block access, http://drupal.org/node/18018.
This much-requested feature is close to ready, but could use at least one more set of eyes and testing, especially since I've introduced some changes.
Did you say *feature*? :) Goba puregin wrote:
Nedjo, you rock! Thanks... Djun
On 21-Feb-2006, at 12:12 PM, Nedjo Rogers wrote:
We can do it. Just one patch every evening and a short note here that you did it.
Just posted a review and update of puregin's patch for enabling role-based block access, http://drupal.org/node/18018.
This much-requested feature is close to ready, but could use at least one more set of eyes and testing, especially since I've introduced some changes.
I just closed a few too... down to 24 now... On 2/20/06, Karoly Negyesi <karoly@negyesi.net> wrote:
According to Dries, http://drupal.org/project/issues?projects=3060&versions=9902,9842,9753,9728,...
has 49 entries.
There are 749 members on this list. Let's assume that only 1 percent of them are core quality (that's nonsense). Even then, one bugfix a day will close all of them by early next week.
Before you turn in, check whether you have fixed your critical 4.7 bug today. It takes usually half an hour at most. To heed my own advice, I just closed two. There are 47 now. Keep me posted in this thread. This week Dries is occupied with upgrading drupal.org. Next Monday I want to point him to an empty list and ask for a release candidate.
Karoly Negyesi wrote:
According to Dries, http://drupal.org/project/issues? projects=3060&versions=9902,9842,9753,9728,6487&categories=bug&priorities=1&states=1,8,13,14
has 49 entries.
the good news is that we only have 18 left to go!see http://drupal.org/project/issues?projects=3060&versions=9902,9842,9753,9728,...
participants (14)
-
Chris Cook -
Dries Buytaert -
Earl Miles -
Gabor Hojtsy -
Greg Knaddison -
John Handelaar -
Karoly Negyesi -
Khalid B -
Morbus Iff -
Moshe Weitzman -
Nedjo Rogers -
Nicolas Tostin -
puregin -
Theodore Serbinski