Well, the Gradle patch has been made in the following way:
1. The result of the release build has been further processed,
extracting the source files for the changed modules and the necessary
files like NOTICE and licenses.
2. So the output of the patch build was a small source zip and the
corresponding nbm-s as binary. The README had the instruction that how
you need to paths the existing source bundle with the new one to create
the binaries.
3. We voted on the source files only
4. The nbms were overwritten in the distribution directory and the
updates.xml.gz was patched by hand.
Probably the ugliest part was the actual release of the nbms. In the
future we could create a separate update center for release updates and
ship that configured in the release. I think the new plugin portal
infrastructure probably could help, if that'd support multi tenancy.
On 10/23/19 5:51 AM, Neil C Smith wrote:
On Wed, 23 Oct 2019 at 13:47, Geertjan Wielenga <geert...@apache.org> wrote:
Will we really need to go through a vote process for this change?
IMO, yes - it's still a source change. And that's not quite the only
change required.
But there are other things we might want to make patches for too.
This thread was not meant to be specific to that one particular issue.
We need to work out a process for how we do this in future.
Best wishes,
Neil
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
