Here's a query to find 2.29.0 issues where you are the author or reporter [1].
[1] https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20fixVersion%20%3D%202.29.0%20AND%20(assignee%20in%20(currentUser())%20OR%20reporter%20in%20(currentUser())) On Tue, Apr 27, 2021 at 9:22 PM Kenneth Knowles <[email protected]> wrote: > Hi all, > > I was just self-reviewing the blog post [1] for the 2.29.0 release > announcement. > > I have these requests, which I would appreciate if I were a user: > > * Can you browse the jiras [2] and change them between > Bug/Feature/Improvement and make sure they are relevant? In particular: > - "sub-task" is so generic; only use if it does not stand on its own > - "feature" should be something a user might care about (IMO) > - "bug" is something else a user might care about, if they are figuring > out how far they have to upgrade > - "improvement" can be changes that aren't that interesting to users > - if a test was failing for a while and we fixed it, set Fix Version = > Not Applicable since it is not really tied to a release > > * Can you take another pass and highlight things that should be on the > blog? Leave a comment on https://github.com/apache/beam/pull/14562. You > can highlight your own work or other people. A quick read makes me think a > lot is missing. The initial blog post is autogenerated from CHANGES.md but > we are not yet very good about making sure things are in that file. > > Kenn > > [1] > http://apache-beam-website-pull-requests.storage.googleapis.com/14562/blog/beam-2.29.0/index.html > [2] > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527&version=12349629 >
