Devs A key requirement of all Apache projects is the ability to do a regular release. Please respond to requests from Aleks (Release Manager) to fix items, remove blocking issues, as he attempts to identify the source of bugs and does quality checks.
We’ve generally been using the approach of continuous development and the release being possible at all times, but as we’ve found, this has not worked with too many changes to review for sources of build and development issues. This, in turn, suggests that we have not been sufficiently vigilant and vigorous in enforcing our PR acceptance. There is a checklist associated with each PR - PLEASE read that checklist and make sure you’re not skipping any step (code conventions, tests, link to tickets, size of code change, etc) Anyone adding a ticket now without a corresponding effort to propose a PR should expect that to be pushed to some future release. Only critical security issues will be a priority. And, we may need to hold off on additional features (tickets w ongoing PR dev) until this release happens… if we can’t get it out soon. This release is massive - spanning too long a time frame, making it correspondingly difficult to get out. Again, this is why regular (continuous?) releases are important. Thank you PMC chair Sent from Gmail Mobile
