On 23/03/07, Oleg Kalnichevski <[EMAIL PROTECTED]> wrote:
On Fri, 2007-03-23 at 10:06 +0000, sebb wrote:
> > On 3/22/07, Roland Weber <[EMAIL PROTECTED]> wrote:
> > > Hi Oleg, all,
> > >
> > > I think re-voting on the actual release packages is the
> > > way to go. But I also think we should take those votes to
> > > general@, now and in the future. Discuss new releases
> > > informally here, tag the code, build and review... then
> > > vote on general@, where basically all the PMCs are.
>
> Only just noticed this part of the thread.
>
> AIUI, yes, formal release votes must be on the general list so that
> all the PMC members will see them.
>
Sebastian,
As far as I know it is perfectly legitimate to hold release votes on
project dev lists. All latest Commons releases were voted upon on
commons-dev if my memory serves me well.
You may well be right...
I thought I remembered being told that JMeter votes must include the
PMC; but a search through my archives only reveals a message saying to
use general AT rather than PMC AT in order to make the vote public. I
can't find why PMC was added at present.
The important aspect is having at least 3 +1 binding votes; for
commons there may well be enough PMC members on the dev list. For this
project (and JMeter) that is less likely.
Oleg
> But having a preliminary discussion/vote on this list seems to me to
> have been very useful too, especially as this is a new package.
> Probably still needed in future releases, but likely to be shorter...
>
> S.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
