Re: Netbeans Vision / Roadmap

[Laszlo Kishalmi]

Well, I can share my vision:

DevOps Cluster, that would have:

  - Go, syntax highlight and parsing, no project support planned.
  - Helm Project Support, mainly project view and code completion in YAML
  - Terraform Project Support
    - Syntax Highlight in tf and tfvars files
    - TF Parsing and parser aided code completion


On 12/4/20 03:05, Eric Bresie wrote:

There has been recent discussions on vision and roadmap for Netbeans
development and the need to discuss so thought I would start a new thread
to discuss.

 From my understanding when under Oracle stewardship there more funded
individuals to support these sorts of things but now that it has been
donated to be an Apache project this now becomes the responsibility of the
community to pick this up.

In the past there has been community release / roadmaps (1) (2) and with
transition some similar Apache wiki flavors(3).

Assuming what is needed is maybe a new “Roadmap” and or “Vision” subpage on
Netbeans wiki page (4) as a starter.

Milestone could be identified based on this.

Assuming specific features, refractors, improvements would further be
captured and come in the form of existing or new JIRA tickets (5) and when
ready for acceptance then on the github project (6) a git Pull Requests
(PR) (7) and tagged towards given milestones with progress updates on the
roadmap where applicable

Assume some possibilities going forward could be...

- improve publicity  and/or improve communication for the project (11) to
get more interest in development (14) and usage
- to do a triage of existing issues, grouping if not already where
possible, getting rid of already closed, rejected, duplicates, or OBE items
(5)
- improve and update documentation to be more up to date (4) (9) (10) (14)
- update or document process documentation (release process, etc.)
- performance assessment and improvements
- where applicable possible codebase refactoring to cleanup, deprecate,
identify areas of improvement, etc.
- complete integration of any community / contributions products (15) (16)
- further plug-in migration to new plugins infrastructure where applicable
- improve LSP (13) support to include of new or existing languages (Kotlin
(12), python, etc.)
- Possible improvements in trending development areas (cloud development,
container development, data science, new languages, etc.)
- Netbeans GUI to FX based UI
- Netbean platform updates where applicable
- Update with New Java features or removal/migration of deprecated
within Netbeans
codebase (modules, records, deprecate apis, etc.) Note: This would require
updating JDK dependency as applicable

I know some aspects of these suggestions may exist in some form or another,
some of this is due to my lack of specifics on some of this.  That or this
is what happens when you can’t sleep at night ;-)

Eric Bresie
ebre...@gmail.com

(1) https://netbeans.org/community/releases/roadmap.html

(2)
https://netbeans.org/community/releases/

(3) https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule

(4)
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeansi

(5)
https://issues.apache.org/jira/projects/NETBEANS/issues

(6)
https://github.com/apache/netbeans

(7)
https://github.com/apache/netbeans/pulls
(8) https://github.com/apache/netbeans/blob/master/README.md

(9) https://netbeans.apache.org/help/index.html

(10) https://netbeans.org/kb/

(11) https://netbeans.apache.org/community/mailing-lists.html

(12)
https://blogs.apache.org/netbeans/entry/initial-language-server-protocol-support

(13) https://langserver.org/

(14) https://netbeans.apache.org/wiki/index.asciidoc

(15)
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition

(16)
https://hg.netbeans.org/



-
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

Re: Netbeans Vision / Roadmap

[Michael Bien]

On 01.12.22 12:50, Jean-Marc Borer wrote:

Short answer, yes - eg. link on all release candidate emails
https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16


I didn't know that one. Milestones are a cool way to mark specific merges

Longer answer, there is some work going on to better categorize all

this - eg. https://github.com/apache/netbeans/releases  The draft one
particularly, but that's private.


That is what I was looking for, but this list is not available until a few
days before the release, right?

Not recently.  What prompted the question?
We were wondering if there is a kind of a road map of planned new features
people agreed to work on.


there is no project wide roadmap. Whatever is ready, is reviewed and 
makes sense to be included is merged before a release.


Individual contributors might have plans for features they really want 
to see in upcoming releases, but there is no project wide one.


the milestones are like a queue of items to integrate before the next 
release, what doesn't make it will be moved to the next milestone or 
will lose the milestone tag.


https://github.com/apache/netbeans/milestone/20 (that is for NB17)

Keep in mind this is not a final list since candidates are added as they 
appear.




Moreover in our company, when we foresee to release a given feature for a
specific version, we tag it even long before the final release.


well if your company wants to contribute something, put it on your 
roadmap :)


regards,

-mbien


-
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

Re: Netbeans Vision / Roadmap

[Laszlo Kishalmi]

On 12/3/22 04:53, Michael Bien wrote:

On 30.11.22 16:08, Neil C Smith wrote:

On Wed, 30 Nov 2022 at 15:02, Jean-Marc Borer  wrote:
Ok, so does it mean, that I have to check Github history to find out 
what

is in a upcoming release  (16 for example)?

Short answer, yes - eg. link on all release candidate emails
https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16

