Hi,

On Wed, 14 Oct 2026 at 14:52, ehsavoie <[email protected]> wrote:
> I've been playing around to use Agent Client Protocol to connect a coding
> agent into NetBeans.
...
> [1]: https://github.com/apache/netbeans/pull/9712

I put the needs-discussion label on the PR, but only just having a
chance to follow up myself.  I don't have a lot of time for NetBeans
right now, and I've been concentrating the time I do have on getting
us ready for freeze, hence reviewing and labelling.

Thanks for looking into this area.  However, I have major reservations
about merging this into the main IDE repository.  There may be a few
module changes / moves that should be there though.

IDE and platform releases are large and time consuming, mostly down to
one person (Eric) now that the release team is no longer, and really
it's enough to keep to the quarterly schedule.  Pushing updates
between releases is awkward, and with the current way the Maven
releases are architected, overly resource intensive.

Features like this, with both rapidly changing ecosystem and potential
security considerations, feel like they would benefit from a lighter
and more responsive release schedule.  It's been discussed in another
context, but I think this is another feature that would be good to
consider releasing via an official plugin repository (ie NetBeans' own
extensions).  Being in extra is pointless as it'll never be released.
Not that this appears to be in extra anyway?!  Just like Maven plugins
have their own repositories and release schedules, let's consider
which features of the IDE are better addressed in that way?

I'm also curious what the "Signed off by" line on each commit means
for the provenance of the code in this PR?

Best wishes,

Neil

---------------------------------------------------------------------
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



Reply via email to