[REMINDER] Ensuring build stability

[Gary Yao <ga...@ververica.com>]

Hi community,

We created the builds@flink.apache.org mailing list as an effort to be more
transparent about build instabilities, especially about issues that were
only
surfacing in CRON builds at the time, such as, Scala 2.12 and Java 9
compilation errors.

While the situation has gotten better, there still occasionally issues
concerning the CRON builds that are reported late (e.g., [1][2]). The
mailing
list was created almost 2 months ago. However, last time Chesnay checked,
there were only 21 subscribers. To continue the high quality of our
releases,
we should aim at keeping the master and the release branches stable at all
times. Therefore, I encourage everyone who is developing Flink to monitor
the
builds mailing list. To subscribe, all you need to do is to send an empty
email to:

    builds-subscribe@flink.apache.org

Best,
Gary

[1] https://issues.apache.org/jira/browse/FLINK-14186
[2] https://issues.apache.org/jira/browse/FLINK-14226

Re: [REMINDER] Ensuring build stability

[Jark Wu <im...@gmail.com>]

+1 to encourage every developer to subscribe builds@f.a.o and welcome any
suggestions about the builds notification.

I think everyone should pay more attention on the failed builds, not only
the one who merged commits. The build is still not stable.
If you find a failed test case from the failed builds, you can search in
the JIRA[1] by the test name to see whether there is already a issue
created.
If there is not, it would be great to create one (and can cc who is
familiar with this if you know).
If there is one, you can attach the new failed build log link under the
JIRA issue to give more clues.

Best,
Jark

[1]:
https://issues.apache.org/jira/browse/FLINK-14402?jql=project%20%3D%20FLINK%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20text%20~%20%22testOneToOneAtLeastOnceRegularSink%22%20ORDER%20BY%20createdDate%20DESC

On Fri, 18 Oct 2019 at 20:45, Gary Yao <ga...@ververica.com> wrote:

> Hi community,
>
> We created the builds@flink.apache.org mailing list as an effort to be
> more
> transparent about build instabilities, especially about issues that were
> only
> surfacing in CRON builds at the time, such as, Scala 2.12 and Java 9
> compilation errors.
>
> While the situation has gotten better, there still occasionally issues
> concerning the CRON builds that are reported late (e.g., [1][2]). The
> mailing
> list was created almost 2 months ago. However, last time Chesnay checked,
> there were only 21 subscribers. To continue the high quality of our
> releases,
> we should aim at keeping the master and the release branches stable at all
> times. Therefore, I encourage everyone who is developing Flink to monitor
> the
> builds mailing list. To subscribe, all you need to do is to send an empty
> email to:
>
>     builds-subscribe@flink.apache.org
>
> Best,
> Gary
>
> [1] https://issues.apache.org/jira/browse/FLINK-14186
> [2] https://issues.apache.org/jira/browse/FLINK-14226
>