sounds good to me.
We could skip 1.2 if you want and go right to master and develop it
there, no?
Regarding testing... As you probably know, github actions build the
'release' cluster config in a matrix, compress the whole workspace it
and use this as artifact for all secondary test jobs (rust would be one
of them).
This artifact won't have rust in it (for now at least).
a) The easiest way to solve this would be to create a
'release_plus_rust' cluster config and build this in the primary job
instead, anticipating that one day rust will be in the 'release' config.
we do also have a "full" cluster config, which we could use for this
purpose.
b) Alternative would be to sideline everything and build + test the rust
cluster isolated in a job. This sounds like the obvious solution at
first but has the consequence that a lot of jobs won't see the rust
modules, e.g commit validation, paperwork checks (sigs, libs, licenses
etc) since those work with the build artifact I believe (but I could be
wrong).
best regards,
michael
On 21.02.23 21:26, Antonio wrote:
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<[email protected]> 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: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
