Hi Neil, Great.
Just one thing — I realize we’re no longer tied to being in sync with the JDK release schedule, which is great and so on, but on the other hand if tweaking the schedule slightly so that we can sync with JDK releases anyway (not a bad thing in principle, since NetBeans is itself built in Java and not some other language or technology and hence undeniably on a technology level has a closer affinity to Java than anything else), then I think we should consiser that. For example, even though we could agree on the schedule exactly as proposed by Neil, we could commit to providing a Beta release in sync with the release of a JDK release, if that release is not too far off our release dates as proposed by Neil. So, practically, Neil suggests an October release and since the next JDK is scheduled for September, we could focus on a Beta of the NetBeans release in sync with that. So, note I’m not pushing for us to be in sync with JDK releases. Instead, I’m suggesting that if a JDK is set to be released in the neighborhood of one of our releases, we could target a Beta release, where that makes sense, to be released as close as possible to that JDK release date. Gj On Thu, 23 May 2019 at 14:29, Victor Corral <[email protected]> wrote: > HARD At WORKNOT > Lazy Consensus > > On Thu, May 23, 2019 at 5:15 AM Victor Corral <[email protected]> wrote: > > > please give me a minute to catch up im only an individual and you have no > > idea how much i reall have on my plate. Im trying to get a hold of the > > president im configuring my domain im about to purchase champion.android > > from the eu. Im learning about how to file for securities in my state, im > > building my bitcoin-core for my clearinghouse proiject andf more but im > > almost where i want to be to maybe ionpress the WORLD!!!!!!! > > > > On Thu, May 23, 2019 at 2:22 AM Neil C Smith <[email protected]> > > wrote: > > > >> Hi, > >> > >> OK, as requested I'm starting a lazy consensus thread] following the > >> discussion thread on draft release schedule - > >> > >> > >> > https://lists.apache.org/thread.html/ea5189b51477cfca2b18e9c122872d36ab3ef6d9babf27c4aa649c3d@%3Cdev.netbeans.apache.org%3E > >> https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule > >> > >> This is to get consensus on the following broad points and specifics > >> that affect how / when we release NB 11.1, and how we present it to > >> users. Other aspects of the release plan are definitely still up for > >> discussion and modifications as necessary. If you have any objections > >> or things to clarify, please respond here by Tues May 28th. > >> > >> General > >> > >> * Four releases a year - mid-January, mid-April, mid-July, mid October. > >> * One release a year (April), starting with NB 11.0, is an LTS that > >> will be kept available until following April. > >> * Only LTS has a full NetCAT process, and an emphasis on stability > >> over features. > >> * Each release has a feature freeze date one month in advance, two > >> months in the case of LTS to fit in NetCAT. > >> * All commits to master are intended for the release - only required > >> PRs should be merged between feature-freeze and release dates. Master > >> should always be releasable. > >> * Major number is increased with LTS - so NB 12.0 will be in April 2020. > >> * Critical and security updates may be pushed via UC to last and LTS > >> release - otherwise releases are not expected to get new features. > >> > >> NB 11.1 -> 11.2 specifics > >> > >> * NB 11.1 release date will be ~15th July. > >> * NB 11.1 feature freeze date will be 15th June. Features for NB 11.1 > >> should be merged by that date. > >> * NB 11.1 beta(s) will be made available for testing as soon as > >> possible after feature freeze date. > >> * NB 11.2 merge window will open after 15th July release, with > >> currently intended feature freeze ~15th Sept and release ~15th Oct > >> * NB 11.0 will remain available alongside NB 11.1, 11.2 or 11.3 until > >> NB 12.0 is released in April 2020. > >> > >> Open questions > >> > >> * Jan raised important point of whether freezing master hinders > >> development, and whether we need a "next" branch. I would suggest we > >> start with freezing master and review after NB 11.1 release, but > >> during release process if it becomes a real problem. Personally I > >> think it would be worth considering feature branches for this that can > >> be merged and closed. If we do have a long-lived "next" branch and > >> end up cherry-picking from it to master do we gain anything or are we > >> better continuing with cherry-picking to release branches? > >> > >> * Glenn raised important issue on NetCAT scheduling / test-spec > >> review. How that fits in the draft schedule definitely needs > >> reviewing, although I don't think it affects the other key dates, and > >> doesn't have a direct NB 11.1 implication(?) > >> > >> Thanks and 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 > >> > >> > >> > >> >
