Hi all,
So to summarize, if I understand correctly:
1. We want Rust or other experimental stuff in the main repo.
1.1. I'll make a PR in a few days (once I domesticate the grammar).
1.2. We want it in a "rust" branch first to fine-tune.
1.3. Then we may want to merge "rust" to "master" in:
1.3.1. Option I: A "rust" cluster?
1.3.2. Option II: Or an "experimental" cluster?
(in any case disabled in cluster.properties)
2. We may want to release these as plugins.
Does this make sense?
Thanks,
Antonio
On 17/2/23 12:57, Neil C Smith wrote:
On Fri, 17 Feb 2023 at 11:32, Michael Bien<mbie...@gmail.com> wrote:
we could hide the feature a little bit during beta, e.g keep the modules
disabled by default and print a warning notification that this is an
experimental feature when someone enables the modules.
Possibly. Make that b.5 though! 😄 I actually meant to have in a
cluster that is not built by default or included in releases at all -
similar to contrib, but for our own in-development things. Unless
rust deserves its own cluster anyway in future?
Could still publish from there to an update centre?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
