We're down to 18 critical bugs! :) URL to bookmark: http://drupal.org/project/issues? projects=3060&versions=9902,9842,9753,9728,6487&categories=bug&prioritie s=1&states=1,8,13,14 -- Dries Buytaert :: http://www.buytaert.net/
URL to bookmark: http://drupal.org/project/issues? projects=3060&versions=9902,9842,9753,9728,6487&categories=bug&prioritie s=1&states=1,8,13,14
Shortened URL services-- -- 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
http://drupal.org/node/50982 code needs review, so I think one bug less. Kuba
On 23 Feb 2006, at 20:57, Dries Buytaert wrote:
We're down to 18 critical bugs! :)
URL to bookmark: http://drupal.org/project/issues? projects=3060&versions=9902,9842,9753,9728,6487&categories=bug&priorit ies=1&states=1,8,13,14
We're down to 13 critical bugs. I guess we'll release a beta 5? I don't think we had 0 critical bugs left when we released either Drupal 4.5 or Drupal 4.6 but I'm willing to try. I have this feeling that it might take us many more weeks to fix them all. -- Dries Buytaert :: http://www.buytaert.net/
On 28 Feb 2006, at 22:23, Dries Buytaert wrote:
URL to bookmark: http://drupal.org/project/issues? projects=3060&versions=9902,9842,9753,9728,6487&categories=bug&priori ties=1&states=1,8,13,14
We're down to 13 critical bugs.
I guess we'll release a beta 5? I don't think we had 0 critical bugs left when we released either Drupal 4.5 or Drupal 4.6 but I'm willing to try. I have this feeling that it might take us many more weeks to fix them all.
Some critical bugs to work on: http://drupal.org/node/28868 -- upgrade path for welcome e-mail * no one assigned to this, fairly easy task, takers? http://drupal.org/node/43220 -- mime type handling (will probably remove) * waiting for walkah, probably going to remove the mime-type handling http://drupal.org/node/49501 -- something wrong with one of the updates that makes the JS updater choke * no one assigned for this, a database available for testing, easy to reproduce now, takers? http://drupal.org/node/5961 -- open_basedir problems * no one assigned for this, around for years, probably dependency on 43220 http://drupal.org/node/42358 -- file upload list stuff not working * dopry is working on this http://drupal.org/node/43462 -- request_uri() brokeness http://drupal.org/node/45064 -- request_uri() brokeness http://drupal.org/node/10917 -- request_uri() brokeness * no one assigned to this, fix 2 (or 3) critical bugs with one patch, takers? http://drupal.org/node/51415 -- problem with moving forum topics http://drupal.org/node/51635 -- problem with moving forum topics http://drupal.org/node/43032 -- problem with moving forum topics * no one assigned to this, fix 3 critical bugs with one patch, takers? -- Dries Buytaert :: http://www.buytaert.net/
On Wed, 2006-03-01 at 10:28 +0100, Dries Buytaert wrote:
On 28 Feb 2006, at 22:23, Dries Buytaert wrote:
URL to bookmark: http://drupal.org/project/issues? projects=3060&versions=9902,9842,9753,9728,6487&categories=bug&priori ties=1&states=1,8,13,14
We're down to 13 critical bugs.
I guess we'll release a beta 5? I don't think we had 0 critical bugs left when we released either Drupal 4.5 or Drupal 4.6 but I'm willing to try. I have this feeling that it might take us many more weeks to fix them all.
Some critical bugs to work on:
http://drupal.org/node/43220 -- mime type handling (will probably remove) * waiting for walkah, probably going to remove the mime-type handling
http://drupal.org/node/5961 -- open_basedir problems * no one assigned for this, around for years, probably dependency on 43220
http://drupal.org/node/42358 -- file upload list stuff not working * dopry is working on this
I'm actually working on all three of these... The first two are related and center around the behavior of file_check_upload. I'd appreciate if someone who can reproduce 43220 would test the patch for 5961 and see if it resolves their problem. The if (function_exists(mime_content_type)) should maintain compatibility for hosts that don't support mime_content_type. * if you really have an issue with the mime_content_type, please open it as another issue, as the original issue killes reported was related to mime_content_type having an invalid path to work with. Issue hijacking really annoys me, as it gets in the way of any real work! * I'm working on a patch that will solve 42358... I'm documenting and testing right now its working well for me, and. I've kind of overstepped the scope of the problem to simplify the upload process. However, my current solution depends on file_check_upload behaving properly, aka depends on the final patch in 5961.
On Wed, 2006-03-01 at 10:28 +0100, Dries Buytaert wrote:
On 28 Feb 2006, at 22:23, Dries Buytaert wrote:
URL to bookmark: http://drupal.org/project/issues? projects=3060&versions=9902,9842,9753,9728,6487&categories=bug&priori ties=1&states=1,8,13,14
We're down to 13 critical bugs.
I guess we'll release a beta 5? I don't think we had 0 critical bugs left when we released either Drupal 4.5 or Drupal 4.6 but I'm willing to try. I have this feeling that it might take us many more weeks to fix them all.
Some critical bugs to work on:
http://drupal.org/node/5961 -- open_basedir problems * no one assigned for this, around for years, probably dependency on 43220
5961 is RTBC.
http://drupal.org/node/42358 -- file upload list stuff not working * dopry is working on this
42358 is up for review... I changed the attachments form to be a reflection of the $node->files array so the FAPI could do the heavy lifting. I'd really like to get these closed out. And would like feedback as to whether my changes make the upload.module easier to follow. .darrel.
On 28 Feb 2006, at 22:23, Dries Buytaert wrote:
We're down to 18 critical bugs! :)
URL to bookmark: http://drupal.org/project/issues? projects=3060&versions=9902,9842,9753,9728,6487&categories=bug&priori ties=1&states=1,8,13,14
We're down to 13 critical bugs.
We're back to 18 critical bugs. -- Dries Buytaert :: http://www.buytaert.net/
Op maandag 6 maart 2006 17:11, schreef Dries Buytaert:
We're back to 18 critical bugs.
I re-opened one, because there were new bugreports and a forumpost indicating its not fixed. We really need some JS savvy people in: http://drupal.org/node/49501 fixing the JS updater. You know your AJAX and JS? Then please have peek in there. Bèr -- | Bèr Kessels | webschuur.com | website development | | Jabber & Google Talk: ber@jabber.webschuur.com | http://bler.webschuur.com | http://www.webschuur.com |
On 28 Feb 2006, at 22:23, Dries Buytaert wrote:
We're down to 18 critical bugs! :)
and we're down to 11 now - http://tinyurl.com/pdzkk - with 1 set to RTC and 6 needing reviews. -K
On 3/8/06, Karthik <narakasura@gmail.com> wrote:
On 28 Feb 2006, at 22:23, Dries Buytaert wrote:
We're down to 18 critical bugs! :)
and we're down to 11 now - http://tinyurl.com/pdzkk - with 1 set to RTC and 6 needing reviews.
You're link is no longer correct (there is a beta 5 now): http://drupal.org/project/issues?projects=3060&versions=10195,9902,9842,9753... -- Dries Buytaert :: http://buytaert.net/
You're link is no longer correct (there is a beta 5 now): http://drupal.org/project/issues?projects=3060&versions=10195,9902,9842,9753...
Ah right - my bad. Shouldn't we be using: http://drupal.org/project/issues/drupal?page=0&projects=3060&categories=bug&... ? That's critical bugs across the board. We can very likely close a bunch of the 4.6.5 issues that will possibly no longer apply. Thanks -K
On Wed, 2006-03-08 at 19:05 +0530, Karthik wrote:
You're link is no longer correct (there is a beta 5 now): http://drupal.org/project/issues?projects=3060&versions=10195,9902,9842,9753...
Ah right - my bad. Shouldn't we be using:
http://drupal.org/project/issues/drupal?page=0&projects=3060&categories=bug&...
?
That's critical bugs across the board. We can very likely close a bunch of the 4.6.5 issues that will possibly no longer apply.
Thanks -K
Just because bugs are closed in the 4.7 tree doesn't mean they're closed in the 4.6 tree, and 4.6 still needs to be supported, until 4.8 is released.
Just because bugs are closed in the 4.7 tree doesn't mean they're closed in the 4.6 tree, and 4.6 still needs to be supported, until 4.8 is released.
As far as I am aware, all non-security/standards related issues for the 4.6/4.5 branch can be closed if they have been fixed in HEAD. Thanks -K
Karthik wrote:
Just because bugs are closed in the 4.7 tree doesn't mean they're closed in the 4.6 tree, and 4.6 still needs to be supported, until 4.8 is released.
As far as I am aware, all non-security/standards related issues for the 4.6/4.5 branch can be closed if they have been fixed in HEAD.
That is our current policy, indeed. For 4.7 we will maintain the branch to more extend, ie I will apply patches for non-critical bugs (but no new features). Cheers, Gerhard
On Wed, Mar 08, 2006 at 08:42:16PM +0100, Gerhard Killesreiter wrote:
Karthik wrote:
Just because bugs are closed in the 4.7 tree doesn't mean they're closed in the 4.6 tree, and 4.6 still needs to be supported, until 4.8 is released.
As far as I am aware, all non-security/standards related issues for the 4.6/4.5 branch can be closed if they have been fixed in HEAD.
That is our current policy, indeed. For 4.7 we will maintain the branch to more extend, ie I will apply patches for non-critical bugs (but no new features).
Eh, sorry? I thought only features and fixes requiring db schema change are not fixable in stable branch. And I'd prefer if it stayed like this. -- Piotrek irc: #debian.pl Mors Drosophilis melanogastribus!
On Wed, 08 Mar 2006 20:42:16 +0100 Gerhard Killesreiter wrote:
Karthik wrote:
As far as I am aware, all non-security/standards related issues for the 4.6/4.5 branch can be closed if they have been fixed in HEAD.
That is our current policy, indeed.
as a specific example, will this no longer be fixed? http://drupal.org/node/49430 "Mysql 5 & db_rewrite_sql issue" (a patch to fix MySQL 5.0.12+ errors in taxonomy.module) now that this has been committed: http://drupal.org/node/51850 "nailing down db_rewrite_sql" (a patch that fixes db_rewrite_sql() to solve all of the JOIN ordering problems once and for all, and fixes the implicit JOIN in taxonomy.module also handled in the 4.6 patch listed above). that seems like a shame to me. i fully understand not adding new features to stable releases, but i don't see how fixing a known bug in the last stable release is a bad thing, even if the bug is already fixed in a (not yet stable) forthcoming release.
For 4.7 we will maintain the branch to more extend, ie I will apply patches for non-critical bugs (but no new features).
that makes perfect sense. new features only go into the development release. but, if the policy (as someone else said) is to "support" 4.6 until 4.8 is out, why not fix bugs when the changes are small? obviously, investing a lot of effort into backporting major changes is a terrible idea, but small, easily verified and tested bug fixes should still be applied to 4.6, IMHO. am i crazy? ;) thanks, -derek
On 08 Mar 2006, at 20:19, Derek Wright wrote:
As far as I am aware, all non-security/standards related issues for the 4.6/4.5 branch can be closed if they have been fixed in HEAD.
That is our current policy, indeed.
as a specific example, will this no longer be fixed?
http://drupal.org/node/49430 "Mysql 5 & db_rewrite_sql issue" (a patch to fix MySQL 5.0.12+ errors in taxonomy.module)
now that this has been committed:
http://drupal.org/node/51850 "nailing down db_rewrite_sql" (a patch that fixes db_rewrite_sql() to solve all of the JOIN ordering problems once and for all, and fixes the implicit JOIN in taxonomy.module also handled in the 4.6 patch listed above).
I still commit bugfixes to the DRUPAL-4-5 and DRUPAL-4-6 branch. These bugfixes are not limited to security problems. For proof, look at any of the release announcements in the Drupal 4.5 or Drupal 4.6 release series. -- Dries Buytaert :: http://www.buytaert.net/
On Wed, 8 Mar 2006 20:30:11 +0100 Dries Buytaert wrote:
I still commit bugfixes to the DRUPAL-4-5 and DRUPAL-4-6 branch.
excellent, glad to hear it! so: 1) no one should go off closing 4.6 issues just because the bug has been fixed in 4.7 ;) 2) we should all be clear what the policy really is. i think it can be summarized as: - new features only happen in a development release, no matter what. - bugs are fixed in all branches where they can be reasonably fixed, if someone does the work to create and test the patches and the core committers agree it's worth the trouble. is that a fair summary? thanks, -derek
On 08 Mar 2006, at 20:39, Derek Wright wrote:
1) no one should go off closing 4.6 issues just because the bug has been fixed in 4.7 ;)
2) we should all be clear what the policy really is. i think it can be summarized as:
- new features only happen in a development release, no matter what.
- bugs are fixed in all branches where they can be reasonably fixed, if someone does the work to create and test the patches and the core committers agree it's worth the trouble.
It is. :) -- Dries Buytaert :: http://www.buytaert.net/
Op woensdag 8 maart 2006 20:39, schreef Derek Wright:
On Wed, 8 Mar 2006 20:30:11 +0100 Dries Buytaert wrote:
I still commit bugfixes to the DRUPAL-4-5 and DRUPAL-4-6 branch.
excellent, glad to hear it!
so:
1) no one should go off closing 4.6 issues just because the bug has been fixed in 4.7 ;)
2) we should all be clear what the policy really is. i think it can be summarized as:
- new features only happen in a development release, no matter what.
- bugs are fixed in all branches where they can be reasonably fixed, if someone does the work to create and test the patches and the core committers agree it's worth the trouble.
- bugs should be fixed in a way that does not require database changes. Only for security issues we allow minimal changes in the database. Or am I wrong? Bèr -- | Bèr Kessels | webschuur.com | website development | | Jabber & Google Talk: ber@jabber.webschuur.com | http://bler.webschuur.com | http://www.webschuur.com | Hoe het naviatie blok te verbergen: http://help.sympal.nl/hoe_het_naviatie_blok_te_verbergen
1) no one should go off closing 4.6 issues just because the bug has been fixed in 4.7 ;)
2) we should all be clear what the policy really is. i think it can be summarized as:
- new features only happen in a development release, no matter what.
- bugs are fixed in all branches where they can be reasonably fixed, if someone does the work to create and test the patches and the core committers agree it's worth the trouble.
- bugs should be fixed in a way that does not require database changes. Only for security issues we allow minimal changes in the database.
Or am I wrong?
Bèr
darrel's statement is as clear as can be, and dries has confirmed it. lets not restart the discussion. i'm guessing ber hasn't finished reading the thread.
On Wed, 2006-03-08 at 16:51 -0500, Moshe Weitzman wrote:
1) no one should go off closing 4.6 issues just because the bug has been fixed in 4.7 ;)
2) we should all be clear what the policy really is. i think it can be summarized as:
- new features only happen in a development release, no matter what.
- bugs are fixed in all branches where they can be reasonably fixed, if someone does the work to create and test the patches and the core committers agree it's worth the trouble.
- bugs should be fixed in a way that does not require database changes. Only for security issues we allow minimal changes in the database.
Or am I wrong?
Bèr
darrel's statement is as clear as can be, and dries has confirmed it
That is actually Derek's statement that is quoted...
Dries Buytaert wrote:
On 08 Mar 2006, at 20:19, Derek Wright wrote:
As far as I am aware, all non-security/standards related issues for the 4.6/4.5 branch can be closed if they have been fixed in HEAD.
That is our current policy, indeed.
as a specific example, will this no longer be fixed?
http://drupal.org/node/49430 "Mysql 5 & db_rewrite_sql issue" (a patch to fix MySQL 5.0.12+ errors in taxonomy.module)
now that this has been committed:
http://drupal.org/node/51850 "nailing down db_rewrite_sql" (a patch that fixes db_rewrite_sql() to solve all of the JOIN ordering problems once and for all, and fixes the implicit JOIN in taxonomy.module also handled in the 4.6 patch listed above).
I still commit bugfixes to the DRUPAL-4-5 and DRUPAL-4-6 branch. These bugfixes are not limited to security problems. For proof, look at any of the release announcements in the Drupal 4.5 or Drupal 4.6 release series.
Right, but if you look at it you will find that many more fixes could have been applied had we had the manpower. WRT the mysql 5 issue: I personally am not inclined to fix it in 4.6 or 4.5, but I would fix it for the upcoming 4.7 branch if it existed today (since I've volunteered to be the maintainer). WRT features: We've neve made backports and I don't intend to change this. Cheers, Gerhard
On Wednesday 08 March 2006 06:03 pm, Dries Buytaert wrote:
On 3/8/06, Karthik <narakasura@gmail.com> wrote:
On 28 Feb 2006, at 22:23, Dries Buytaert wrote:
We're down to 18 critical bugs! :)
and we're down to 11 now - http://tinyurl.com/pdzkk - with 1 set to RTC and 6 needing reviews.
You're link is no longer correct (there is a beta 5 now):
http://drupal.org/project/issues?projects=3060&versions=10195,9902,9842,9753... And what about beta6? How does one figure out the versions id to add to the url? thanks. Augustin. -- http://www.wechange.org/ Because we and the world need to change. http://www.reuniting.info/ Intimate Relationships, peace and harmony in the couple. http://www.gnosis-usa.com/ Revolutionary Psychology, White Tantrism, Dream Yoga... http://www.masquilier.org/ Condorcet, Approval alternative, better voting methods.
On Saturday 18 March 2006 08:25 pm, Anguo wrote:
On Wednesday 08 March 2006 06:03 pm, Dries Buytaert wrote: And what about beta6?
How does one figure out the versions id to add to the url?
by looking at the source of the search page! The updated URL is: http://drupal.org/project/issues?projects=3060&versions=10238,10195,9902,984... or: http://tinyurl.com/g8y8n thank you. Augustin. -- http://www.wechange.org/ Because we and the world need to change. http://www.reuniting.info/ Intimate Relationships, peace and harmony in the couple. http://www.gnosis-usa.com/ Revolutionary Psychology, White Tantrism, Dream Yoga... http://www.masquilier.org/ Condorcet, Approval alternative, better voting methods.
participants (13)
-
Anguo -
Bèr Kessels -
Darrel O'Pry -
Derek Wright -
Dries Buytaert -
Dries Buytaert -
Gerhard Killesreiter -
Karoly Negyesi -
Karthik -
Kuba Zygmunt -
Morbus Iff -
Moshe Weitzman -
piotr＠mallorn.ii.uj.edu.pl