I've gone over the tickets and removed Fix Version from many of them that
do not seem to be critical defects. If I removed Fix Version from a ticket
you care about, please feel free to add it back. I am not trying to decide
what is in/out of the release, just trying to triage the Jira data to match
expected practices.

It should probably be documented somewhere outside of the release guide. As
far as I can tell, the fact that we triage them down to zero is the only
place we mention that it is used to indicate release blockers and not used
for feature targets.

Kenn

On Wed, Oct 23, 2019 at 10:40 AM Kenneth Knowles <[email protected]> wrote:

>  Wow, 28 release blocking tickets! That is the most I've ever seen, by
> far. Many appear to be feature requests, not release-blocking defects. I
> believe this is not according to our normal best practice. The release
> cadence should not wait for features in progress, with exceptions discussed
> on dev@. As a matter of best practice, I think we should triage feature
> requests to not have Fix Version set until it has been discussed on dev@.
>
> Kenn
>
> On Wed, Oct 23, 2019 at 9:55 AM Mikhail Gryzykhin <[email protected]>
> wrote:
>
>> Hi all,
>>
>> Beam 2.17 release branch cut is scheduled today (2019/10/23) according
>> to the release calendar [1].  I'll start working on the branch cutoff
>> and later work on cherry picking blocker fixes.
>>
>> If you have release blocking issues for 2.17 please mark their "Fix
>> Version" as 2.17.0 [2]. This tag is already created in JIRA in case you
>> would like to move any non-blocking issues to that version.
>>
>> There is a decent amount of open bugs to be resolved in 2.17.0 [2] and
>> only 4 [3] are marked as blockers. Please, review those if these bugs are
>> actually to be resolved in 2.17.0 and prioritize fixes if possible.
>>
>> Any thoughts, comments, objections?
>>
>> Regards.
>> Mikhail.
>>
>>
>> [1]
>> https://calendar.google.com/calendar/embed?src=0p73sl034k80oob7seouanigd0%40group.calendar.google.com
>> [2]
>> https://issues.apache.org/jira/browse/BEAM-8457?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Reopened%2C%20Open%2C%20%22In%20Progress%22%2C%20%22Under%20Discussion%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20fixVersion%20%3D%202.17.0
>> [3]
>> https://issues.apache.org/jira/browse/BEAM-8457?jql=project%20%3D%20BEAM%20AND%20status%20in%20(Reopened%2C%20Open%2C%20%22In%20Progress%22%2C%20%22Under%20Discussion%22%2C%20%22In%20Implementation%22%2C%20%22Triage%20Needed%22)%20AND%20priority%20%3D%20Blocker%20AND%20fixVersion%20%3D%202.17.0
>>
>

Reply via email to