Longer answer, there is some work going on to better categorize all
this - eg. https://github.com/apache/netbeans/releases  The draft one
particularly, but that's private.


I updated the release notes for 16:

https://github.com/apache/netbeans/releases/tag/16


Thanks for that! I've manually edited that, grouping my editor work.

OMG. Just realized, I'm the Editor guy in NB16!



(if there is something wrong with the updated notes any PMC can simply 
re-generate them with the default)



doing this retroactively is not as easy as it sounds since the 
generator uses the template file from master at the time of the 
release and there was no such file at that time in the repo.


Cheating and doing a force push on a private clone won't work either 
since it has no access to the PRs.


So i wrote a rudimentary tool which does some boolean algebra on draft 
release notes generated from HEAD backwards. Seems to work ok.


For older releases we would have to manually label a lot of PRs first 
(I fixed it for 16), since we only started labeling PRs consistently 
when CI started to require that.


-mbien


-
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

Re: Netbeans Vision / Roadmap

[Eric Bresie]

So are milestones added before  (leading up to a release)  or after
(tagging PRs included/merged) into the actual release?

Would a "milestone r - candidate" tag/milestone be valuable as an "up
front" to help collect of possible candidate PRs for a coming release as a
way of a given PR author as saying "I want this to be included into the
next release"?  Or would it be tagged for the release even if it doesn't
get included (I assume at that point the milestone would be removed by the
release manager or applicable authority)?

Or would the tagging be done during the PR completion activity (i.e. once
PR is completed, accepted [and merged?]) it would be tagged in the
applicable milestone release and merged into main (or a release branch)?

The above someone has the ability to tag things to a given milestone (i.e.
not new committers/contributors without the ability).

Eric Bresie
ebre...@gmail.com


On Thu, Dec 1, 2022 at 5:51 AM Jean-Marc Borer  wrote:

> >
> > Short answer, yes - eg. link on all release candidate emails
> > https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16
>
>
> I didn't know that one. Milestones are a cool way to mark specific merges
>
> Longer answer, there is some work going on to better categorize all
> > this - eg. https://github.com/apache/netbeans/releases  The draft one
> > particularly, but that's private.
>
>
> That is what I was looking for, but this list is not available until a few
> days before the release, right?
>
> Not recently.  What prompted the question?
> >
>
> We were wondering if there is a kind of a road map of planned new features
> people agreed to work on.
> Moreover in our company, when we foresee to release a given feature for a
> specific version, we tag it even long before the final release. We were
> looking for such an equivalent in the NB project.
>
> I think that is exactly the purpose of milestones.
>
> Thx for your answers
>
> On Wed, Nov 30, 2022 at 3:09 PM Neil C Smith 
> wrote:
>
> > On Wed, 30 Nov 2022 at 15:02, Jean-Marc Borer  wrote:
> > > Ok, so does it mean, that I have to check Github history to find out
> what
> > > is in a upcoming release  (16 for example)?
> >
> > Short answer, yes - eg. link on all release candidate emails
> > https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16
> >
> > Longer answer, there is some work going on to better categorize all
> > this - eg. https://github.com/apache/netbeans/releases  The draft one
> > particularly, but that's private.
> >
> > > > > Am I missing something or did something change for the release
> > > > management?
> >
> > Not recently.  What prompted the question?
> >
> > 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
> >
> >
> >
> >
>

Re: Netbeans Vision / Roadmap

[Michael Bien]

On 30.11.22 16:08, Neil C Smith wrote:

On Wed, 30 Nov 2022 at 15:02, Jean-Marc Borer  wrote:

Ok, so does it mean, that I have to check Github history to find out what
is in a upcoming release  (16 for example)?

Short answer, yes - eg. link on all release candidate emails
https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16

Longer answer, there is some work going on to better categorize all
this - eg. https://github.com/apache/netbeans/releases  The draft one
particularly, but that's private.


I updated the release notes for 16:

https://github.com/apache/netbeans/releases/tag/16

(if there is something wrong with the updated notes any PMC can simply 
re-generate them with the default)



doing this retroactively is not as easy as it sounds since the generator 
uses the template file from master at the time of the release and there 
was no such file at that time in the repo.


Cheating and doing a force push on a private clone won't work either 
since it has no access to the PRs.


So i wrote a rudimentary tool which does some boolean algebra on draft 
release notes generated from HEAD backwards. Seems to work ok.


For older releases we would have to manually label a lot of PRs first (I 
fixed it for 16), since we only started labeling PRs consistently when 
CI started to require that.


-mbien


-
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

Re: Netbeans Vision / Roadmap

[Jean-Marc Borer]

>
> Short answer, yes - eg. link on all release candidate emails
> https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16


I didn't know that one. Milestones are a cool way to mark specific merges

Longer answer, there is some work going on to better categorize all
> this - eg. https://github.com/apache/netbeans/releases  The draft one
> particularly, but that's private.


That is what I was looking for, but this list is not available until a few
days before the release, right?

Not recently.  What prompted the question?
>

