On Thu, 11 Jul 2019 at 09:18, Geertjan Wielenga <[email protected]> wrote: > We should just document the various features that aren’t quite right yet > and create issues for them. If we don’t, this is potentially the start of a > very significant slip that we can’t afford.
Agreed, particularly now I can get into JIRA and see mention of the workaround. It's also not been marked with 11.1(!). and only classed as major (which seems accurate per https://cwiki.apache.org/confluence/display/NETBEANS/Bug+Priority+Guidelines ) Creating the voting candidates (affectively the releases) is significantly more time consuming than the betas. More so when you're still learning and have to rewrite half the docs because we're out of incubation. :-) Of course, if I've screwed something up in that process and we need a second VC anyway then we should consider this. But, in general, we're going to have a month of betas (two for LTS) before releases, and that's the time we should be picking up functionality issues. And a voting candidate for release won't be made if there are blocker or critical issues assigned to the release. Ideally we'll only need one actual voting thread per release, unless a critical or blocker crops up during the vote (particularly around checking Apache release requirements). None of this precludes your right to -1 but given also Geertjan's point above my intention is to keep the vote thread live for the full 72hrs unless a blocking or critical is found in the meantime. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
