Re: Submit bug report
Hi Alexis, Please see [1] for instructions & links on how to submit bug reports. Anyway maybe you've found a feature, and not a bug ;-). Maybe you want to tell us a little bit about the problem before creating an issue in JIRA, thay may save you some time. Kind regards, Antonio [1] http://netbeans.apache.org/participate/report-issue.html On 17/04/18 11:13, Alexius Diakogiannis wrote: Dear all, I 've found a bug regarding Netbeans and new Fedora 27. How can I submit it? Thanks *Alexius Diakogiannis, CSM* *Archer / Linux Lover / Java Geek* *About me*: https://about.me/diakogiannis/ *Linked In*: https://www.linkedin.com/in/diakogiannis/ *Blog:* https://www.jee.gr - 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
Re: Time to branch for the release candidate?
+1 to Chris / Neil You shouldn't be developing in master, ideally On Tue, 17 Apr 2018, 15:10 Christian Lenz, wrote: > Master shouldn’t be that one, where the wild development is going on. > Master should be that one which is already live. > In General, what gitflow does. Wild development is going on on the dev > branch, for the next release. If whatever is finished, there is a release > branch. After that, it will merged into master and created a tag. > > If this is not possible, then an other solution is that develop stays > clean and always releasable. You only work on Feature branches. After the > Feature is finished and ready to go, it will merged into develop. Someday > you can create a release branch of develop. > > > Cheer > > Chris > > Von: Neil C Smith > Gesendet: Dienstag, 17. April 2018 14:53 > An: dev@netbeans.incubator.apache.org > Betreff: Re: Time to branch for the release candidate? > > On Tue, 17 Apr 2018 at 12:10 Jaroslav Tulach > 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 > -- > Neil C Smith > Artist & Technologist > www.neilcsmith.net > > Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org > >
AW: Time to branch for the release candidate?
Master shouldn’t be that one, where the wild development is going on. Master should be that one which is already live. In General, what gitflow does. Wild development is going on on the dev branch, for the next release. If whatever is finished, there is a release branch. After that, it will merged into master and created a tag. If this is not possible, then an other solution is that develop stays clean and always releasable. You only work on Feature branches. After the Feature is finished and ready to go, it will merged into develop. Someday you can create a release branch of develop. Cheer Chris Von: Neil C Smith Gesendet: Dienstag, 17. April 2018 14:53 An: dev@netbeans.incubator.apache.org Betreff: Re: Time to branch for the release candidate? On Tue, 17 Apr 2018 at 12:10 Jaroslav Tulach 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 -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: Time to branch for the release candidate?
On Tue, 17 Apr 2018 at 12:10 Jaroslav Tulach 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 -- Neil C Smith Artist & Technologist www.neilcsmith.net Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: Time to branch for the release candidate?
+1 for branching Sven John McDonnell schrieb am Di., 17. Apr. 2018, 14:08: > I agree, > > But we need to make sure that only agreed/safe fixes get merged into the > release candidate. Whats the criteria to use? Only accept blocking bug > fixes? > > John > > On 17 April 2018 at 12:10, Jaroslav Tulach > 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. > > > > Maybe this is an overkill, but it would make me feel safer. > > -jt > > > > > > 2018-04-17 13:04 GMT+02:00 Geertjan Wielenga < > > geertjan.wiele...@googlemail.com>: > > > > > Hi all, > > > > > > Is it time to create a branch for the release candidate? > > > > > > If yes, or after questions and discussions, who will do it? > > > > > > Thanks, > > > > > > Gj > > > > > >
Re: Time to branch for the release candidate?
I agree, But we need to make sure that only agreed/safe fixes get merged into the release candidate. Whats the criteria to use? Only accept blocking bug fixes? John On 17 April 2018 at 12:10, Jaroslav Tulach 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. > > Maybe this is an overkill, but it would make me feel safer. > -jt > > > 2018-04-17 13:04 GMT+02:00 Geertjan Wielenga < > geertjan.wiele...@googlemail.com>: > > > Hi all, > > > > Is it time to create a branch for the release candidate? > > > > If yes, or after questions and discussions, who will do it? > > > > Thanks, > > > > Gj > > >
Re: Time to branch for the release candidate?
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. Maybe this is an overkill, but it would make me feel safer. -jt 2018-04-17 13:04 GMT+02:00 Geertjan Wielenga < geertjan.wiele...@googlemail.com>: > Hi all, > > Is it time to create a branch for the release candidate? > > If yes, or after questions and discussions, who will do it? > > Thanks, > > Gj >
Time to branch for the release candidate?
Hi all, Is it time to create a branch for the release candidate? If yes, or after questions and discussions, who will do it? Thanks, Gj
Submit bug report
Dear all, I 've found a bug regarding Netbeans and new Fedora 27. How can I submit it? Thanks *Alexius Diakogiannis, CSM* *Archer / Linux Lover / Java Geek* *About me*: https://about.me/diakogiannis/ *Linked In*: https://www.linkedin.com/in/diakogiannis/ *Blog:* https://www.jee.gr