We were wondering if there is a kind of a road map of planned new features
people agreed to work on.
Moreover in our company, when we foresee to release a given feature for a
specific version, we tag it even long before the final release. We were
looking for such an equivalent in the NB project.

I think that is exactly the purpose of milestones.

Thx for your answers

On Wed, Nov 30, 2022 at 3:09 PM Neil C Smith  wrote:

> On Wed, 30 Nov 2022 at 15:02, Jean-Marc Borer  wrote:
> > Ok, so does it mean, that I have to check Github history to find out what
> > is in a upcoming release  (16 for example)?
>
> Short answer, yes - eg. link on all release candidate emails
> https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16
>
> Longer answer, there is some work going on to better categorize all
> this - eg. https://github.com/apache/netbeans/releases  The draft one
> particularly, but that's private.
>
> > > > Am I missing something or did something change for the release
> > > management?
>
> Not recently.  What prompted the question?
>
> 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
>
>
>
>

Re: Netbeans Vision / Roadmap

[Neil C Smith]

On Wed, 30 Nov 2022 at 15:02, Jean-Marc Borer  wrote:
> Ok, so does it mean, that I have to check Github history to find out what
> is in a upcoming release  (16 for example)?

Short answer, yes - eg. link on all release candidate emails
https://github.com/apache/netbeans/pulls?q=is%3Amerged+milestone%3ANB16

Longer answer, there is some work going on to better categorize all
this - eg. https://github.com/apache/netbeans/releases  The draft one
particularly, but that's private.

> > > Am I missing something or did something change for the release
> > management?

Not recently.  What prompted the question?

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

Re: Netbeans Vision / Roadmap

[Eric Bresie]

I thought something like this was proposed or in use but aren’t PR tagged or 
label with some form of release tag?  Would that help?

Get Outlook for iOS<https://aka.ms/o0ukef>

From: Jean-Marc Borer 
Sent: Wednesday, November 30, 2022 9:01:46 AM
To: dev@netbeans.apache.org 
Subject: Re: Netbeans Vision / Roadmap

Ok, so does it mean, that I have to check Github history to find out what
is in a upcoming release  (16 for example)?

JMB

On Wed, Nov 30, 2022 at 12:50 PM Geertjan Wielenga
 wrote:

> As every release, we add to the release what individual contributors want
> to contribute, we will release 4 times per year. I don’t see this roadmap
> changing.
>
> Gj
>
> On Wed, 30 Nov 2022 at 13:42, Jean-Marc Borer  wrote:
>
> > Hi dear PMCs,
> >
> > I would like to reactivate this discussion, because we (our team) are
> > wondering if there is still a roadmap for the forthcoming releases
> > somewhere. The
> > https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
> > confluence page contains very few (not say no) information about this.
> >
> > Am I missing something or did something change for the release
> management?
> >
> > Best regards,
> >
> > JMB
> >
> > On Fri, Dec 4, 2020 at 11:06 AM Eric Bresie  wrote:
> >
> > > There has been recent discussions on vision and roadmap for Netbeans
> > > development and the need to discuss so thought I would start a new
> thread
> > > to discuss.
> > >
> > > From my understanding when under Oracle stewardship there more funded
> > > individuals to support these sorts of things but now that it has been
> > > donated to be an Apache project this now becomes the responsibility of
> > the
> > > community to pick this up.
> > >
> > > In the past there has been community release / roadmaps (1) (2) and
> with
> > > transition some similar Apache wiki flavors(3).
> > >
> > > Assuming what is needed is maybe a new “Roadmap” and or “Vision”
> subpage
> > on
> > > Netbeans wiki page (4) as a starter.
> > >
> > > Milestone could be identified based on this.
> > >
> > > Assuming specific features, refractors, improvements would further be
> > > captured and come in the form of existing or new JIRA tickets (5) and
> > when
> > > ready for acceptance then on the github project (6) a git Pull Requests
> > > (PR) (7) and tagged towards given milestones with progress updates on
> the
> > > roadmap where applicable
> > >
> > > Assume some possibilities going forward could be...
> > >
> > > - improve publicity  and/or improve communication for the project (11)
> to
> > > get more interest in development (14) and usage
> > > - to do a triage of existing issues, grouping if not already where
> > > possible, getting rid of already closed, rejected, duplicates, or OBE
> > items
> > > (5)
> > > - improve and update documentation to be more up to date (4) (9) (10)
> > (14)
> > > - update or document process documentation (release process, etc.)
> > > - performance assessment and improvements
> > > - where applicable possible codebase refactoring to cleanup, deprecate,
> > > identify areas of improvement, etc.
> > > - complete integration of any community / contributions products (15)
> > (16)
> > > - further plug-in migration to new plugins infrastructure where
> > applicable
> > > - improve LSP (13) support to include of new or existing languages
> > (Kotlin
> > > (12), python, etc.)
> > > - Possible improvements in trending development areas (cloud
> development,
> > > container development, data science, new languages, etc.)
> > > - Netbeans GUI to FX based UI
> > > - Netbean platform updates where applicable
> > > - Update with New Java features or removal/migration of deprecated
> > > within Netbeans
> > > codebase (modules, records, deprecate apis, etc.) Note: This would
> > require
> > > updating JDK dependency as applicable
> > >
> > > I know some aspects of these suggestions may exist in some form or
> > another,
> > > some of this is due to my lack of specifics on some of this.  That or
> > this
> > > is what happens when you can’t sleep at night ;-)
> > >
> > > Eric Bresie
> > > ebre...@gmail.com
> > >
> > > (1) https://netbeans.org/community/releases/roadmap.html
> > >
> > > (2)
> > > https://netbeans.o

