Moving some discussion points / questions off the lazy consensus threads ...

On Sat, 9 Oct 2021 at 14:57, Eric Bresie <ebre...@gmail.com> wrote:
> So does this mean updating source/target attributes throughout as well?

No!  It means doing that on a per module basis where strictly
necessary and reviewed, as per Jaroslav's suggestions.

> Is it possible to run any of the “java hints” across the code base and see
> where java 11 migration actions may be needed?

I don't think now is the time for that unless it involves code that no
longer functions in later JDKs?!

On Sat, 9 Oct 2021 at 15:34, Eric Bresie <ebre...@gmail.com> wrote:
> With no longer providing LTS (or is that just none presently planned),

As written they amount to the same thing.  The thing about lazy
consensus is that generally you can -1 if you're willing to step up
and work on an alternative.  Despite Laszlo's great work on a couple
of updates, we don't really have anyone still working on triaging
issues, backporting and doing updates to really justify us calling it
an LTS.  So, at least in my opinion, as and until a small group of
people want to volunteer to do that and make an LTS work (and define
what LTS means), we're not really in any position to provide one.

> what
> about the NETCAT teams role?  I could be wrong, but as I recall NETCAT
> testing tended to be more done as part of LTS releases.  Would that no
> longer be the case?

To be decided.  Various options have been discussed in the past.  We
could open up the tests for all beta testers, or run different tribes
on different releases, or stop it entirely, or ....  I left it out
again, because I've no idea what option would pass consensus at the
moment.  Or, quite frankly, even what I think we should do.

> Assume some of the NETCAT type testing may be somewhat addressed by
> automated CI testing but not sure if that’s the whole story.

Definitely not! :-)

> What is meant by “archived” here?
>
> * NetBeans 12.0 will be archived from the point of NetBeans 12.6 release.
>
> Is this notionally like saying it’s no longer supported, artifacts will be
> moved out of the mainline view/context (i.e. web pages showing as “old”
> archived builds)?  Is this treated similar to the Netbeans 8.x releases
> pre-Apache?

No, treated the same as every previous Apache release - eg. same thing
as everything before 12.5.  Moved off mirrors to ASF archive, not
included on main download pages, etc.

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



Reply via email to