sofie204 commented on PR #871: URL: https://github.com/apache/flink-web/pull/871#issuecomment-5006501109
@davidradl Thanks for helping resolve this issue David @snuyanzin: On how topics were picked, the selection of topics, FLIPs, tickets, etc was a manual process that came from a sweep of the dev@ archive (all the [VOTE]/[RESULT]/[ANNOUNCEMENT] threads from april–june), the 2.3.0 release announcement (because of the impact to users), and a cross-reference against the most recent community update which would be April, I included all these items into a sort of inventory spreadsheet with the links to the post, FLIPs and relevant Jira pages. The idea was to rank them based on the impact of the change and the relevance as well (I read through the flips in order to determine the relevance). the reason why the items you listed got missed was that my focus was skewed towards the vote threads, announcements and major FLIPs and as a result, the work that lives only at the Jira level like the ones you linked above the calcite upgrade, json parse reuse, did not enter into the list. Especially when they are not in the 2.3.0 release version. The community announcements scope is "the changes we think matter most across April - June" so my aim was not full coverage but rather things that are most impactful and the way i determined that is what I stated above. I will take a look at what you linked above. Based on my process, it's clear that the individual Jira tickets with 2.4.0 labels are a part that I missed. That said, with three months of activity across a project this size, some judgment calls are going to be made as this update can't cover everything. What I will commit to is applying the same criteria to everything that gets flagged like you have just done. So where some items may not meet the bar for user impact then the release notes and Jira include the complete record. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