Re: Netbeans Vision / Roadmap

[Jean-Marc Borer]

Ok, so does it mean, that I have to check Github history to find out what
is in a upcoming release  (16 for example)?

JMB

On Wed, Nov 30, 2022 at 12:50 PM Geertjan Wielenga
 wrote:

> As every release, we add to the release what individual contributors want
> to contribute, we will release 4 times per year. I don’t see this roadmap
> changing.
>
> Gj
>
> On Wed, 30 Nov 2022 at 13:42, Jean-Marc Borer  wrote:
>
> > Hi dear PMCs,
> >
> > I would like to reactivate this discussion, because we (our team) are
> > wondering if there is still a roadmap for the forthcoming releases
> > somewhere. The
> > https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
> > confluence page contains very few (not say no) information about this.
> >
> > Am I missing something or did something change for the release
> management?
> >
> > Best regards,
> >
> > JMB
> >
> > On Fri, Dec 4, 2020 at 11:06 AM Eric Bresie  wrote:
> >
> > > There has been recent discussions on vision and roadmap for Netbeans
> > > development and the need to discuss so thought I would start a new
> thread
> > > to discuss.
> > >
> > > From my understanding when under Oracle stewardship there more funded
> > > individuals to support these sorts of things but now that it has been
> > > donated to be an Apache project this now becomes the responsibility of
> > the
> > > community to pick this up.
> > >
> > > In the past there has been community release / roadmaps (1) (2) and
> with
> > > transition some similar Apache wiki flavors(3).
> > >
> > > Assuming what is needed is maybe a new “Roadmap” and or “Vision”
> subpage
> > on
> > > Netbeans wiki page (4) as a starter.
> > >
> > > Milestone could be identified based on this.
> > >
> > > Assuming specific features, refractors, improvements would further be
> > > captured and come in the form of existing or new JIRA tickets (5) and
> > when
> > > ready for acceptance then on the github project (6) a git Pull Requests
> > > (PR) (7) and tagged towards given milestones with progress updates on
> the
> > > roadmap where applicable
> > >
> > > Assume some possibilities going forward could be...
> > >
> > > - improve publicity  and/or improve communication for the project (11)
> to
> > > get more interest in development (14) and usage
> > > - to do a triage of existing issues, grouping if not already where
> > > possible, getting rid of already closed, rejected, duplicates, or OBE
> > items
> > > (5)
> > > - improve and update documentation to be more up to date (4) (9) (10)
> > (14)
> > > - update or document process documentation (release process, etc.)
> > > - performance assessment and improvements
> > > - where applicable possible codebase refactoring to cleanup, deprecate,
> > > identify areas of improvement, etc.
> > > - complete integration of any community / contributions products (15)
> > (16)
> > > - further plug-in migration to new plugins infrastructure where
> > applicable
> > > - improve LSP (13) support to include of new or existing languages
> > (Kotlin
> > > (12), python, etc.)
> > > - Possible improvements in trending development areas (cloud
> development,
> > > container development, data science, new languages, etc.)
> > > - Netbeans GUI to FX based UI
> > > - Netbean platform updates where applicable
> > > - Update with New Java features or removal/migration of deprecated
> > > within Netbeans
> > > codebase (modules, records, deprecate apis, etc.) Note: This would
> > require
> > > updating JDK dependency as applicable
> > >
> > > I know some aspects of these suggestions may exist in some form or
> > another,
> > > some of this is due to my lack of specifics on some of this.  That or
> > this
> > > is what happens when you can’t sleep at night ;-)
> > >
> > > Eric Bresie
> > > ebre...@gmail.com
> > >
> > > (1) https://netbeans.org/community/releases/roadmap.html
> > >
> > > (2)
> > > https://netbeans.org/community/releases/
> > >
> > > (3)
> > https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
> > >
> > > (4)
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeansi
> > >
> > > (5)
> > > https://issues.apache.org/jira/projects/NETBEANS/issues
> > >
> > > (6)
> > > https://github.com/apache/netbeans
> > >
> > > (7)
> > > https://github.com/apache/netbeans/pulls
> > > (8) https://github.com/apache/netbeans/blob/master/README.md
> > >
> > > (9) https://netbeans.apache.org/help/index.html
> > >
> > > (10) https://netbeans.org/kb/
> > >
> > > (11) https://netbeans.apache.org/community/mailing-lists.html
> > >
> > > (12)
> > >
> > >
> >
> https://blogs.apache.org/netbeans/entry/initial-language-server-protocol-support
> > >
> > > (13) https://langserver.org/
> > >
> > > (14) https://netbeans.apache.org/wiki/index.asciidoc
> > >
> > > (15)
> > > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition
> > >
> > > (16)
> > > https://hg.netbeans.org/
> > >
> > > --
> > > Eric Bresie
> > > ebre...@gmail.com
> > >
> >
>

