Hi,
I was thinking that this is a great opportunity for branding and/or
renaming the platform, making emphasis that the platform is IDE
agnostic, and that it can be used to build any sort of desktop applications.
For instance, we could name the platform as "Apache NetBeans Platform"
(ANP), or "Apache NetBeans Application Platform" (ANAP), or "Apache
NetBeans Desktop Application Platform" (ANDAP), or "Apache NetBeans
Awesome Platform for building Flipping Modular Desktop Applications"
(ANAPFMDA), or whatever, instead of just "Apache NetBeans 9.0 Alpha".
The object being to make it clear that you can use the NetBeans Platform
to build any kind of applications, not just IDEs, and making it clear
that Apache NetBeans is much more than an IDE.
Choosing a name that is easy to find in search engines would be a plus.
Cheers,
Antonio
P.S.: IntelliJ started blogging about their platform on June 2017, they
even have a specific Twitter account:
https://blog.jetbrains.com/platform/2017/06/introducing-jetbrains-platform-blog-and-twitter-for-plugin-developers/
El 05/11/17 a las 20:22, Geertjan Wielenga escribió:
Here's the proposal, at the start of this thread:
- Apache NetBeans 9.0 Alpha -- NetBeans Platform only (i.e., only the core
modules, possibly without JavaHelp). In this way, we'll have worked through
the process for a coherent part of Apache NetBeans and will only have
JavaHelp and SwingLayout to deal with in terms of GPL. (I believe SwingX is
not applicable to the platform, but the IDE.)
- Apache NetBeans 9.0 Beta -- Everything currently in Apache NetBeans Git,
i.e., the above and then also including all the other clusters currently
there, i.e., Java SE tooling.
- Apache NetBeans 9.0 -- All of the above, including NetCAT involvement.
This will be the officially tested version of Apache NetBeans.
Gj
On Sun, Nov 5, 2017 at 8:20 PM, Geertjan Wielenga <
[email protected]> wrote:
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
