You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Amend, Christian" <ch...@sap.com> on 2015/10/28 15:37:44 UTC
[VOTE] New release process for V4 library
Hi,
As per our discussion about the release process[1] I think that we have reached a consensus. Since this is a big change for how we operate Olingo right now I would like to call for a vote on this topic.
The following rules will apply for the V4 core library (client + server) starting with a successful vote:
1. We plan a new release ~3 months
2. Critical and major bugs must be fixed before a release can be made. Changes to the priority can be made if the issue does not fit the "major" or "critical" priority
3. The roadmap will be tracked within the JIRA and should be made as early as possible
4. Additional unplanned features can happen but should be added with consent of the Olingo PMC
5. We will provide informal beta releases for testing after ~1,5 months (no release process required)
If I missed anything please don`t hesitate to reply and point it out.
I vote +1 for these changes to our release policy. If this vote is successful I would also document this on our homepage.
Best Regards,
Christian
[1] http://markmail.org/thread/yiogo2hmzsqifcmc
Re: [VOTE] New release process for V4 library
Posted by Ramesh Reddy <ra...@redhat.com>.
+1
a tentative target release date should be set on JIRA system, so that community users will have visibility when the next release is coming up.
Ramesh..
----- Original Message -----
> Hi,
>
> As per our discussion about the release process[1] I think that we have
> reached a consensus. Since this is a big change for how we operate Olingo
> right now I would like to call for a vote on this topic.
>
> The following rules will apply for the V4 core library (client + server)
> starting with a successful vote:
>
>
> 1. We plan a new release ~3 months
>
> 2. Critical and major bugs must be fixed before a release can be made.
> Changes to the priority can be made if the issue does not fit the "major" or
> "critical" priority
>
> 3. The roadmap will be tracked within the JIRA and should be made as
> early as possible
>
> 4. Additional unplanned features can happen but should be added with
> consent of the Olingo PMC
>
> 5. We will provide informal beta releases for testing after ~1,5 months
> (no release process required)
>
> If I missed anything please don`t hesitate to reply and point it out.
>
> I vote +1 for these changes to our release policy. If this vote is successful
> I would also document this on our homepage.
>
> Best Regards,
> Christian
>
> [1] http://markmail.org/thread/yiogo2hmzsqifcmc
>
Re: [VOTE] New release process for V4 library
Posted by Madhawa Kasun Gunasekara <ma...@gmail.com>.
+1
Madhawa
On Thu, Oct 29, 2015 at 1:05 AM, mibo <mi...@apache.org> wrote:
> Hi,
>
> from my side a +1 after our discussion about the release process ;o)
>
> Only suggestion/adaption to below is, that we should try to change the
> default priority for a new created JIRA issue to be not „major“.
> IMHO the default should be between „major“ and „minor“, however this does
> not exists as an option ;o)
> And as far as I know the Apache JIRA does not allow a modification of this
> (please correct me if I’am wrong).
>
> But all above does not change my „+1“ for our consensus ;o)
>
> Best Regards,
> Michael
>
> > Am 28.10.2015 um 15:37 schrieb Amend, Christian <christian.amend@sap.com
> >:
> >
> > Hi,
> >
> > As per our discussion about the release process[1] I think that we have
> reached a consensus. Since this is a big change for how we operate Olingo
> right now I would like to call for a vote on this topic.
> >
> > The following rules will apply for the V4 core library (client + server)
> starting with a successful vote:
> >
> >
> > 1. We plan a new release ~3 months
> >
> > 2. Critical and major bugs must be fixed before a release can be
> made. Changes to the priority can be made if the issue does not fit the
> "major" or "critical" priority
> >
> > 3. The roadmap will be tracked within the JIRA and should be made
> as early as possible
> >
> > 4. Additional unplanned features can happen but should be added
> with consent of the Olingo PMC
> >
> > 5. We will provide informal beta releases for testing after ~1,5
> months (no release process required)
> >
> > If I missed anything please don`t hesitate to reply and point it out.
> >
> > I vote +1 for these changes to our release policy. If this vote is
> successful I would also document this on our homepage.
> >
> > Best Regards,
> > Christian
> >
> > [1] http://markmail.org/thread/yiogo2hmzsqifcmc
>
>
Re: [VOTE] New release process for V4 library
Posted by mibo <mi...@apache.org>.
Hi,
from my side a +1 after our discussion about the release process ;o)
Only suggestion/adaption to below is, that we should try to change the default priority for a new created JIRA issue to be not „major“.
IMHO the default should be between „major“ and „minor“, however this does not exists as an option ;o)
And as far as I know the Apache JIRA does not allow a modification of this (please correct me if I’am wrong).
But all above does not change my „+1“ for our consensus ;o)
Best Regards,
Michael
> Am 28.10.2015 um 15:37 schrieb Amend, Christian <ch...@sap.com>:
>
> Hi,
>
> As per our discussion about the release process[1] I think that we have reached a consensus. Since this is a big change for how we operate Olingo right now I would like to call for a vote on this topic.
>
> The following rules will apply for the V4 core library (client + server) starting with a successful vote:
>
>
> 1. We plan a new release ~3 months
>
> 2. Critical and major bugs must be fixed before a release can be made. Changes to the priority can be made if the issue does not fit the "major" or "critical" priority
>
> 3. The roadmap will be tracked within the JIRA and should be made as early as possible
>
> 4. Additional unplanned features can happen but should be added with consent of the Olingo PMC
>
> 5. We will provide informal beta releases for testing after ~1,5 months (no release process required)
>
> If I missed anything please don`t hesitate to reply and point it out.
>
> I vote +1 for these changes to our release policy. If this vote is successful I would also document this on our homepage.
>
> Best Regards,
> Christian
>
> [1] http://markmail.org/thread/yiogo2hmzsqifcmc