Re: Netbeans Vision / Roadmap

[Geertjan Wielenga]

As every release, we add to the release what individual contributors want
to contribute, we will release 4 times per year. I don’t see this roadmap
changing.

Gj

On Wed, 30 Nov 2022 at 13:42, Jean-Marc Borer  wrote:

> Hi dear PMCs,
>
> I would like to reactivate this discussion, because we (our team) are
> wondering if there is still a roadmap for the forthcoming releases
> somewhere. The
> https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
> confluence page contains very few (not say no) information about this.
>
> Am I missing something or did something change for the release management?
>
> Best regards,
>
> JMB
>
> On Fri, Dec 4, 2020 at 11:06 AM Eric Bresie  wrote:
>
> > There has been recent discussions on vision and roadmap for Netbeans
> > development and the need to discuss so thought I would start a new thread
> > to discuss.
> >
> > From my understanding when under Oracle stewardship there more funded
> > individuals to support these sorts of things but now that it has been
> > donated to be an Apache project this now becomes the responsibility of
> the
> > community to pick this up.
> >
> > In the past there has been community release / roadmaps (1) (2) and with
> > transition some similar Apache wiki flavors(3).
> >
> > Assuming what is needed is maybe a new “Roadmap” and or “Vision” subpage
> on
> > Netbeans wiki page (4) as a starter.
> >
> > Milestone could be identified based on this.
> >
> > Assuming specific features, refractors, improvements would further be
> > captured and come in the form of existing or new JIRA tickets (5) and
> when
> > ready for acceptance then on the github project (6) a git Pull Requests
> > (PR) (7) and tagged towards given milestones with progress updates on the
> > roadmap where applicable
> >
> > Assume some possibilities going forward could be...
> >
> > - improve publicity  and/or improve communication for the project (11) to
> > get more interest in development (14) and usage
> > - to do a triage of existing issues, grouping if not already where
> > possible, getting rid of already closed, rejected, duplicates, or OBE
> items
> > (5)
> > - improve and update documentation to be more up to date (4) (9) (10)
> (14)
> > - update or document process documentation (release process, etc.)
> > - performance assessment and improvements
> > - where applicable possible codebase refactoring to cleanup, deprecate,
> > identify areas of improvement, etc.
> > - complete integration of any community / contributions products (15)
> (16)
> > - further plug-in migration to new plugins infrastructure where
> applicable
> > - improve LSP (13) support to include of new or existing languages
> (Kotlin
> > (12), python, etc.)
> > - Possible improvements in trending development areas (cloud development,
> > container development, data science, new languages, etc.)
> > - Netbeans GUI to FX based UI
> > - Netbean platform updates where applicable
> > - Update with New Java features or removal/migration of deprecated
> > within Netbeans
> > codebase (modules, records, deprecate apis, etc.) Note: This would
> require
> > updating JDK dependency as applicable
> >
> > I know some aspects of these suggestions may exist in some form or
> another,
> > some of this is due to my lack of specifics on some of this.  That or
> this
> > is what happens when you can’t sleep at night ;-)
> >
> > Eric Bresie
> > ebre...@gmail.com
> >
> > (1) https://netbeans.org/community/releases/roadmap.html
> >
> > (2)
> > https://netbeans.org/community/releases/
> >
> > (3)
> https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
> >
> > (4)
> > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeansi
> >
> > (5)
> > https://issues.apache.org/jira/projects/NETBEANS/issues
> >
> > (6)
> > https://github.com/apache/netbeans
> >
> > (7)
> > https://github.com/apache/netbeans/pulls
> > (8) https://github.com/apache/netbeans/blob/master/README.md
> >
> > (9) https://netbeans.apache.org/help/index.html
> >
> > (10) https://netbeans.org/kb/
> >
> > (11) https://netbeans.apache.org/community/mailing-lists.html
> >
> > (12)
> >
> >
> https://blogs.apache.org/netbeans/entry/initial-language-server-protocol-support
> >
> > (13) https://langserver.org/
> >
> > (14) https://netbeans.apache.org/wiki/index.asciidoc
> >
> > (15)
> > https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition
> >
> > (16)
> > https://hg.netbeans.org/
> >
> > --
> > Eric Bresie
> > ebre...@gmail.com
> >
>

Re: Netbeans Vision / Roadmap

[Jean-Marc Borer]

Hi dear PMCs,

I would like to reactivate this discussion, because we (our team) are
wondering if there is still a roadmap for the forthcoming releases
somewhere. The
https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
confluence page contains very few (not say no) information about this.

