Hey Guys, good to see its ongoing the discussion About another release. I know that I already said that but I want to point it up again. As said, I also think that 4 releases a year is possible, where we focus on good NetCat process on the major releases (11, 12, 13, etc.) and not that much process on the minor releases (11.1, 12.1, etc.). And also Patches should/could be possible. So when there are some tickets that are related to a major release and we don’t want to postpone the release, why not making a patch release (NetBeans 11 Patch1, Patch2, etc.) or Bugfixing (NetBeans 11.0.1, NetBeans 11.0.2). So patches and bugfix versions should only have bug fixes which are really needed/critical/blocker or whatever.
At the Moment, why I think it was a bit to much pressure are 2 things: 1. Getting major releases everytime while we are still in donation phase. So in my point of view, I think we will have less stress after all of the donation from Oracle is done. 2. A very long process, that we don’t want to cut or postponed for NetCAT So all in all, I think after all the donation it will be less stress IMHO and we will have more time for other Things to work/Focus on. I’m also for 11.1 for this I can add the package.json Icon finally. Unfortunately, I couldn’t find time to work on further but it would be sad if we will only have it for NetBeans 12. Only my 2 cents and yes I know, it is my Problem that the stuff is not going into NetBeans 11. Cheers Chris Von: Geertjan Wielenga Gesendet: Dienstag, 26. März 2019 12:07 An: dev Betreff: Re: [DISCUSSION] Apache NetBeans 11.1 Development If we do 11.1, it would be in June, i.e., 3 months after 11.0 and 3 months before 12.0: https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+Roadmap (Or we could simply call it 12.0, personally I don't mind so much about numbers.) It would contain whatever we have in master at the time of the release, i.e., cut a release branch in 3 months containing whatever we have there. It would also be a good opportunity for a brand new release manager (Eirik? Neil? Sven?, i.e., several candidates spring to mind) to cut their teeth on a small release, i.e., there wouldn't be heaps of new licenses, new modules, new donations, new features. Instead, it would be a small release -- and we could focus on fixing bugs, which is sorely needed. Gj On Tue, Mar 26, 2019 at 9:59 AM Laszlo Kishalmi <laszlo.kisha...@gmail.com> wrote: > Well, in order to have smaller incremental time-based releases, we have > to work on our release process first. > > I think 4 releases a year is kind of doable if we have the RM capacity > to do that (the one major, one bugfix is probably not that important > regarding that). Right now the release process is consists of 30 steps, > from which ~15 requires code changes in the release branch beside the > usual cherry-picks. > > It is just FYI. So currently it is not a lightweight task to cut a > release right from the master. > > On 3/25/19 10:23 AM, Geertjan Wielenga wrote: > > I have been thinking differently about this ‘capacity’ item. In summary, > I > > think it will be easier to release 4 times per year than 2 times per > year, > > precisely because of the capacity item. Dealing with smaller incremental > > fixed date releases will I believe simplify rather than complexify > things. > > Neil C Smith did a good job of helping me see this perspective at Fosdem > > recently and I hope I summarized him correctly but this is how I have > come > > to see it. > > > > Gj > > > > > > On Mon, 25 Mar 2019 at 18:08, Matthias Bläsing < > mblaes...@doppel-helix.eu> > > wrote: > > > >> Hi Laszlo, > >> > >> Am Sonntag, den 24.03.2019, 14:29 -0700 schrieb Laszlo Kishalmi: > >>> While we are doing the voting round, I think we need to think about > >>> NetBeans 11.1. > >>> > >>> Are we planning continue do cherry-picking into the release branch for > >>> 11.1 or do something more sophisticated? I mean 11.1 would be only some > >>> patch release or bringing some new things as well, like I'm planning to > >>> donate my Gradle support for Java EE projects. > >>> > >>> So any idea? > >> my understanding was, that in 6 months (or whatever amount), we will > >> release netbeans 12 with whatever was integrated into master. I think > >> Gradle support for Java EE would fill that bill perfectly. > >> > >> Do we really have the capacity to release 12 and 11.1? I don't think > >> so. > >> > >> Greetings > >> > >> Matthias > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > >> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > >> > >> For further information about the NetBeans mailing lists, visit: > >> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > >> > >> > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
