Hey Jan,

sounds like a great idea. I don’t know exactly how it was before at Oracle, but 
afaik when there are patch updates or smth similar, NetBeans noticed that right 
from the IDE and I could update it right from the IDE w/o building the whole 
IDE by the source or whatever. Only to let you know that, that I prefer the 
same old way as for Oracle, if possible. Yes that means to override existing 
nbm files. Or yes, Maybe with the update center.

A changelog should be also a must have, that the user see what changed, why was 
there an update etc.


Cheers

Chris


Von: Jan Lahoda
Gesendet: Dienstag, 26. März 2019 20:08
An: dev@netbeans.incubator.apache.org
Betreff: Re: [MENTORS] Partial/Patch releases

Hi,

My personal opinion:
I think it'd be awesome if we could release updates to just some modules
(and do that with less overhead than the full release).

With some work, we might be able to create a source zip (i.e. a release
candidate) for individual module(s). One tricky part of that is we need a
README with a description of what it does (we should be able to generate
LICENSE/NOTICE, so these are likely a smaller problem). I'd personally be
fine if we said "to build this module, please download the already released
full source code, replace the module(s) and build." (so that we wouldn't
need much changes to the build infrastructure to do the actual build).

For the convenience binary, I think it would be best if we could overwrite
the existing NBM on the existing update centre directory. But if not
possible, it might be possible to create a convenience binary consisting of
the NBM+the update centre catalog (the .xml) pointing to the convenience
binary NBMs from the last/previous full release.

Jan


On Sun, Mar 24, 2019 at 11:16 AM Laszlo Kishalmi <laszlo.kisha...@gmail.com>
wrote:

> Dear Mentors,
>
> NetBeans is a big modular project. It has the infrastructure to deliver
> patches on module level.
>
> It is quite plausible that as we are going to have more modules
> included, we need to release critical bugfixes in form of patch releases
> some modules.
>
> Regarding that we are right now voting on the whole source code before
> releases, how shall we handle patch releases of a module?
>
> Also the most consumable format of these patches are convenience binary
> format nbm modules which is currently backed up by Apache infra for
> distribution. That would mean we would overwrite some files in the
> release folder.
>
> So my question, how is it possible do partial releases (based on
> modules) inside Apache?
>
> Laszlo Kishalmi
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Reply via email to