# 5.4 alpha - Thread: https://externals.io/message/53427 - Original archive: https://news-web.php.net/php.internals/53427 - Started by Stas Malyshev on 2011-06-20T16:43:04+00:00 - Messages: 26 - Page 1 of 2: messages 1 to 25 (25 per page, add `?page=N` to the URL) - Next page: https://externals.io/message/53427.md?page=2 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #53427 — Stas Malyshev — 2011-06-20T16:43:04+00:00 URL: https://externals.io/message/53427#53427 Hi! Since we've got voting on the process RFCs finally going on, after much deliberation we've decided it'd be best to let the votes finish before the first official 5.4 release. Thus, we decided to postpone 5.4 alpha 1 until June 28th (next Tuesday). The updated schedule is at https://wiki.php.net/todo/php54 , please check out. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 --- ## #53609 — Derick Rethans — 2011-06-28T10:45:41+00:00 URL: https://externals.io/message/53427#53609 · In reply to: #53427 > Since we've got voting on the process RFCs finally going on, after much > deliberation we've decided it'd be best to let the votes finish before the > first official 5.4 release. Thus, we decided to postpone 5.4 alpha 1 until > June 28th (next Tuesday). The updated schedule is at > https://wiki.php.net/todo/php54 , please check out. I think we should delay it a little until we have the bugs data back. Bjori has been in contact with them on the phone today. I would also like to point out that Thursday is our general release day, and we have a release process described in detail here: http://svn.php.net/viewvc/php/php-src/trunk/README.RELEASE_PROCESS?revision=311614&view=markup cheers, Derick --- ## #53614 — Stas Malyshev — 2011-06-28T16:39:10+00:00 URL: https://externals.io/message/53427#53614 · In reply to: #53609 Hi! > I would also like to point out that Thursday is our general release day, > and we have a release process described in detail here: > http://svn.php.net/viewvc/php/php-src/trunk/README.RELEASE_PROCESS?revision=311614&view=markup It doesn't say there Thursday is our general release day. If we want to make it so - ok, let's everybody agree on that and put it there. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 --- ## #53615 — Pierre Joye — 2011-06-28T16:45:20+00:00 URL: https://externals.io/message/53427#53615 · In reply to: #53614 > > […] > > It doesn't say there Thursday is our general release day. If we want to make > it so - ok, let's everybody agree on that and put it there. What we actually did during the last years was to release on Tuesday or Thursday, with a little preference to release final (stable) on Thursday. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org --- ## #53616 — Hannes Magnusson — 2011-06-28T16:54:14+00:00 URL: https://externals.io/message/53427#53616 · In reply to: #53615 > > > > […] > > What we actually did during the last years was to release on Tuesday > or Thursday, with a little preference to release final (stable) on > Thursday. Little preference? According http://www.php.net/releases/ array(4) { ["Thursday"]=> int(30) ["Tuesday"]=> int(3) ["Monday"]=> int(3) ["Wednesday"]=> int(1) } -Hannes --- ## #53617 — Derick Rethans — 2011-06-28T16:55:44+00:00 URL: https://externals.io/message/53427#53617 · In reply to: #53614 > > […] > > It doesn't say there Thursday is our general release day. If we want > to make it so - ok, let's everybody agree on that and put it there. I'm actually surprised it isn't in there. I did write that document some eons ago. But anyway, let's add it then :) cheers, Derick --- ## #53618 — Pierre Joye — 2011-06-28T16:57:01+00:00 URL: https://externals.io/message/53427#53618 · In reply to: #53616 hi, On Tue, Jun 28, 2011 at 6:54 PM, Hannes Magnusson wrote: > Little preference? > > According http://www.php.net/releases/ > > > array(4) { >  ["Thursday"]=> >  int(30) >  ["Tuesday"]=> >  int(3) >  ["Monday"]=> >  int(3) >  ["Wednesday"]=> >  int(1) > } So Thursday was the big preference, wed uploads mean "stable" as we upload it one day before so they get mirrored when the announce is sent. -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org --- ## #53619 — Stas Malyshev — 2011-06-28T16:57:32+00:00 URL: https://externals.io/message/53427#53619 · In reply to: #53617 Hi! > > > I'm actually surprised it isn't in there. I did write that document > some eons ago. But anyway, let's add it then :) OK, as soon as we are all agreed on Thursday and it's there I'll shift the schedule for next releases so it'll actually be on Thursday, though I'm not sure why would it actually matter :) -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 --- ## #53620 — Philip Olson — 2011-06-28T17:28:08+00:00 URL: https://externals.io/message/53427#53620 · In reply to: #53619 > Hi! > > > > […] > > OK, as soon as we are all agreed on Thursday and it's there I'll shift the schedule for next releases so it'll actually be on Thursday, though I'm not sure why would it actually matter :) The day an alpha/beta is released doesn't feel important, unlike stable releases, but I suppose consistency has its good points. :) I think the main point is to wait for bugs.php.net, which is making real progress and should be available Thursday. Also, it's important to clarify that the [soon-to-be-popular] built-in web server is not part of this alpha because the alpha was tagged a few days before its addition. I think repackaging would be worth it for this case, but waiting for alpha2 is feasible. Regards, Philip --- ## #53621 — Stas Malyshev — 2011-06-28T17:31:22+00:00 URL: https://externals.io/message/53427#53621 · In reply to: #53620 Hi! > Also, it's important to clarify that the [soon-to-be-popular] > built-in web server is not part of this alpha because the alpha was > tagged a few days before its addition. I think repackaging would be > worth it for this case, but waiting for alpha2 is feasible. We'll have alpha2 in a month. I'm really not a fan on last minute repackaging, that's when screw ups happen almost every time. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 --- ## #53622 — Pierre Joye — 2011-06-28T17:43:03+00:00 URL: https://externals.io/message/53427#53622 · In reply to: #53621 > Hi! > > > […] > > We'll have alpha2 in a month. I'm really not a fan on last minute > repackaging, that's when screw ups happen almost every time. I do think we should repackage. There are many issues fixed since last week and it makes no sense to release something not representing what the current 5.4 branch is. It takes 1h~ to do it, no big deal. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org --- ## #53623 — Christopher Jones — 2011-06-28T17:57:59+00:00 URL: https://externals.io/message/53427#53623 · In reply to: #53622 > > > […] > > I do think we should repackage. There are many issues fixed since last > week and it makes no sense to release something not representing what > the current 5.4 branch is. +1 Chris -- Email: christopher.jones@oracle.com Tel: +1 650 506 8630 Blog: http://blogs.oracle.com/opal/ --- ## #53624 — Stas Malyshev — 2011-06-28T18:06:20+00:00 URL: https://externals.io/message/53427#53624 · In reply to: #53622 Hi! > I do think we should repackage. There are many issues fixed since last > week and it makes no sense to release something not representing what > the current 5.4 branch is. Really, guys, if we ever want to have scheduled and orderly releases, changing release schedule in the last minute repeatedly and repackaging in the last second is exactly NOT the way to do it. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 --- ## #53625 — Ferenc Kovacs — 2011-06-28T18:10:59+00:00 URL: https://externals.io/message/53427#53625 · In reply to: #53624 > Hi! > > > > […] > > Really, guys, if we ever want to have scheduled and orderly releases, > changing release schedule in the last minute repeatedly and repackaging in > the last second is exactly NOT the way to do it. > Usually I would agree, but in the current situation I would vote for the repackaging. we already streched our release date, and going with the current 5.4 HEAD still seems a better idea than with the current alpha. Tyrael --- ## #53626 — Mike Robinson — 2011-06-28T18:25:22+00:00 URL: https://externals.io/message/53427#53626 · In reply to: #53624 On June-28-11 2:06 PM Stas Malyshev wrote: > > > […] > > Really, guys, if we ever want to have scheduled and orderly releases, > changing release schedule in the last minute repeatedly and repackaging > in the last second is exactly NOT the way to do it. IMHO, exactly right. Not much point in having a plan if it isn't followed, and that usually ends up causing problems - what the plan is supposed to prevent. Best Regards, Mike Robinson --- ## #53627 — David Soria Parra — 2011-06-28T18:25:39+00:00 URL: https://externals.io/message/53427#53627 · In reply to: #53624 > Hi! > > > > […] > > Really, guys, if we ever want to have scheduled and orderly releases, > changing release schedule in the last minute repeatedly and repackaging > in the last second is exactly NOT the way to do it. > I agree with Stas. Repackaging in the last second might cause troubles and include obvious bugs. I prefer having a some time between packaging and releasing, if it's an alpha or not it doesn't matter. So in this case, to really try to finally stay on schedule , so we should release the already pacakged version and have an alpha2 in two weeks. --- ## #53628 — Ferenc Kovacs — 2011-06-28T18:35:13+00:00 URL: https://externals.io/message/53427#53628 · In reply to: #53627 > > > […] > > I agree with Stas. Repackaging in the last second might cause troubles > and include obvious bugs. I prefer having a some time between packaging > and releasing, if it's an alpha or not it doesn't matter. So in this > case, to really try to finally stay on schedule , so we should release the > already pacakged version and have an alpha2 in two weeks. > > -- > > > > wasn't the alpha1 packaged in the last second? it was packaged on Jun 19, and it was planned to be released on Jun 20. and it did include obvious bugs. so if we already screwed up, we could at least fix what we can instead of releasing a version, which we all know is broken. this can make a bad impression in the early adopters. but I won't whine much about this, just told my 2 cents. Tyrael --- ## #53629 — Stas Malyshev — 2011-06-28T19:00:56+00:00 URL: https://externals.io/message/53427#53629 · In reply to: #53628 Hi! > wasn't the alpha1 packaged in the last second? > it was packaged on Jun 19, and it was planned to be released on Jun 20. > and it did include obvious bugs. No, it was not. It was checked, ensured it builds on all systems I have access too, etc, and it was done in advance of the release. And I'm sure it has bugs - as every alpha in the world does. That's why it is alpha and not final release. The point of alpha is not to provide a stable platform but initial point for the release and flush out bugs by expanding the user base. It's not a production release. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 --- ## #53631 — Hannes Magnusson — 2011-06-28T19:49:42+00:00 URL: https://externals.io/message/53427#53631 · In reply to: #53629 > final release. The point of alpha is not to provide a stable platform but > initial point for the release and flush out bugs by expanding the user base. > It's not a production release. Exactly. Requiring a working bug tracker. Postponing the release for a week if I can't get in touch with the guys early enough is the logical thing in my opinion. We do however have a 5.4RC out there for some reason.. As for repacking, I totally agree with not repackage - even though it is very annoying that it doesn't include many things people have been working on :) If you opt for waiting another week, I would like to see a retagging+packaging on Tuesday :] -Hannes --- ## #53632 — Stas Malyshev — 2011-06-28T19:59:35+00:00 URL: https://externals.io/message/53427#53632 · In reply to: #53631 Hi! > > > […] > > Exactly. Requiring a working bug tracker. > Postponing the release for a week if I can't get in touch with the > guys early enough is the logical thing in my opinion. > We do however have a 5.4RC out there for some reason.. It looks like we could have some working tracker (even though without all the old stuff back yet) very soon - at least so it seems from the info that I've got - so provided that we already delayed it a number of times, I'd rather have it out sooner. We could though advance the next alpha - say, to Thursday July 21, if we are settled on Thursday being the Release Day :) - which is not that far out, and will have all the new goodies. I'd rather have something out to get the release process finally officially kick off than to wait again. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 --- ## #53633 — Hannes Magnusson — 2011-06-28T20:06:51+00:00 URL: https://externals.io/message/53427#53633 · In reply to: #53632 > Hi! > > > > […] That was ofcourse supposed to say 5.3RC :) > > It looks like we could have some working tracker (even though without all > the old stuff back yet) very soon - at least so it seems from the info that > I've got - so provided that we already delayed it a number of times, I'd > rather have it out sooner. We could though advance the next alpha - say, to Hang on.. wait what? So Pierres weird threats on IRC weren't silly jokes? Heck, we could apt-get install bugzilla on a random mirror if you just want some bug tracker database to ignore and "have something". -Hannes --- ## #53634 — Ferenc Kovacs — 2011-06-28T20:21:47+00:00 URL: https://externals.io/message/53427#53634 · In reply to: #53633 > Hang on.. wait what? > So Pierres weird threats on IRC weren't silly jokes? > > Heck, we could apt-get install bugzilla on a random mirror if you just > want some bug tracker database to ignore and "have something". > merging the new bugs would be a little more work though. and it would be weird that we change to bugzilla, then back to the old bugtracker when we get the backup from the hoster. Tyrael --- ## #53636 — Pierre Joye — 2011-06-28T21:27:22+00:00 URL: https://externals.io/message/53427#53636 · In reply to: #53633 On Tue, Jun 28, 2011 at 10:06 PM, Hannes Magnusson wrote: > Hang on.. wait what? > So Pierres weird threats on IRC weren't silly jokes? > > Heck, we could apt-get install bugzilla on a random mirror if you just > want some bug tracker database to ignore and "have something". Hannes, with all respects to your work, such comments are not welcome in this list. As I told you, it is not me, but the release managers who decide when a release can be done. And despite our efforts to get the situation around bugs.php.net sorted out, nothing, absolutely nothing happened in two weeks. We bring it back and we will restore the existing data as soon as we have the backups. See my other mail for the details. -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org --- ## #53648 — Derick Rethans — 2011-06-29T10:41:56+00:00 URL: https://externals.io/message/53427#53648 · In reply to: #53629 > > > […] > > No, it was not. It was checked, ensured it builds on all systems I > have access too, etc, and it was done in advance of the release. And > I'm sure it has bugs - as every alpha in the world does. That's why it > is alpha and not final release. The point of alpha is not to provide a > stable platform but initial point for the release and flush out bugs > by expanding the user base. It's not a production release. But it missed the built-in webserver thing :( regards, Derick --- ## #53651 — Ferenc Kovacs — 2011-06-29T11:18:09+00:00 URL: https://externals.io/message/53427#53651 · In reply to: #53648 > > > > […] > > But it missed the built-in webserver thing :( > > regards, > Derick > AFAIK that got into it, but the fixes for the related crashes did not. Tyrael --- Next page: https://externals.io/message/53427.md?page=2