Hi Neil,
On Fri, May 17, 2019 at 6:12 PM Neil C Smith <[email protected]> wrote:
> Hi,
>
> Quick bump, just to see if there are any further thoughts on this?
>
> If there aren't objections I'd really like to run a vote thread on
> this next week - not the whole text - lots still to discuss - just key
> points around release dates, LTS, version numbering and feature/master
> freeze. Basically anything that affects how we do the next release
>
I'd like to ask: is there a plan for a "next" branch to which one could
merge stuff for the next release while the master is closed (and which
would be automatically merged into master when the merge window would
open)? As master is going to be closed for extensive periods of time, it
feels there should be a place where work could happen (rather than managing
private branches that are effectively done, but cannot be pushed/merged
anywhere, as the master is closed).
Thanks,
Jan
> and whether we archive 11.0 or not.
>
> If we are freezing master for a month in mid-June, it would also be
> good to decide and advertise that by end of next week or so?
>
> 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
>
>
>
>
