We're talking about an alpha release here, not beta, and not final. The html.editor module is not part of the platform, which is part of the plan for the alpha release.
There are no failing unit tests for the alpha release: https://builds.apache.org/view/Incubator%20Projects/job/incubator-netbeans-release/ Gj On Sun, Nov 5, 2017 at 8:17 PM, Matthias Bläsing <[email protected]> wrote: > Hey, > > Am Sonntag, den 05.11.2017, 19:57 +0100 schrieb Geertjan Wielenga: > > On Wed, Nov 1, 2017 at 8:21 PM, Jan Lahoda <[email protected]> wrote: > > > > > FWIW, I've started with a Jenkins job to build release artefacts, > > > for the > > > with "9.0 alpha" platform-only release here: > > > https://builds.apache.org/view/Incubator%20Projects/job/ > > > incubator-netbeans-release/ > > > > > > Please note this is still a work-in-progress. > > > > > > The idea is that the build should do very minimal checks to verify > > > releaseability. When the build passes/is blue, we could send the > > > release > > > vote e-mail. > > > > > > > > > > From #57 onwards, the build of NetBeans 9.0 Alpha (i.e., > > specifically, and > > narrowly, the NetBeans Platform) is blue: > > > > https://builds.apache.org/view/Incubator%20Projects/job/incubator-net > > beans-release/57/ > > > > That means we can send the release vote e-mail. > > I disagree. Lars send an important message: The donation from oracle > came with important files removed. One such example was the > "html.editor" module, which lost it much of its functionality because > of removed DTDs. The same is true for XML schema files and such. > > So from my POV we need to do the same as for the fixing of licenses: Go > through every module, run at least the unittests, check why they fail > and fix them. > > Netbeans was always released after NetCat - that should catch it, but I > would not release at this point. > > Greetings > > Matthias >
