-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Owen Winkler wrote:
> Sean Coates wrote:
>>> I totally agree, you just beat me to the email. The majority of the
>>> PMC in fact is on the east coast of the US and would have been
>>> asleep during this vote. I'm +1 as well, but even if I'd been -1 and
>>> had some valid technical reason to veto the release this morning it
>>> wouldn't have done me much good...
>> Sign me up for a third on that. I also agree that a middle of the
>> night vote (at least for me) is useless.
>> FWIW, I'm also +1 on release.
>> We're not on a real deadline, though, so there's no reason this vote
>> couldn't have stayed open for at least 12h (preferably at least 24).
>>
>
> I'll take the blame for that.
>
> Three weeks of work specifically to get to a release and a couple of
> solid nights of exhaustive testing ("Dear God, Michael Harris, we know
> about that bug, for the love of Pete!") should still merit 24 hours of
> vote veto.
>
> Owen
>
I think we need to look at the release process as a whole to prevent the
short vote time as well as the giant time between releases. Given the
amount of time since our last release, I don't think that three weeks is
really a ridiculous amount of time for prepping the release.
These are my suggestions off the top of my head...
We need a way to identify, reliably, when it's time to release. How do
do that I don't have a clue. People with more whole-project experience
will have to provide input on that. My initial thought is that any
community member should be able to call for a release vote. The vote
should simply be "Has enough changed to make it worthwhile for a typical
user to upgrade?" If the vote is yes, then we initiate our release
procedure.
We then need a more formalized release procedure consisting of
branching/tagging, testing, notification to plugin/theme developers,
documentation, and then packaging, voting, releasing and followup.
I'll try to start building something on the wiki with more specifics
about what I'm thinking when time allows.
- --
Sean T. Evans
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAknaXQ4ACgkQmQpMBUWJpdt8WgCglkL13oMpDN0Ag9jXkfmkBSu8
fpUAoNpe8lQ21AZdW8/j0lqcQYHx1KbS
=V6RW
-----END PGP SIGNATURE-----
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
-~----------~----~----~----~------~----~------~--~---
