This is currently filtred by API Changes label (because it was too big) with no much formatting but this count since release Apache NetBeans 11.1-beta1 pre release I guess we can make the draft based on release140 branches (it will be some direct commit to adjust as it's not working on forks) but thanks to Michael we can rerun in the actions tab.
Is it important to keep the rc tag of unreleased material ? (we have tracks on the json) (completly forgot to tag for 14 oups) Eric -----Message d'origine----- De : Neil C Smith <> Envoyé : mercredi 8 juin 2022 12:06 À : [email protected] Objet : Re: List of fixes for Apache NetBeans 14 On Wed, 8 Jun 2022 at 09:17, Eric Barboni <[email protected]> wrote: > Hi I would like to try the drafter but it implies tagging release in > github. I asked on the ml with no response not sure we can do that Might be worth sharing https://github.com/apache/netbeans/releases/tag/untagged-10fff99a5a1f406ad460 This is akin to what it will give us? Marking tags for our releases as GH releases is a good idea, as long as we can keep the RC tags not marked as releases. Using the UI "Create release from tag" button as at https://github.com/apache/netbeans/releases/tag/13 after tagging probably? Can release drafter handle our branching structure? ie. will it pick up only changes from one tagged release to the next across different branches? 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 --------------------------------------------------------------------- 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
