Release Process

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Release Process

Dominik Bruhn
Hey everyone,
about three month ago, I made a PR [1] to the flink github project
containing a small change for the RabbitMQ source. This PR was merged
and the code is in the master.

But: This code never made it into a release. In JIRA [2], it is meant to
be released with 1.2. How is the policy here? When can I expect to see
this in the a official release? How are the rules here?

Thanks for a clarification,
Dominik

[1]: https://github.com/apache/flink/pull/2373
[2]: https://issues.apache.org/jira/browse/FLINK-4394
Reply | Threaded
Open this post in threaded view
|

Re: Release Process

Fabian Hueske-2
Hi Dominik,

the discussion about the 1.2 release was started on the dev mailing list [1] about 2 weeks ago.

So far the proposed timeline is have a release in mid December.

Best, Fabian

2016-11-03 22:50 GMT+01:00 Dominik Bruhn <[hidden email]>:
Hey everyone,
about three month ago, I made a PR [1] to the flink github project containing a small change for the RabbitMQ source. This PR was merged and the code is in the master.

But: This code never made it into a release. In JIRA [2], it is meant to be released with 1.2. How is the policy here? When can I expect to see this in the a official release? How are the rules here?

Thanks for a clarification,
Dominik

[1]: https://github.com/apache/flink/pull/2373
[2]: https://issues.apache.org/jira/browse/FLINK-4394

Reply | Threaded
Open this post in threaded view
|

Re: Release Process

Chesnay Schepler
In reply to this post by Dominik Bruhn
Hello,

Every contribution to the master branch will be released as part of the
next minor version, in your case this would be 1.2.
We are currently aiming for a release in December.

In between minor versions several bug-fix versions are released (1.1.1,
1.1.2 etc.). For these the community picks
commits to include, which is decided on the mailing list in the
discussion thread for the respective release.

Note that (afaik) no contributor scans through all recently resolved
JIRA's when these discussions starts, but generally
only adds the ones he is aware of at the moment or was directly involved
in. As such it can happen that fixes fall
through the cracks and are never included in a bug-fix release, which is
what happened here.

Regards,
Chesnay

On 03.11.2016 22:50, Dominik Bruhn wrote:

> Hey everyone,
> about three month ago, I made a PR [1] to the flink github project
> containing a small change for the RabbitMQ source. This PR was merged
> and the code is in the master.
>
> But: This code never made it into a release. In JIRA [2], it is meant
> to be released with 1.2. How is the policy here? When can I expect to
> see this in the a official release? How are the rules here?
>
> Thanks for a clarification,
> Dominik
>
> [1]: https://github.com/apache/flink/pull/2373
> [2]: https://issues.apache.org/jira/browse/FLINK-4394
>