On Thu, Oct 28, 2010 at 10:13 AM, Kalle Korhonen
<[email protected]> wrote:
>> -1 at the moment because I think this is a bit premature. I think
>> when attempting a release, we should at least have a quick email to
>> ask the other devs if there's anything left that needs to be resolved
>> before we can take a vote.
>
> This was discussed on private.
That was the case, but because of a critical work deadline, I've been
out of the loop for the last 36 hours and the comment was embedded in
a long string of emails that I haven't fully caught up on (this
morning I've had my first bit of 'breathing room').
In the past, the project team has always dedicated a thread for
discussing prep for a release, and I assumed it would be the same this
time around and not embedded in a different thread. I'm just asking
that we have such a dedicated discussion thread as a course of action
for anything that will probably lead to a vote ('e.g. 'Upcoming
Release: blah') - just so all members can clearly distinguish things
of this level of importance before being surprised by a full vote.
Alan's comment about the crowd source code is another example of why
this is a good idea. That should have been surfaced in the release
discussion thread, not the vote thread IMO.
This isn't strictly required of course - just a requested courtesy.
The [VOTE] thread itself is obviously enough of an attention grabber
to catch any outstanding issues (as this one clearly did).
I'm fine changing my vote to +1 after I've had a chance to alter those
Jira issues that I've mentioned.
Best,
Les
