On Tue, Nov 08, 2016 at 02:30:22PM -0700, Darin McBride wrote:
> (In fact, if I remember, I'd propose the same rule of thumb for voting here
> in
> general - rather than making it a hard-and-fast 72hr wait, I'd suggest in
> general, using an async communication method such as email, that the
On Tue, Nov 08, 2016 at 07:06:10AM +, Andrew Beverley wrote:
> Thanks for the updated governance MST. Just one comment/question from
> me (this is not intended to be critical because I made the previous
> alternate proposal, it's a genuine concern that I would like to see
> answered that led
On 2016-11-08 1:10 PM, Matt S Trout wrote:
On Tue, Nov 08, 2016 at 12:18:14PM +0100, Hartmaier Alexander wrote:
Are 72 hours enough to reach a significant amount of list members?
For releasing a CPAN version that's fine for me as git master should
always be in a releaseable state but for
On Tuesday November 8 2016 9:05:30 PM Matt S Trout wrote:
> On Mon, Nov 07, 2016 at 10:42:38PM -0800, Darren Duncan wrote:
> > Here's an idea. In the spirit of your proposal, how about when the
> > discussion seems to be over and it seems time to vote, either Matt
> > or Peter would propose that
On 2016-11-08 1:05 PM, Matt S Trout wrote:
On Mon, Nov 07, 2016 at 10:42:38PM -0800, Darren Duncan wrote:
Here's an idea. In the spirit of your proposal, how about when the
discussion seems to be over and it seems time to vote, either Matt
or Peter would propose that a vote occurs, with the
On Tue, Nov 08, 2016 at 12:18:14PM +0100, Hartmaier Alexander wrote:
> Are 72 hours enough to reach a significant amount of list members?
> For releasing a CPAN version that's fine for me as git master should
> always be in a releaseable state but for feature branch merges I'd like
> to have this
On Mon, Nov 07, 2016 at 10:42:38PM -0800, Darren Duncan wrote:
> Here's an idea. In the spirit of your proposal, how about when the
> discussion seems to be over and it seems time to vote, either Matt
> or Peter would propose that a vote occurs, with the VOTE email etc,
> and then the other one
Are 72 hours enough to reach a significant amount of list members?
For releasing a CPAN version that's fine for me as git master should
always be in a releaseable state but for feature branch merges I'd like
to have this extended to say a week.
What do the others think?