Am I missing something or did something change for the release management?

Best regards,

JMB

On Fri, Dec 4, 2020 at 11:06 AM Eric Bresie  wrote:

> There has been recent discussions on vision and roadmap for Netbeans
> development and the need to discuss so thought I would start a new thread
> to discuss.
>
> From my understanding when under Oracle stewardship there more funded
> individuals to support these sorts of things but now that it has been
> donated to be an Apache project this now becomes the responsibility of the
> community to pick this up.
>
> In the past there has been community release / roadmaps (1) (2) and with
> transition some similar Apache wiki flavors(3).
>
> Assuming what is needed is maybe a new “Roadmap” and or “Vision” subpage on
> Netbeans wiki page (4) as a starter.
>
> Milestone could be identified based on this.
>
> Assuming specific features, refractors, improvements would further be
> captured and come in the form of existing or new JIRA tickets (5) and when
> ready for acceptance then on the github project (6) a git Pull Requests
> (PR) (7) and tagged towards given milestones with progress updates on the
> roadmap where applicable
>
> Assume some possibilities going forward could be...
>
> - improve publicity  and/or improve communication for the project (11) to
> get more interest in development (14) and usage
> - to do a triage of existing issues, grouping if not already where
> possible, getting rid of already closed, rejected, duplicates, or OBE items
> (5)
> - improve and update documentation to be more up to date (4) (9) (10) (14)
> - update or document process documentation (release process, etc.)
> - performance assessment and improvements
> - where applicable possible codebase refactoring to cleanup, deprecate,
> identify areas of improvement, etc.
> - complete integration of any community / contributions products (15) (16)
> - further plug-in migration to new plugins infrastructure where applicable
> - improve LSP (13) support to include of new or existing languages (Kotlin
> (12), python, etc.)
> - Possible improvements in trending development areas (cloud development,
> container development, data science, new languages, etc.)
> - Netbeans GUI to FX based UI
> - Netbean platform updates where applicable
> - Update with New Java features or removal/migration of deprecated
> within Netbeans
> codebase (modules, records, deprecate apis, etc.) Note: This would require
> updating JDK dependency as applicable
>
> I know some aspects of these suggestions may exist in some form or another,
> some of this is due to my lack of specifics on some of this.  That or this
> is what happens when you can’t sleep at night ;-)
>
> Eric Bresie
> ebre...@gmail.com
>
> (1) https://netbeans.org/community/releases/roadmap.html
>
> (2)
> https://netbeans.org/community/releases/
>
> (3) https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
>
> (4)
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeansi
>
> (5)
> https://issues.apache.org/jira/projects/NETBEANS/issues
>
> (6)
> https://github.com/apache/netbeans
>
> (7)
> https://github.com/apache/netbeans/pulls
> (8) https://github.com/apache/netbeans/blob/master/README.md
>
> (9) https://netbeans.apache.org/help/index.html
>
> (10) https://netbeans.org/kb/
>
> (11) https://netbeans.apache.org/community/mailing-lists.html
>
> (12)
>
> https://blogs.apache.org/netbeans/entry/initial-language-server-protocol-support
>
> (13) https://langserver.org/
>
> (14) https://netbeans.apache.org/wiki/index.asciidoc
>
> (15)
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition
>
> (16)
> https://hg.netbeans.org/
>
> --
> Eric Bresie
> ebre...@gmail.com
>

Re: [External] Netbeans Vision / Roadmap

[Marangwanda, Ronald]

I think that Netbeans should focus on speed of development and developer 
ergonomics.

Using Ant as a build tool is probably fine except the next question is why use 
Ant in 2020?

I think Gradle or Maven would be easier for many new developers to contribute 
using just because of familiarity.

Navigating the new Documentation website is hard to do because I just found out 
there is a blog link which in my opinion contains what I want most of the time:

The latest netbeans version and where to download it:

It could even be set up along tracks:
1. Dev  track
2. Stable tracj
3. LTS track

That is the first thing I want to see is what is the latest version ( dev, 
stable, LTS) of Netbeans and where do I get it. I find this information always 
hard to find:

I sometimes end up on Jenkins pages.

The update tool inside the IDE is probably the most interesting feature for 
rapid development but I have never figure out how it works.

Is it just for plugins or can I update Netbeans itself using the Chek for 
Updates button?

I think this is again a lack on focus on rapid development and deployment.

Ron




On Dec 11, 2020, at 1:24 PM, Eric Bresie 
mailto:ebre...@gmail.com>> wrote:

Not fully aware of the current documentation organizational structure (if
there is such a thing) so...Where might be the best placed to put this sort
of information?
Eric Bresie
ebre...@gmail.com


On Fri, Dec 4, 2020 at 5:46 AM Neil C Smith 
mailto:neilcsm...@apache.org>> wrote:

On Fri, 4 Dec 2020 at 11:06, Eric Bresie 
mailto:ebre...@gmail.com>> wrote:
- Netbeans GUI to FX based UI

