[DISCUSS] Planning for next release 1.20.0-incubating

[Matteo Merli <mm...@apache.org>]

Since the first release is out, I'd like to get started on the discussion
for the next one :)

I propose to try to keep a monthly cadence for releases so that we can
quickly iterate over new feature and bug fixes, and avoid having to
create to many patch releases in between, which can be time consuming.

Also, I'd like to get some planning upfront, for determine the date and
then each contributor can comment on which major changes he wants to
target for inclusion in next release.

That should give a good level of transparency and clarity on the
expectations.

Finally, we should start a rotation between committers for the role of
"release manager", the one who will help coordinate the whole process
of the release.

Since I've already done the first release, who wants to do next?


Matteo
-- 
Matteo Merli
<mm...@apache.org>

Re: [DISCUSS] Planning for next release 1.20.0-incubating

[Matteo Merli <ma...@gmail.com>]

Nice, should we target for the first half of September? Also it would be
good to have all major changes merged around ~1 week before the release, to
avoid last-minute surprises.



On Thu, Aug 10, 2017 at 5:58 PM Joe F <jo...@apache.org> wrote:

> I can fill in for one release
>
> Joe
>
-- 
Matteo Merli
<mm...@apache.org>

Re: [DISCUSS] Planning for next release 1.20.0-incubating

[Joe F <jo...@apache.org>]

I can fill in for one release

Joe

On Aug 10, 2017 3:14 PM, "Matteo Merli" <mm...@apache.org> wrote:

> Since the first release is out, I'd like to get started on the discussion
> for the next one :)
>
> I propose to try to keep a monthly cadence for releases so that we can
> quickly iterate over new feature and bug fixes, and avoid having to
> create to many patch releases in between, which can be time consuming.
>
> Also, I'd like to get some planning upfront, for determine the date and
> then each contributor can comment on which major changes he wants to
> target for inclusion in next release.
>
> That should give a good level of transparency and clarity on the
> expectations.
>
> Finally, we should start a rotation between committers for the role of
> "release manager", the one who will help coordinate the whole process
> of the release.
>
> Since I've already done the first release, who wants to do next?
>
>
> Matteo
> --
> Matteo Merli
> <mm...@apache.org>
>