Just for my interest, which types of people can approve Pull Requests? As we are now open source the community is deciding what's important by providing the PR's but we have quite a few stacked up. It has previously been mentioned in someone else request to get one approved that they should just sent a message to dev but that's not really a process, it's just hiding the fact there isn't really one.
Also who gets to flag an issue as 9.0, I guess in general what makes an issue relevant to a particular version or not. As we move to integrating the next code donation, there will now be two parallel streams running. Bug fixing/enhancing the current code base and integrating the new modules. What is the strategy here, branching seems like best approach here but it looks like aren't doing this. What is the plan to effectively manage the two streams? On Thu, 26 Apr 2018, 18:56 Laszlo Kishalmi, <laszlo.kisha...@gmail.com> wrote: > Well, > > I'm trying to collect the remaining things to do for 9.0 release for a > week now, from GitHub PR-s, JIRA and this mailing list. Regarding 9.0 in > numbers are the following (none may be accurate, though): > > We have 31 open PR-s in GitHub (not necessary 9.0 related) > > We have 44 open issues with PR-s. > > We have 32 open issues marked for 9.0 > > We also have 5 open issues with PR-s for 9.0 > > The issues and PRs are not really aligned. > > Well this does not necessarily means that we should not branch for > release. I just would like to say, we probably need to be more focused > on what we are doing. > > I could promise to go over the open issues and the PR-s and close those > which have merged PRs-. > > Also I feel the number of open PRs is quite high, though it might really > mean that changes that we do not want to include into 9.0 are piling up > (indicates the need of the release branch). > > Also those 5 issues with PR-s might just go into master in the following > days and we could make the release branch after that. > > So If I would vote for release branch now it would be 0/-1 right now as > we (or maybe just me) can't really see clearly on 9.0. > > > > On 04/17/2018 05:52 AM, Neil C Smith wrote: > > On Tue, 17 Apr 2018 at 12:10 Jaroslav Tulach <jaroslav.tul...@gmail.com> > > wrote: > > > >> Yeah, there are changes in the queue for the master branch that could be > >> too destabilizing. To avoid something like that to negatively influence > the > >> 9.0 release, I'd suggest to create a branch release/9.0 and put only the > >> safe fixes ready for 9.0 there. The wild development would continue in > the > >> master branch. > >> > > +1 to branching and that. Longer term perhaps a more gitflow-like system > > where PR's come into a develop branch too? > > > > A question, though - I assume this will branch off master now, not from > > the beta tag? Given that in NetCAT we were testing the beta, I assume > > there is nothing you'd consider "too destabilizing" between then and > now? > > > > Best wishes, > > > > Neil > > > --------------------------------------------------------------------- > 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 > > > >
