Hi All,
A few recent emails make me think that there's at least the
possibility we'll want to consider some cherry-picked module updates
for 11.2 over the next month or so, assuming the release goes through
OK.
At present I think we've only done this once for 11.0 with the gradle
patch update? That process seemed a little unwieldy to me, and
somewhat detached from our build server?! Or maybe that's me
mis-remembering things?
I'm wondering whether if we do ship updates, we trigger a new
milestone in the release branch, and have a vote on full sources, as
per normal. Alongside that we nominate specific module convenience
binaries (nbms) to be added to the mirrors / update centre.
That seems a potentially easier way to handle this. On the downside,
it may require keeping both the original and updated source bundles on
the mirrors? I'm also wondering what the mirroring / archiving
implications of overwriting specific nbms are?
We would possibly end up with a dist structure something like -
11.2 /
11.2 source
11.2 binaries
nbms /
update centre
11.2-update1
11.2-update1 source
Any thoughts? Barking up wrong tree? :-)
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
