+1 for 3-month minor release schedule
> On Oct 9, 2018, at 12:32 AM, Juan José Ramos <jra...@pivotal.io> wrote:
>
> +1 for time-based releases.
>
> On Tue, Oct 9, 2018 at 12:02 AM Michael Stolz <mst...@pivotal.io> wrote:
>
>> +1 Quarterly releases
>>
>> --
>> Mike Stolz
>> Principal Engineer - Gemfire Product Manager
>> Mobile: 631-835-4771
>>
>> On Oct 8, 2018 6:52 PM, "Sai Boorlagadda" <sai.boorlaga...@gmail.com>
>> wrote:
>>
>>> +1 for time-based minors (if patches are reserved for security fixes)
>>>
>>> On Mon, Oct 8, 2018 at 2:55 PM Anthony Baker <aba...@pivotal.io> wrote:
>>>
>>>> We reserve the patch version number for when we want to issue a fix
>> for a
>>>> security vulnerability or address a critical bug. We did that with
>> 1.1.1
>>>> and 1.2.1.
>>>>
>>>> I think the release schedule and SemVer are separate topics. AFAICT
>> this
>>>> proposal is just about putting a more deterministic schedule around
>> what
>>> we
>>>> are already doing / have been doing. Given that releases have
>>> significant
>>>> overhead, I think it makes sense to plan ahead. If you want to know
>> more
>>>> about that ask Naba, the last release manager :-)
>>>>
>>>>
>>>> Anthony
>>>>
>>>>
>>>>> On Oct 8, 2018, at 2:42 PM, Udo Kohlmeyer <u...@apache.org> wrote:
>>>>>
>>>>> -0
>>>>>
>>>>> It seems we have completely disregarded the *patch* version number.
>>> Does
>>>> this mean Geode versions will be *major*,*minor*? Can we then remove
>> the
>>>> *patch* version on the release version?
>>>>>
>>>>> In addition to this, should the test coverage not be sufficient
>> enough
>>>> to allow "release when green"? I must agree with @Jacob, I would prefer
>>>> something a lot less formalized. If the community has contributed a
>>>> significant fix, should that not warrant an ad-hoc patch release? Or
>> what
>>>> if the community has added functionality, that could "fill" a single
>>> minor
>>>> release by itself, should that not warrant a pre-emptive release.
>>>>>
>>>>> All these questions are not enough to warrant this effort to be
>>> blocked,
>>>> but I prefer those use cases to be considered for a more comprehensive
>>>> documentation effort, than what is currently on the wiki.
>>>>>
>>>>> In addition to that, is a release with only bug fixes in it, really
>>>> still a worthy of minor release number, or does it not count as a patch
>>>> release?
>>>>>
>>>>> --Udo
>>>>>
>>>>>
>>>>> On 10/8/18 14:27, Jacob Barrett wrote:
>>>>>> +0
>>>>>>
>>>>>> My preference is to release when there is something worth releasing
>>>> rather
>>>>>> than arbitrary points in time but I don't hold that preference
>>> strongly
>>>>>> enough to spike this effort.
>>>>>>
>>>>>> On Mon, Oct 8, 2018 at 2:24 PM Alexander Murmann <
>> amurm...@pivotal.io
>>>>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi everyone,
>>>>>>>
>>>>>>> As discussed in "Predictable minor release cadence", I'd like us to
>>>> find
>>>>>>> agreement on releasing a new minor version every three months.
>> There
>>>> are
>>>>>>> more details in the other thread and I should have captured
>>> everything
>>>>>>> relevant on the wiki:
>>>>>>> https://cwiki.apache.org/confluence/display/GEODE/Release+Schedule
>>>>>>>
>>>>>>> There are also some discussions about patch releases. Let's please
>>>> focus
>>>>>>> this vote on the proposed minor release schedule and carry on other
>>>>>>> discussions in the [DISCUSS] thread.
>>>>>>>
>>>>>>> Thank you all!
>>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>
>
> --
> Juan José Ramos Cassella
> Senior Technical Support Engineer
> Email: jra...@pivotal.io
> Office#: +353 21 4238611
> Mobile#: +353 87 2074066
> After Hours Contact#: +1 877 477 2269
> Office Hours: Mon - Thu 08:30 - 17:00 GMT. Fri 08:30 - 16:00 GMT
> How to upload artifacts:
> https://support.pivotal.io/hc/en-us/articles/204369073
> How to escalate a ticket:
> https://support.pivotal.io/hc/en-us/articles/203809556
>
> [image: support] <https://support.pivotal.io/> [image: twitter]
> <https://twitter.com/pivotal> [image: linkedin]
> <https://www.linkedin.com/company/3048967> [image: facebook]
> <https://www.facebook.com/pivotalsoftware> [image: google plus]
> <https://plus.google.com/+Pivotal> [image: youtube]
> <https://www.youtube.com/playlist?list=PLAdzTan_eSPScpj2J50ErtzR9ANSzv3kl>
