You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@ws.apache.org by Davanum Srinivas <da...@gmail.com> on 2007/05/01 12:53:19 UTC
[POLICY] Release Policy
Folks,
How about we follow incubator project guidelines in addition to what
we do now...Please reply back to general@ws (am BCC'ing all dev
lists).
- All Release binaries must be be explicitly VOTE'd on
- All Release binaries should pass the RAT test [1] (exception: not
sure if RAT support C/C++ code)
- There must be at least 3 Binding PMC VOTE's on each release (which
we do already)
Thanks,
dims
[1] http://code.google.com/p/arat/
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: soap-user-unsubscribe@ws.apache.org
For additional commands, e-mail: soap-user-help@ws.apache.org
Re: [POLICY] Release Policy
Posted by Dinesh Premalal <xy...@gmail.com>.
On 5/1/07, Davanum Srinivas <da...@gmail.com> wrote:
>
> - All Release binaries must be be explicitly VOTE'd on
>
Just in case if release manager changes release artifacts while VOTE
thread is going on, Is it need to re-vote or Is it ok to go with old
votes? Anybody has an idea on this.
thanks,
Dinesh
--
Dinesh Premalal
dinesh@wso2.com
WSO2, Inc.; http://www.wso2.com/
GPG Key ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
Re: [POLICY] Release Policy
Posted by Davanum Srinivas <da...@gmail.com>.
Jeremy,
Please feel free to pick up items from incubator or else where and
bring it into this thread. When this thread dies down, i'll post a
VOTE with line items and then we can beat in into a doc for use by all
ws projects.
thanks,
dims
On 5/1/07, Jeremy Hughes <jp...@gmail.com> wrote:
> Hi Dims,
>
> On 01/05/07, Davanum Srinivas <da...@gmail.com> wrote:
> > Folks,
> >
> > How about we follow incubator project guidelines in addition to what
> > we do now...Please reply back to general@ws (am BCC'ing all dev
> > lists).
>
> Do you mean just the items below or going further and taking the
> incubator podling guideline docs from their website and shaping them
> to fit WS?
>
> >
> > - All Release binaries must be be explicitly VOTE'd on
> > - All Release binaries should pass the RAT test [1] (exception: not
> > sure if RAT support C/C++ code)
> > - There must be at least 3 Binding PMC VOTE's on each release (which
> > we do already)
>
> +1 to these though.
>
> >
> > Thanks,
> > dims
> >
> > [1] http://code.google.com/p/arat/
>
> Cheers,
> Jeremy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
> For additional commands, e-mail: general-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org
Re: [POLICY] Release Policy
Posted by David Illsley <da...@gmail.com>.
+1 to the specified guidelines and to putting them into some kind of
ws.apache-specific policy document.
David
On 01/05/07, Jeremy Hughes <jp...@gmail.com> wrote:
> Hi Dims,
>
> On 01/05/07, Davanum Srinivas <da...@gmail.com> wrote:
> > Folks,
> >
> > How about we follow incubator project guidelines in addition to what
> > we do now...Please reply back to general@ws (am BCC'ing all dev
> > lists).
>
> Do you mean just the items below or going further and taking the
> incubator podling guideline docs from their website and shaping them
> to fit WS?
>
> >
> > - All Release binaries must be be explicitly VOTE'd on
> > - All Release binaries should pass the RAT test [1] (exception: not
> > sure if RAT support C/C++ code)
> > - There must be at least 3 Binding PMC VOTE's on each release (which
> > we do already)
>
> +1 to these though.
>
> >
> > Thanks,
> > dims
> >
> > [1] http://code.google.com/p/arat/
>
> Cheers,
> Jeremy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
> For additional commands, e-mail: general-help@ws.apache.org
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org
Re: [POLICY] Release Policy
Posted by Jeremy Hughes <jp...@gmail.com>.
Hi Dims,
On 01/05/07, Davanum Srinivas <da...@gmail.com> wrote:
> Folks,
>
> How about we follow incubator project guidelines in addition to what
> we do now...Please reply back to general@ws (am BCC'ing all dev
> lists).
Do you mean just the items below or going further and taking the
incubator podling guideline docs from their website and shaping them
to fit WS?
>
> - All Release binaries must be be explicitly VOTE'd on
> - All Release binaries should pass the RAT test [1] (exception: not
> sure if RAT support C/C++ code)
> - There must be at least 3 Binding PMC VOTE's on each release (which
> we do already)
+1 to these though.
>
> Thanks,
> dims
>
> [1] http://code.google.com/p/arat/
Cheers,
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org
Re: [POLICY] Release Policy
Posted by Thilina Gunarathne <cs...@gmail.com>.
Better late than never... :)
Big +1...
Even though this will make the process complicated, this can take off
lot of pressure and responsibility off from the release mangers head,
as there will be more people to check the final release build.. This
will help us to eliminate the last minute mistakes...
~Thilina
On 5/3/07, Daniel Jemiolo <da...@us.ibm.com> wrote:
> Wouldn't the fact that the community has to approve the release by voting
> prevent people from creating an unstable or unwarranted release? If
> someone wanted to hijack that plan and create a release that wasn't on
> schedule, he would have to gain the support of the community and those
> with binding votes (who are presumably in tune with what the community
> wants, and would veto anything that was not healthy for the project).
> Keeping the requirements simple (one vote) makes the process seem more
> community-driven and less corporate/bureaucratic, in my opinion.
>
> Dan
>
>
> Sanjiva Weerawarana <sa...@opensource.lk> wrote on 05/02/2007 02:29:27
> PM:
>
> > Is there even a release manager concept though in that model? Anyone can
>
> > build candidate release artifacts and call for a vote? No that doesn't
> > make sense .. so we'd still need to have a vote to decide to do a
> release,
> > appoint a release manager and then that person calls for the vote on
> > actual candidate release artifacts. Is that the basic proposal?
> >
> > Sanjiva.
> >
> > Davanum Srinivas wrote:
> > > new VOTE has to be explicitly started.
> > >
> > > -- dims
> > >
> > > On 5/2/07, Dinesh Premalal <di...@wso2.com> wrote:
> > >> Hi,
> > >> "Davanum Srinivas" <da...@gmail.com> writes:
> > >>
> > >>
> > >> > - All Release binaries must be be explicitly VOTE'd on
> > >>
> > >> Just in case if release manager change release artifacts while VOTE
> > >> thread going on, Is it need to re-vote or Is it ok to go with old
> > >> votes? Anybody has an idea on this.
> > >>
> > >> thanks,
> > >> Dinesh
> > >> --
> > >> Dinesh Premalal
> > >> dinesh@wso2.com
> > >> WSO2, Inc.; http://www.wso2.com/
> > >> GPG Key ID : A255955C
> > >> GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255
> 955C
> > >>
> > >
> > >
> >
> > --
> > Sanjiva Weerawarana, Ph.D.
> > Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> > Director; Open Source Initiative; http://www.opensource.org/
> > Member; Apache Software Foundation; http://www.apache.org/
> > Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
> > For additional commands, e-mail: general-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
> For additional commands, e-mail: general-help@ws.apache.org
>
>
--
Thilina Gunarathne - http://www.wso2.com - http://thilinag.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org
Re: [POLICY] Release Policy
Posted by Davanum Srinivas <da...@gmail.com>.
Time to readup on what httpd does. that's the gold standard:
http://httpd.apache.org/dev/release.html
-- dims
On 5/2/07, Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> Is there even a release manager concept though in that model? Anyone can
> build candidate release artifacts and call for a vote? No that doesn't
> make sense .. so we'd still need to have a vote to decide to do a release,
> appoint a release manager and then that person calls for the vote on
> actual candidate release artifacts. Is that the basic proposal?
>
> Sanjiva.
>
> Davanum Srinivas wrote:
> > new VOTE has to be explicitly started.
> >
> > -- dims
> >
> > On 5/2/07, Dinesh Premalal <di...@wso2.com> wrote:
> >> Hi,
> >> "Davanum Srinivas" <da...@gmail.com> writes:
> >>
> >>
> >> > - All Release binaries must be be explicitly VOTE'd on
> >>
> >> Just in case if release manager change release artifacts while VOTE
> >> thread going on, Is it need to re-vote or Is it ok to go with old
> >> votes? Anybody has an idea on this.
> >>
> >> thanks,
> >> Dinesh
> >> --
> >> Dinesh Premalal
> >> dinesh@wso2.com
> >> WSO2, Inc.; http://www.wso2.com/
> >> GPG Key ID : A255955C
> >> GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
> >>
> >
> >
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Director; Open Source Initiative; http://www.opensource.org/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
> For additional commands, e-mail: general-help@ws.apache.org
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org
Re: [POLICY] Release Policy
Posted by Daniel Jemiolo <da...@us.ibm.com>.
Wouldn't the fact that the community has to approve the release by voting
prevent people from creating an unstable or unwarranted release? If
someone wanted to hijack that plan and create a release that wasn't on
schedule, he would have to gain the support of the community and those
with binding votes (who are presumably in tune with what the community
wants, and would veto anything that was not healthy for the project).
Keeping the requirements simple (one vote) makes the process seem more
community-driven and less corporate/bureaucratic, in my opinion.
Dan
Sanjiva Weerawarana <sa...@opensource.lk> wrote on 05/02/2007 02:29:27
PM:
> Is there even a release manager concept though in that model? Anyone can
> build candidate release artifacts and call for a vote? No that doesn't
> make sense .. so we'd still need to have a vote to decide to do a
release,
> appoint a release manager and then that person calls for the vote on
> actual candidate release artifacts. Is that the basic proposal?
>
> Sanjiva.
>
> Davanum Srinivas wrote:
> > new VOTE has to be explicitly started.
> >
> > -- dims
> >
> > On 5/2/07, Dinesh Premalal <di...@wso2.com> wrote:
> >> Hi,
> >> "Davanum Srinivas" <da...@gmail.com> writes:
> >>
> >>
> >> > - All Release binaries must be be explicitly VOTE'd on
> >>
> >> Just in case if release manager change release artifacts while VOTE
> >> thread going on, Is it need to re-vote or Is it ok to go with old
> >> votes? Anybody has an idea on this.
> >>
> >> thanks,
> >> Dinesh
> >> --
> >> Dinesh Premalal
> >> dinesh@wso2.com
> >> WSO2, Inc.; http://www.wso2.com/
> >> GPG Key ID : A255955C
> >> GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255
955C
> >>
> >
> >
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Director; Open Source Initiative; http://www.opensource.org/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
> For additional commands, e-mail: general-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org
Re: [POLICY] Release Policy
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Is there even a release manager concept though in that model? Anyone can
build candidate release artifacts and call for a vote? No that doesn't
make sense .. so we'd still need to have a vote to decide to do a release,
appoint a release manager and then that person calls for the vote on
actual candidate release artifacts. Is that the basic proposal?
Sanjiva.
Davanum Srinivas wrote:
> new VOTE has to be explicitly started.
>
> -- dims
>
> On 5/2/07, Dinesh Premalal <di...@wso2.com> wrote:
>> Hi,
>> "Davanum Srinivas" <da...@gmail.com> writes:
>>
>>
>> > - All Release binaries must be be explicitly VOTE'd on
>>
>> Just in case if release manager change release artifacts while VOTE
>> thread going on, Is it need to re-vote or Is it ok to go with old
>> votes? Anybody has an idea on this.
>>
>> thanks,
>> Dinesh
>> --
>> Dinesh Premalal
>> dinesh@wso2.com
>> WSO2, Inc.; http://www.wso2.com/
>> GPG Key ID : A255955C
>> GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
>>
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Director; Open Source Initiative; http://www.opensource.org/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org
Re: [POLICY] Release Policy
Posted by Davanum Srinivas <da...@gmail.com>.
new VOTE has to be explicitly started.
-- dims
On 5/2/07, Dinesh Premalal <di...@wso2.com> wrote:
> Hi,
> "Davanum Srinivas" <da...@gmail.com> writes:
>
>
> > - All Release binaries must be be explicitly VOTE'd on
>
> Just in case if release manager change release artifacts while VOTE
> thread going on, Is it need to re-vote or Is it ok to go with old
> votes? Anybody has an idea on this.
>
> thanks,
> Dinesh
> --
> Dinesh Premalal
> dinesh@wso2.com
> WSO2, Inc.; http://www.wso2.com/
> GPG Key ID : A255955C
> GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org
Re: [POLICY] Release Policy
Posted by Jeremy Hughes <hu...@apache.org>.
On 01/05/07, Daniel Jemiolo <da...@us.ibm.com> wrote:
> +1 to all of these... although I thought 1 & 3 were already official
> policy(!)
I looked but couldn't find anything that actually said they were
policy. More like best practice.
>
> Dan
>
>
>
> "Davanum Srinivas" <da...@gmail.com> wrote on 05/01/2007 06:53:19 AM:
>
> > Folks,
> >
> > How about we follow incubator project guidelines in addition to what
> > we do now...Please reply back to general@ws (am BCC'ing all dev
> > lists).
> >
> > - All Release binaries must be be explicitly VOTE'd on
> > - All Release binaries should pass the RAT test [1] (exception: not
> > sure if RAT support C/C++ code)
> > - There must be at least 3 Binding PMC VOTE's on each release (which
> > we do already)
> >
> > Thanks,
> > dims
> >
> > [1] http://code.google.com/p/arat/
> >
> > --
> > Davanum Srinivas :: http://davanum.wordpress.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: pubscribe-user-unsubscribe@ws.apache.org
> > For additional commands, e-mail: pubscribe-user-help@ws.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
> For additional commands, e-mail: general-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org
Re: [POLICY] Release Policy
Posted by Daniel Jemiolo <da...@us.ibm.com>.
+1 to all of these... although I thought 1 & 3 were already official
policy(!)
Dan
"Davanum Srinivas" <da...@gmail.com> wrote on 05/01/2007 06:53:19 AM:
> Folks,
>
> How about we follow incubator project guidelines in addition to what
> we do now...Please reply back to general@ws (am BCC'ing all dev
> lists).
>
> - All Release binaries must be be explicitly VOTE'd on
> - All Release binaries should pass the RAT test [1] (exception: not
> sure if RAT support C/C++ code)
> - There must be at least 3 Binding PMC VOTE's on each release (which
> we do already)
>
> Thanks,
> dims
>
> [1] http://code.google.com/p/arat/
>
> --
> Davanum Srinivas :: http://davanum.wordpress.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: pubscribe-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: pubscribe-user-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org