Thanks Eric for that, and agree with a lot of it.  But I can't see
this one happening.  Leaving aside technical aspects or desirability
(and I still have a lot of doubts about FX!), there would be some
licensing hurdles to overcome here at ASF.  And we might want to drop
some of the things that are currently (and optionally) FX webview
based in the NetBeans UI for a start, even if we did get go ahead for
other modules.

In the shorter term, focus on aspects of the IDE working headless for
VSCode, etc. may have benefits in opening up scope for exploring other
UIs anyway?

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://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/NETBEANS/Mailing*lists__;Kw!!CjcC7IQ!dfgBdSX34umjIXV7ssnMeAPUhOVQwBk2OL0NOgxftAPEu6iB5NdpCx9IhH2GAw1b4m8JHA$
 [cwiki[.]apache[.]org]


This e-mail may contain confidential and/or privileged information for the sole 
use of the intended recipient.
Any review or distribution by anyone other than the person for whom it was 
originally intended is strictly prohibited.
If you have received this e-mail in error, please contact the sender and delete 
all copies.
Opinions, conclusions or other information contained in this e-mail may not be 
that of the organization.

If you feel you have received an email from UHN of a commercial nature and 
would like to be removed from the sender's mailing list please do one of the 
following:
(1) Follow any unsubscribe process the sender has included in their email
(2) Where no unsubscribe process has been included, reply to the sender and 
type "unsubscribe" in the subject line. If you require additional information 
please go to our UHN Newsletters and Mailing Lists page.
Please note that we are unable to automatically unsubscribe individuals from 
all UHN mailing lists.

Re: Netbeans Vision / Roadmap

[Eric Bresie]

Not fully aware of the current documentation organizational structure (if
there is such a thing) so...Where might be the best placed to put this sort
of information?
Eric Bresie
ebre...@gmail.com


On Fri, Dec 4, 2020 at 5:46 AM Neil C Smith  wrote:

> On Fri, 4 Dec 2020 at 11:06, Eric Bresie  wrote:
> > - Netbeans GUI to FX based UI
>
> Thanks Eric for that, and agree with a lot of it.  But I can't see
> this one happening.  Leaving aside technical aspects or desirability
> (and I still have a lot of doubts about FX!), there would be some
> licensing hurdles to overcome here at ASF.  And we might want to drop
> some of the things that are currently (and optionally) FX webview
> based in the NetBeans UI for a start, even if we did get go ahead for
> other modules.
>
> In the shorter term, focus on aspects of the IDE working headless for
> VSCode, etc. may have benefits in opening up scope for exploring other
> UIs anyway?
>
> 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
>
>
>
>

Re: Netbeans Vision / Roadmap

[Neil C Smith]

On Fri, 4 Dec 2020 at 11:06, Eric Bresie  wrote:
> - Netbeans GUI to FX based UI

Thanks Eric for that, and agree with a lot of it.  But I can't see
this one happening.  Leaving aside technical aspects or desirability
(and I still have a lot of doubts about FX!), there would be some
licensing hurdles to overcome here at ASF.  And we might want to drop
some of the things that are currently (and optionally) FX webview
based in the NetBeans UI for a start, even if we did get go ahead for
other modules.

In the shorter term, focus on aspects of the IDE working headless for
VSCode, etc. may have benefits in opening up scope for exploring other
UIs anyway?

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

Re: Netbeans Vision / Roadmap

[Geertjan Wielenga]

Excellent. Would be great to have these tasks in a table in our Wiki, maybe
we can get more people involved via these tasks, we could also approach the
users mailing list, once we have the table, to see if they’d like to be
involved.

Gj

On Fri, 4 Dec 2020 at 12:06, Eric Bresie  wrote:

