You don't even need time to test the patch! You just apply it on your production site, the bigger, the better and sit back. If it breaks stuff, you undo the patch. If it works, you report back success after a day of testing. In other words, we are pretty confident it's release worthy. On the other hand, we do not want to release something bad. So please help us in testing. Thanks Karoly Negyesi Ps. Yes last time we should have done the same. It's never late to correct yourself though :) .
Is there a reason for not releasing it as a beta? Probably would get more interest. Or would that confuse people? On 2/23/06, Karoly Negyesi <karoly@negyesi.net> wrote:
You don't even need time to test the patch! You just apply it on your production site, the bigger, the better and sit back. If it breaks stuff, you undo the patch. If it works, you report back success after a day of testing.
In other words, we are pretty confident it's release worthy. On the other hand, we do not want to release something bad. So please help us in testing.
Thanks
Karoly Negyesi
Ps. Yes last time we should have done the same. It's never late to correct yourself though :) .
Nathan The normal process is that beta is for unreleased software. Security fixes do not go to beta, as you said it is too confusing, and also a resource drain on the community. On 2/23/06, Nathan Digriz <nathandigriz@gmail.com> wrote:
Is there a reason for not releasing it as a beta? Probably would get more interest. Or would that confuse people?
On 2/23/06, Karoly Negyesi < karoly@negyesi.net> wrote:
You don't even need time to test the patch! You just apply it on your production site, the bigger, the better and sit back. If it breaks stuff, you undo the patch. If it works, you report back success after a day of testing.
In other words, we are pretty confident it's release worthy. On the other hand, we do not want to release something bad. So please help us in testing.
Thanks
Karoly Negyesi
Ps. Yes last time we should have done the same. It's never late to correct yourself though :) .
On Thu, Feb 23, 2006 at 09:54:58AM +0100, Karoly Negyesi wrote:
You don't even need time to test the patch! You just apply it on your production site, the bigger, the better and sit back. If it breaks stuff, you undo the patch. If it works, you report back success after a day of testing.
In other words, we are pretty confident it's release worthy. On the other hand, we do not want to release something bad. So please help us in testing.
Hello, any chance http://drupal.org/node/48591#comment-75827 will be commited before 4.6.6 is released? The patch needs a review/test (yes, I know it's "postgresql" bug, but the patch changes node_save() so it affect everyone). -- Piotrek irc: #debian.pl Mors Drosophilis melanogastribus!
On Thursday 23 February 2006 12:54 am, Karoly Negyesi wrote:
You don't even need time to test the patch! You just apply it on your production site, the bigger, the better and sit back. If it breaks stuff, you undo the patch. If it works, you report back success after a day of testing.
In other words, we are pretty confident it's release worthy. On the other hand, we do not want to release something bad. So please help us in testing.
Thanks
Karoly Negyesi
Ps. Yes last time we should have done the same. It's never late to correct yourself though :) .
Umm, were interested parties supposed to contact you privately for a URL? -- Jason Flatt http://www.oadae.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 13; Cramer, 11; Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005) Linux User: http://www.sourcemage.org/ Drupal Fanatic: http://drupal.org/
participants (5)
-
Jason Flatt -
Karoly Negyesi -
Khalid B -
Nathan Digriz -
piotr＠mallorn.ii.uj.edu.pl