Hi Neil, I want to do like you did as I think it's a good way to do. I'm not sure to clearly understand the workflow in with git. It seems that you are using directly the apache git and not a fork.
Will try to document in the confluence page. To make it easy for future. Best Regards Eric -----Message d'origine----- De : Neil C Smith <neilcsm...@apache.org> Envoyé : lundi 27 janvier 2020 14:54 À : dev <dev@netbeans.apache.org> Objet : Re: Apache NetBeans 11.3-beta1 is ... available for testing ! On Mon, 27 Jan 2020 at 13:45, Eric Barboni <sk...@apache.org> wrote: > To make beta2, the correct way to do is to merge to master and get the diff > from branch release113 to master as a PR ? Up to you. I did the last two using PRs from master to release11x. It has the benefit of seeing everything in one place, providing a link to all changes, and running Travis tests against the release branch. eg. https://github.com/apache/netbeans/pull/1539 I also tended to open the PR before it was required, after first master merge, it'll update as master is updated. Picked up a couple of minor issues in 11.1 process that way, although much less (no) divergence now. Best wishes, Neil --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org For additional commands, e-mail: dev-h...@netbeans.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.apache.org For additional commands, e-mail: dev-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
