me too. Would prefer to have it in NB rather than as plugin since
language support is a core feature of IDEs IMO.
Having it in the main repo during dev time has also its benefits, CI,
potentially more eyes on the code etc.
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.
best regards,
michael
On 16.02.23 23:46, László Kishalmi wrote:
I'd vote for b.4 by Neil.
On Thu, Feb 16, 2023 at 12:02 PM Chris <christian.l...@gmx.net> wrote:
Hey all,
as far as I can remember, under oracle there was a time where we had a
similar process to continous deployment. That means, that it was also
possible, to release bugfixes inside the core and updates of plugins
from the core between releases. Sometimes I opened NetBeans 7.1 and
after weeks I got the info "there are updates" no 3rd-party-plugins, no
7.1 to 7.2. It was just that I had the HTML editor 1.1.1 -> 1.1.2 (just
an example, not the correct version). So what is with those approaches?
I would like to see as many stuff as possible inside the core and yes we
have problems of updating stuff, when we wait for a new release. So is
it possible to have such continous deployment after a PR was merged and
all tests are green, in between releases? That means for me, we can have
everything inside the code, rust, go, whatever and have also bugfixes
and new small features. Is this not possible under apache?
Cheers
Chris
Am 16.02.2023 um 10:20 schrieb Neil C Smith:
Hi,
On Thu, 16 Feb 2023 at 07:02, Antonio <anto...@vieiro.net.invalid>
wrote:
a) I don't think Rust support is ready yet to be merged with core:
...
b.2) Create a repo of ours and let "rust" be an experimental plugin, and
keep on improving it there.
b.4) might be to merge into master as a separate cluster, or in an
experimental cluster, and not include in the release list of clusters?
Can see pros and cons to both approaches. Having somewhere we could
develop and release (experimental) plugins from might be good. Having
the development happen here also good.
Personally see far more reason to eventually include Rust in core than
some of the more product oriented things we do have in there that
should have been kept as plugins IMO.
Best wishes,
Neil
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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
---------------------------------------------------------------------
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
