On Wed, Mar 27, 2019 at 4:10 PM Mark Struberg <strub...@yahoo.de.invalid> wrote:
> +1 > Or is it mostly about a 'full distribution for users'? > In which case it might probably be possible to just do a svn cp from the > old version to a patch-version (e.g. netbeans-11rc4.1).svn cp does not cost > any space. It's merely a reference. Like a symlink on the file system.Then > just change the one file and be done. > Is that what you were thinking of? > I guess the idea is that if we need to patch a handful of files in one or a few modules, it seems wasteful to release the whole IDE (because the sources are about a 100MB and the convenience binaries even more; and the reviewers would need to review several tens of thousands of files in the release, vast majority of which didn't really change). But, as NetBeans is a modular application, what we can do is to create a release (source zip) with just the changed modules. Which should be fairly small, in most cases. And also create convenience binaries and publish them, so that users that are using convenience binaries can easily upgrade their IDE (without downloading and installing whole new IDE). I assume this is overall OK. There is a question where exactly place the convenience binary, there are several options, including: -replace the "old" convenience binary with the new one. As a particular example, say we are producing an update for module java/java.source for Apache NetBeans 10.0. Can we replace the "org-netbeans-modules-java-source.nbm" file under the existing: https://www-eu.apache.org/dist/incubator/netbeans/incubating-netbeans/incubating-10.0/nbms/java/ -we could create a new directory, say incubating-10.0p1/nbms which would contain only "org-netbeans-modules-java-source.nbm", an updated catalog.xml, which would mostly refer to the files from incubating-10.0/nbms (+.gz of the catalog.xml) (and possibly tasks.jar) -as Mark is noting, we could svn cp the NBMs from 10.0/nbms to 10.0p1/nbms (although this feels like it might be more manual work). Jan > LieGrue,strub > > On Wednesday, 27 March 2019, 11:01:20 CET, Bertrand Delacretaz < > bdelacre...@apache.org> wrote: > > Hi, > > On Sun, Mar 24, 2019 at 11:16 AM Laszlo Kishalmi > <laszlo.kisha...@gmail.com> wrote: > > ...Regarding that we are right now voting on the whole source code before > > releases, how shall we handle patch releases of a module?... > > Assuming a patch is a set of source files it can be handled like any > other Apache Release. > > Nothing says that an Apache Release needs to be a complete > application, it's just a set of source code files. > > -Bertrand > > --------------------------------------------------------------------- > 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 > > > >