> There has been recent discussions on vision and roadmap for Netbeans
> development and the need to discuss so thought I would start a new thread
> to discuss.
>
> From my understanding when under Oracle stewardship there more funded
> individuals to support these sorts of things but now that it has been
> donated to be an Apache project this now becomes the responsibility of the
> community to pick this up.
>
> In the past there has been community release / roadmaps (1) (2) and with
> transition some similar Apache wiki flavors(3).
>
> Assuming what is needed is maybe a new “Roadmap” and or “Vision” subpage on
> Netbeans wiki page (4) as a starter.
>
> Milestone could be identified based on this.
>
> Assuming specific features, refractors, improvements would further be
> captured and come in the form of existing or new JIRA tickets (5) and when
> ready for acceptance then on the github project (6) a git Pull Requests
> (PR) (7) and tagged towards given milestones with progress updates on the
> roadmap where applicable
>
> Assume some possibilities going forward could be...
>
> - improve publicity  and/or improve communication for the project (11) to
> get more interest in development (14) and usage
> - to do a triage of existing issues, grouping if not already where
> possible, getting rid of already closed, rejected, duplicates, or OBE items
> (5)
> - improve and update documentation to be more up to date (4) (9) (10) (14)
> - update or document process documentation (release process, etc.)
> - performance assessment and improvements
> - where applicable possible codebase refactoring to cleanup, deprecate,
> identify areas of improvement, etc.
> - complete integration of any community / contributions products (15) (16)
> - further plug-in migration to new plugins infrastructure where applicable
> - improve LSP (13) support to include of new or existing languages (Kotlin
> (12), python, etc.)
> - Possible improvements in trending development areas (cloud development,
> container development, data science, new languages, etc.)
> - Netbeans GUI to FX based UI
> - Netbean platform updates where applicable
> - Update with New Java features or removal/migration of deprecated
> within Netbeans
> codebase (modules, records, deprecate apis, etc.) Note: This would require
> updating JDK dependency as applicable
>
> I know some aspects of these suggestions may exist in some form or another,
> some of this is due to my lack of specifics on some of this.  That or this
> is what happens when you can’t sleep at night ;-)
>
> Eric Bresie
> ebre...@gmail.com
>
> (1) https://netbeans.org/community/releases/roadmap.html
>
> (2)
> https://netbeans.org/community/releases/
>
> (3) https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule
>
> (4)
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeansi
>
> (5)
> https://issues.apache.org/jira/projects/NETBEANS/issues
>
> (6)
> https://github.com/apache/netbeans
>
> (7)
> https://github.com/apache/netbeans/pulls
> (8) https://github.com/apache/netbeans/blob/master/README.md
>
> (9) https://netbeans.apache.org/help/index.html
>
> (10) https://netbeans.org/kb/
>
> (11) https://netbeans.apache.org/community/mailing-lists.html
>
> (12)
>
> https://blogs.apache.org/netbeans/entry/initial-language-server-protocol-support
>
> (13) https://langserver.org/
>
> (14) https://netbeans.apache.org/wiki/index.asciidoc
>
> (15)
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition
>
> (16)
> https://hg.netbeans.org/
>
> --
> Eric Bresie
> ebre...@gmail.com
>

Netbeans Vision / Roadmap

[Eric Bresie]

There has been recent discussions on vision and roadmap for Netbeans
development and the need to discuss so thought I would start a new thread
to discuss.

>From my understanding when under Oracle stewardship there more funded
individuals to support these sorts of things but now that it has been
donated to be an Apache project this now becomes the responsibility of the
community to pick this up.

In the past there has been community release / roadmaps (1) (2) and with
transition some similar Apache wiki flavors(3).

Assuming what is needed is maybe a new “Roadmap” and or “Vision” subpage on
Netbeans wiki page (4) as a starter.

Milestone could be identified based on this.

Assuming specific features, refractors, improvements would further be
captured and come in the form of existing or new JIRA tickets (5) and when
ready for acceptance then on the github project (6) a git Pull Requests
(PR) (7) and tagged towards given milestones with progress updates on the
roadmap where applicable

Assume some possibilities going forward could be...

- improve publicity  and/or improve communication for the project (11) to
get more interest in development (14) and usage
- to do a triage of existing issues, grouping if not already where
possible, getting rid of already closed, rejected, duplicates, or OBE items
(5)
- improve and update documentation to be more up to date (4) (9) (10) (14)
- update or document process documentation (release process, etc.)
- performance assessment and improvements
- where applicable possible codebase refactoring to cleanup, deprecate,
identify areas of improvement, etc.
- complete integration of any community / contributions products (15) (16)
- further plug-in migration to new plugins infrastructure where applicable
- improve LSP (13) support to include of new or existing languages (Kotlin
(12), python, etc.)
- Possible improvements in trending development areas (cloud development,
container development, data science, new languages, etc.)
- Netbeans GUI to FX based UI
- Netbean platform updates where applicable
- Update with New Java features or removal/migration of deprecated
within Netbeans
codebase (modules, records, deprecate apis, etc.) Note: This would require
updating JDK dependency as applicable

I know some aspects of these suggestions may exist in some form or another,
some of this is due to my lack of specifics on some of this.  That or this
is what happens when you can’t sleep at night ;-)

Eric Bresie
ebre...@gmail.com

(1) https://netbeans.org/community/releases/roadmap.html

(2)
https://netbeans.org/community/releases/

(3) https://cwiki.apache.org/confluence/display/NETBEANS/Release+Schedule

(4)
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeansi

(5)
https://issues.apache.org/jira/projects/NETBEANS/issues

(6)
https://github.com/apache/netbeans

(7)
https://github.com/apache/netbeans/pulls
(8) https://github.com/apache/netbeans/blob/master/README.md

(9) https://netbeans.apache.org/help/index.html

(10) https://netbeans.org/kb/

(11) https://netbeans.apache.org/community/mailing-lists.html

(12)
https://blogs.apache.org/netbeans/entry/initial-language-server-protocol-support

(13) https://langserver.org/

(14) https://netbeans.apache.org/wiki/index.asciidoc

(15)
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition

(16)
https://hg.netbeans.org/

-- 
Eric Bresie
ebre...@gmail.com