One of the really nice features of NB has been the fact that you can run dozens of versions installed in parallel (I usually only have not more than four).
I grew accustomed to living on the nightly builds and, fortunately, if one doesn't work you run "uninstall" and wait a couple of days and try again...assuming you are interested in the new feature usually announced by Gj in one of his blog entries. Seems like a few days before a new "version" release the nightly builds were not available while the release version was pulled together. I found this procedure to be very handy. Seems like this process could still be done with Git/Apache....why not? I think it's unique and I'm not aware any of the competitors who provide that service (maybe Eclipse does -- not sure). As I write Jenkins is building #473 and I'm running on #470. Maybe we just need to make the Jenkins builds more obvious for those of us who like to bleed and keep the "versions" on a cadence that is convenient for developers. What is best for developers? My $.02. On Tue, Jun 26, 2018 at 2:12 PM, Sven Reimers <[email protected]> wrote: > Hi all, > > I like the overall concept - just some small things. > > 1. Having people wait for critical bugfixes for 6 months is quite long - > can we do better? > > 2. Do we plan to do update releases, e.g. 9.1, or 9.0 patch 1 (as before) > with just some cherrypicked stuff onto the existing release base branch? > How does this fit in with NetCAT, e.g. just do some sanity checks for the > patch release? > > Just my 2€c > > -Sven >
