So are milestones added before (leading up to a release) or after (tagging PRs included/merged) into the actual release?
Would a "milestone r - candidate" tag/milestone be valuable as an "up front" to help collect of possible candidate PRs for a coming release as a way of a given PR author as saying "I want this to be included into the next release"? Or would it be tagged for the release even if it doesn't get included (I assume at that point the milestone would be removed by the release manager or applicable authority)? Or would the tagging be done during the PR completion activity (i.e. once PR is completed, accepted [and merged?]) it would be tagged in the applicable milestone release and merged into main (or a release branch)? The above someone has the ability to tag things to a given milestone (i.e. not new committers/contributors without the ability). Eric Bresie [email protected] On Thu, Dec 1, 2022 at 5:51 AM Jean-Marc Borer <[email protected]> wrote: > > > > Short answer, yes - eg. link on all release candidate emails > > https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16 > > > I didn't know that one. Milestones are a cool way to mark specific merges > > Longer answer, there is some work going on to better categorize all > > this - eg. https://github.com/apache/netbeans/releases The draft one > > particularly, but that's private. > > > That is what I was looking for, but this list is not available until a few > days before the release, right? > > Not recently. What prompted the question? > > > > We were wondering if there is a kind of a road map of planned new features > people agreed to work on. > Moreover in our company, when we foresee to release a given feature for a > specific version, we tag it even long before the final release. We were > looking for such an equivalent in the NB project. > > I think that is exactly the purpose of milestones. > > Thx for your answers > > On Wed, Nov 30, 2022 at 3:09 PM Neil C Smith <[email protected]> > wrote: > > > On Wed, 30 Nov 2022 at 15:02, Jean-Marc Borer <[email protected]> wrote: > > > Ok, so does it mean, that I have to check Github history to find out > what > > > is in a upcoming release (16 for example)? > > > > Short answer, yes - eg. link on all release candidate emails > > https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16 > > > > Longer answer, there is some work going on to better categorize all > > this - eg. https://github.com/apache/netbeans/releases The draft one > > particularly, but that's private. > > > > > > > Am I missing something or did something change for the release > > > > management? > > > > Not recently. What prompted the question? > > > > 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 > > > > > > > > >
