You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Geertjan Wielenga <ge...@googlemail.com> on 2017/09/26 07:17:33 UTC
Allow code contributions or focus on release only?
Hi all,
We need to discuss something, I think -- do we begin accepting pull
requests, and thereby encourage pull requests to be created -- or do we
focus very narrowly on preparing Apache NetBeans for its first incubator
release?
If we were to focus narrowly on preparing the Apache release, then this is
what we would focus on, nothing else:
https://cwiki.apache.org/confluence/display/NETBEANS/List+of+Modules+to+Review
At the same time, of course, people want to add their mark to Apache
NetBeans. And that means code or an icon, a menu item, a new UI thing to
point at and say -- see, I did that! These kinds of enhancements could be
done at the same time as the above, and would require that some people
split their time between doing the module reviews and reviewing pull
requests.
I'm not stating a preference here, just putting the discussion out there,
since I've seen conflicting opinions about this and I think it would be
good to discuss this centrally.
Thanks,
Gj
Re: Allow code contributions or focus on release only?
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Agree as well and really cool to see much activity and interaction.
Gj
On Tue, Sep 26, 2017 at 10:16 PM, Sven Reimers <sv...@gmail.com>
wrote:
> Hi all,
>
> I fully agree with Jan..
>
> Let's try to get something released first so we know the process..
>
> Hope to have some time to review modules real soon now..
>
> -Sven
>
> Am 26.09.2017 22:13 schrieb "Jan Lahoda" <la...@gmail.com>:
>
> > +1 (I think that if we want to get some rest and fun, we could use
> branches
> > to experiment with some new features (and I may do so at some point), but
> > we should limit unnecessary changes to master, and use our code
> > review/discussion bandwidth as much as possible for working on a release)
> >
> > I personally even think we could try to release just the platform (e.g.
> > NetBeans Platform 9.0 beta) once the platform modules are reviewed. That
> > would help us validate whether the approach we are taking makes sense
> (and
> > what needs to be improved) and would help us learn about the release
> > process (and the platform is a useful thing on its own, so releasing it
> > wouldn't be just an artificial move).
> >
> > Jan
> >
> >
> > On Tue, Sep 26, 2017 at 8:23 PM, Michael Nascimento <mi...@gmail.com>
> > wrote:
> >
> > > Definitely we should focus on getting an Apache NetBeans release.
> > > Sincerely, at this point, I think we should maybe have a Apache
> NetBeans
> > > 9.0 Java edition, so we can have something release and then a full
> Apache
> > > NB 9.0. Otherwise, sounds like we'll get no release this year, which
> > would
> > > be pretty sad.
> > >
> > > Regards,
> > > Michael
> > >
> > > <http://www.avg.com/email-signature?utm_medium=email&
> > > utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > > Virus-free.
> > > www.avg.com
> > > <http://www.avg.com/email-signature?utm_medium=email&
> > > utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > >
> > > On Tue, Sep 26, 2017 at 4:17 AM, Geertjan Wielenga <
> > > geertjan.wielenga@googlemail.com> wrote:
> > >
> > > > Hi all,
> > > >
> > > > We need to discuss something, I think -- do we begin accepting pull
> > > > requests, and thereby encourage pull requests to be created -- or do
> we
> > > > focus very narrowly on preparing Apache NetBeans for its first
> > incubator
> > > > release?
> > > >
> > > > If we were to focus narrowly on preparing the Apache release, then
> this
> > > is
> > > > what we would focus on, nothing else:
> > > >
> > > > https://cwiki.apache.org/confluence/display/NETBEANS/
> > > > List+of+Modules+to+Review
> > > >
> > > > At the same time, of course, people want to add their mark to Apache
> > > > NetBeans. And that means code or an icon, a menu item, a new UI thing
> > to
> > > > point at and say -- see, I did that! These kinds of enhancements
> could
> > be
> > > > done at the same time as the above, and would require that some
> people
> > > > split their time between doing the module reviews and reviewing pull
> > > > requests.
> > > >
> > > > I'm not stating a preference here, just putting the discussion out
> > there,
> > > > since I've seen conflicting opinions about this and I think it would
> be
> > > > good to discuss this centrally.
> > > >
> > > > Thanks,
> > > >
> > > > Gj
> > > >
> > >
> >
>
Re: Allow code contributions or focus on release only?
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Nope. No special knowledge needed, at all:
https://www.youtube.com/watch?v=Z4PBNSRp5g8
Gj
On Wed, Sep 27, 2017 at 9:13 AM, Christian Lenz <ch...@gmx.net>
wrote:
> I don’t know as much for this Review, so it would be better if there is
> someone else who is doing this, with more advanced experiences.
>
> Gesendet von Mail für Windows 10
>
> Von: Geertjan Wielenga
> Gesendet: Mittwoch, 27. September 2017 09:11
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Allow code contributions or focus on release only?
>
> Sure your PR will get merged, just not right now since we're focused on
> getting Apache NetBeans released. Do you want to join in with the Module
> Review?
>
> Gj
>
> On Wed, 27 Sep 2017 at 09:06, Christian Lenz <ch...@gmx.net>
> wrote:
>
> > So I should not doing any PR (my #3 PR will not be merged, right?) and I
> > should do it on Feature Branches? How is the process for Review and
> > merging? If we have 19275 feature branches, no one knows, when the
> Feature
> > is finish. Maybe we should have a release branch where we should merge
> the
> > stuff from Feature into release or whatever to make it clear: my Feature
> is
> > ready for Review/use etc.
> >
> > Gesendet von Mail für Windows 10
> >
> > Von: Geertjan Wielenga
> > Gesendet: Mittwoch, 27. September 2017 00:28
> > An: dev@netbeans.incubator.apache.org
> > Betreff: Re: Allow code contributions or focus on release only?
> >
> > Yup -- and corresponds with what we're doing.
> >
> > I love it when a plan comes together.
> >
> > Gj
> >
> > On Wed, Sep 27, 2017 at 12:03 AM, Wade Chandler <wadechandler@apache.org
> >
> > wrote:
> >
> > > That all sounds like a good strategy to me.
> > >
> > > +1
> > >
> > > Wade
> > >
> > > On Sep 26, 2017 17:44, "Craig Russell" <ap...@gmail.com> wrote:
> > >
> > > > I have no dog in this particular hunt, but if it were up to me I'd
> > > > prioritize:
> > > >
> > > > getting code into repositories with clean RAT reports
> > > > getting Netbeans to build and run
> > > > creating release(s) for major platforms
> > > > ...
> > > > serious bug reports
> > > > ...
> > > > features (in branches)
> > > >
> > > > Craig
> > > >
> > > > > On Sep 26, 2017, at 1:16 PM, Sven Reimers <sv...@gmail.com>
> > > > wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > I fully agree with Jan..
> > > > >
> > > > > Let's try to get something released first so we know the process..
> > > > >
> > > > > Hope to have some time to review modules real soon now..
> > > > >
> > > > > -Sven
> > > > >
> > > > > Am 26.09.2017 22:13 schrieb "Jan Lahoda" <la...@gmail.com>:
> > > > >
> > > > >> +1 (I think that if we want to get some rest and fun, we could use
> > > > branches
> > > > >> to experiment with some new features (and I may do so at some
> > point),
> > > > but
> > > > >> we should limit unnecessary changes to master, and use our code
> > > > >> review/discussion bandwidth as much as possible for working on a
> > > > release)
> > > > >>
> > > > >> I personally even think we could try to release just the platform
> > > (e.g.
> > > > >> NetBeans Platform 9.0 beta) once the platform modules are
> reviewed.
> > > That
> > > > >> would help us validate whether the approach we are taking makes
> > sense
> > > > (and
> > > > >> what needs to be improved) and would help us learn about the
> release
> > > > >> process (and the platform is a useful thing on its own, so
> releasing
> > > it
> > > > >> wouldn't be just an artificial move).
> > > > >>
> > > > >> Jan
> > > > >>
> > > > >>
> > > > >> On Tue, Sep 26, 2017 at 8:23 PM, Michael Nascimento <
> > > misterm@gmail.com>
> > > > >> wrote:
> > > > >>
> > > > >>> Definitely we should focus on getting an Apache NetBeans release.
> > > > >>> Sincerely, at this point, I think we should maybe have a Apache
> > > > NetBeans
> > > > >>> 9.0 Java edition, so we can have something release and then a
> full
> > > > Apache
> > > > >>> NB 9.0. Otherwise, sounds like we'll get no release this year,
> > which
> > > > >> would
> > > > >>> be pretty sad.
> > > > >>>
> > > > >>> Regards,
> > > > >>> Michael
> > > > >>>
> > > > >>> <http://www.avg.com/email-signature?utm_medium=email&
> > > > >>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > > > >>> Virus-free.
> > > > >>> www.avg.com
> > > > >>> <http://www.avg.com/email-signature?utm_medium=email&
> > > > >>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > > > >>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > > >>>
> > > > >>> On Tue, Sep 26, 2017 at 4:17 AM, Geertjan Wielenga <
> > > > >>> geertjan.wielenga@googlemail.com> wrote:
> > > > >>>
> > > > >>>> Hi all,
> > > > >>>>
> > > > >>>> We need to discuss something, I think -- do we begin accepting
> > pull
> > > > >>>> requests, and thereby encourage pull requests to be created --
> or
> > do
> > > > we
> > > > >>>> focus very narrowly on preparing Apache NetBeans for its first
> > > > >> incubator
> > > > >>>> release?
> > > > >>>>
> > > > >>>> If we were to focus narrowly on preparing the Apache release,
> then
> > > > this
> > > > >>> is
> > > > >>>> what we would focus on, nothing else:
> > > > >>>>
> > > > >>>> https://cwiki.apache.org/confluence/display/NETBEANS/
> > > > >>>> List+of+Modules+to+Review
> > > > >>>>
> > > > >>>> At the same time, of course, people want to add their mark to
> > Apache
> > > > >>>> NetBeans. And that means code or an icon, a menu item, a new UI
> > > thing
> > > > >> to
> > > > >>>> point at and say -- see, I did that! These kinds of enhancements
> > > could
> > > > >> be
> > > > >>>> done at the same time as the above, and would require that some
> > > people
> > > > >>>> split their time between doing the module reviews and reviewing
> > pull
> > > > >>>> requests.
> > > > >>>>
> > > > >>>> I'm not stating a preference here, just putting the discussion
> out
> > > > >> there,
> > > > >>>> since I've seen conflicting opinions about this and I think it
> > would
> > > > be
> > > > >>>> good to discuss this centrally.
> > > > >>>>
> > > > >>>> Thanks,
> > > > >>>>
> > > > >>>> Gj
> > > > >>>>
> > > > >>>
> > > > >>
> > > >
> > > > Craig L Russell
> > > > Secretary, Apache Software Foundation
> > > > clr@apache.org http://db.apache.org/jdo
> > > >
> > > >
> > >
> >
> >
>
>
AW: Allow code contributions or focus on release only?
Posted by Christian Lenz <ch...@gmx.net>.
I don’t know as much for this Review, so it would be better if there is someone else who is doing this, with more advanced experiences.
Gesendet von Mail für Windows 10
Von: Geertjan Wielenga
Gesendet: Mittwoch, 27. September 2017 09:11
An: dev@netbeans.incubator.apache.org
Betreff: Re: Allow code contributions or focus on release only?
Sure your PR will get merged, just not right now since we're focused on
getting Apache NetBeans released. Do you want to join in with the Module
Review?
Gj
On Wed, 27 Sep 2017 at 09:06, Christian Lenz <ch...@gmx.net> wrote:
> So I should not doing any PR (my #3 PR will not be merged, right?) and I
> should do it on Feature Branches? How is the process for Review and
> merging? If we have 19275 feature branches, no one knows, when the Feature
> is finish. Maybe we should have a release branch where we should merge the
> stuff from Feature into release or whatever to make it clear: my Feature is
> ready for Review/use etc.
>
> Gesendet von Mail für Windows 10
>
> Von: Geertjan Wielenga
> Gesendet: Mittwoch, 27. September 2017 00:28
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Allow code contributions or focus on release only?
>
> Yup -- and corresponds with what we're doing.
>
> I love it when a plan comes together.
>
> Gj
>
> On Wed, Sep 27, 2017 at 12:03 AM, Wade Chandler <wa...@apache.org>
> wrote:
>
> > That all sounds like a good strategy to me.
> >
> > +1
> >
> > Wade
> >
> > On Sep 26, 2017 17:44, "Craig Russell" <ap...@gmail.com> wrote:
> >
> > > I have no dog in this particular hunt, but if it were up to me I'd
> > > prioritize:
> > >
> > > getting code into repositories with clean RAT reports
> > > getting Netbeans to build and run
> > > creating release(s) for major platforms
> > > ...
> > > serious bug reports
> > > ...
> > > features (in branches)
> > >
> > > Craig
> > >
> > > > On Sep 26, 2017, at 1:16 PM, Sven Reimers <sv...@gmail.com>
> > > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I fully agree with Jan..
> > > >
> > > > Let's try to get something released first so we know the process..
> > > >
> > > > Hope to have some time to review modules real soon now..
> > > >
> > > > -Sven
> > > >
> > > > Am 26.09.2017 22:13 schrieb "Jan Lahoda" <la...@gmail.com>:
> > > >
> > > >> +1 (I think that if we want to get some rest and fun, we could use
> > > branches
> > > >> to experiment with some new features (and I may do so at some
> point),
> > > but
> > > >> we should limit unnecessary changes to master, and use our code
> > > >> review/discussion bandwidth as much as possible for working on a
> > > release)
> > > >>
> > > >> I personally even think we could try to release just the platform
> > (e.g.
> > > >> NetBeans Platform 9.0 beta) once the platform modules are reviewed.
> > That
> > > >> would help us validate whether the approach we are taking makes
> sense
> > > (and
> > > >> what needs to be improved) and would help us learn about the release
> > > >> process (and the platform is a useful thing on its own, so releasing
> > it
> > > >> wouldn't be just an artificial move).
> > > >>
> > > >> Jan
> > > >>
> > > >>
> > > >> On Tue, Sep 26, 2017 at 8:23 PM, Michael Nascimento <
> > misterm@gmail.com>
> > > >> wrote:
> > > >>
> > > >>> Definitely we should focus on getting an Apache NetBeans release.
> > > >>> Sincerely, at this point, I think we should maybe have a Apache
> > > NetBeans
> > > >>> 9.0 Java edition, so we can have something release and then a full
> > > Apache
> > > >>> NB 9.0. Otherwise, sounds like we'll get no release this year,
> which
> > > >> would
> > > >>> be pretty sad.
> > > >>>
> > > >>> Regards,
> > > >>> Michael
> > > >>>
> > > >>> <http://www.avg.com/email-signature?utm_medium=email&
> > > >>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > > >>> Virus-free.
> > > >>> www.avg.com
> > > >>> <http://www.avg.com/email-signature?utm_medium=email&
> > > >>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > > >>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > >>>
> > > >>> On Tue, Sep 26, 2017 at 4:17 AM, Geertjan Wielenga <
> > > >>> geertjan.wielenga@googlemail.com> wrote:
> > > >>>
> > > >>>> Hi all,
> > > >>>>
> > > >>>> We need to discuss something, I think -- do we begin accepting
> pull
> > > >>>> requests, and thereby encourage pull requests to be created -- or
> do
> > > we
> > > >>>> focus very narrowly on preparing Apache NetBeans for its first
> > > >> incubator
> > > >>>> release?
> > > >>>>
> > > >>>> If we were to focus narrowly on preparing the Apache release, then
> > > this
> > > >>> is
> > > >>>> what we would focus on, nothing else:
> > > >>>>
> > > >>>> https://cwiki.apache.org/confluence/display/NETBEANS/
> > > >>>> List+of+Modules+to+Review
> > > >>>>
> > > >>>> At the same time, of course, people want to add their mark to
> Apache
> > > >>>> NetBeans. And that means code or an icon, a menu item, a new UI
> > thing
> > > >> to
> > > >>>> point at and say -- see, I did that! These kinds of enhancements
> > could
> > > >> be
> > > >>>> done at the same time as the above, and would require that some
> > people
> > > >>>> split their time between doing the module reviews and reviewing
> pull
> > > >>>> requests.
> > > >>>>
> > > >>>> I'm not stating a preference here, just putting the discussion out
> > > >> there,
> > > >>>> since I've seen conflicting opinions about this and I think it
> would
> > > be
> > > >>>> good to discuss this centrally.
> > > >>>>
> > > >>>> Thanks,
> > > >>>>
> > > >>>> Gj
> > > >>>>
> > > >>>
> > > >>
> > >
> > > Craig L Russell
> > > Secretary, Apache Software Foundation
> > > clr@apache.org http://db.apache.org/jdo
> > >
> > >
> >
>
>
Re: Allow code contributions or focus on release only?
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Sure your PR will get merged, just not right now since we're focused on
getting Apache NetBeans released. Do you want to join in with the Module
Review?
Gj
On Wed, 27 Sep 2017 at 09:06, Christian Lenz <ch...@gmx.net> wrote:
> So I should not doing any PR (my #3 PR will not be merged, right?) and I
> should do it on Feature Branches? How is the process for Review and
> merging? If we have 19275 feature branches, no one knows, when the Feature
> is finish. Maybe we should have a release branch where we should merge the
> stuff from Feature into release or whatever to make it clear: my Feature is
> ready for Review/use etc.
>
> Gesendet von Mail für Windows 10
>
> Von: Geertjan Wielenga
> Gesendet: Mittwoch, 27. September 2017 00:28
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Allow code contributions or focus on release only?
>
> Yup -- and corresponds with what we're doing.
>
> I love it when a plan comes together.
>
> Gj
>
> On Wed, Sep 27, 2017 at 12:03 AM, Wade Chandler <wa...@apache.org>
> wrote:
>
> > That all sounds like a good strategy to me.
> >
> > +1
> >
> > Wade
> >
> > On Sep 26, 2017 17:44, "Craig Russell" <ap...@gmail.com> wrote:
> >
> > > I have no dog in this particular hunt, but if it were up to me I'd
> > > prioritize:
> > >
> > > getting code into repositories with clean RAT reports
> > > getting Netbeans to build and run
> > > creating release(s) for major platforms
> > > ...
> > > serious bug reports
> > > ...
> > > features (in branches)
> > >
> > > Craig
> > >
> > > > On Sep 26, 2017, at 1:16 PM, Sven Reimers <sv...@gmail.com>
> > > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I fully agree with Jan..
> > > >
> > > > Let's try to get something released first so we know the process..
> > > >
> > > > Hope to have some time to review modules real soon now..
> > > >
> > > > -Sven
> > > >
> > > > Am 26.09.2017 22:13 schrieb "Jan Lahoda" <la...@gmail.com>:
> > > >
> > > >> +1 (I think that if we want to get some rest and fun, we could use
> > > branches
> > > >> to experiment with some new features (and I may do so at some
> point),
> > > but
> > > >> we should limit unnecessary changes to master, and use our code
> > > >> review/discussion bandwidth as much as possible for working on a
> > > release)
> > > >>
> > > >> I personally even think we could try to release just the platform
> > (e.g.
> > > >> NetBeans Platform 9.0 beta) once the platform modules are reviewed.
> > That
> > > >> would help us validate whether the approach we are taking makes
> sense
> > > (and
> > > >> what needs to be improved) and would help us learn about the release
> > > >> process (and the platform is a useful thing on its own, so releasing
> > it
> > > >> wouldn't be just an artificial move).
> > > >>
> > > >> Jan
> > > >>
> > > >>
> > > >> On Tue, Sep 26, 2017 at 8:23 PM, Michael Nascimento <
> > misterm@gmail.com>
> > > >> wrote:
> > > >>
> > > >>> Definitely we should focus on getting an Apache NetBeans release.
> > > >>> Sincerely, at this point, I think we should maybe have a Apache
> > > NetBeans
> > > >>> 9.0 Java edition, so we can have something release and then a full
> > > Apache
> > > >>> NB 9.0. Otherwise, sounds like we'll get no release this year,
> which
> > > >> would
> > > >>> be pretty sad.
> > > >>>
> > > >>> Regards,
> > > >>> Michael
> > > >>>
> > > >>> <http://www.avg.com/email-signature?utm_medium=email&
> > > >>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > > >>> Virus-free.
> > > >>> www.avg.com
> > > >>> <http://www.avg.com/email-signature?utm_medium=email&
> > > >>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > > >>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > > >>>
> > > >>> On Tue, Sep 26, 2017 at 4:17 AM, Geertjan Wielenga <
> > > >>> geertjan.wielenga@googlemail.com> wrote:
> > > >>>
> > > >>>> Hi all,
> > > >>>>
> > > >>>> We need to discuss something, I think -- do we begin accepting
> pull
> > > >>>> requests, and thereby encourage pull requests to be created -- or
> do
> > > we
> > > >>>> focus very narrowly on preparing Apache NetBeans for its first
> > > >> incubator
> > > >>>> release?
> > > >>>>
> > > >>>> If we were to focus narrowly on preparing the Apache release, then
> > > this
> > > >>> is
> > > >>>> what we would focus on, nothing else:
> > > >>>>
> > > >>>> https://cwiki.apache.org/confluence/display/NETBEANS/
> > > >>>> List+of+Modules+to+Review
> > > >>>>
> > > >>>> At the same time, of course, people want to add their mark to
> Apache
> > > >>>> NetBeans. And that means code or an icon, a menu item, a new UI
> > thing
> > > >> to
> > > >>>> point at and say -- see, I did that! These kinds of enhancements
> > could
> > > >> be
> > > >>>> done at the same time as the above, and would require that some
> > people
> > > >>>> split their time between doing the module reviews and reviewing
> pull
> > > >>>> requests.
> > > >>>>
> > > >>>> I'm not stating a preference here, just putting the discussion out
> > > >> there,
> > > >>>> since I've seen conflicting opinions about this and I think it
> would
> > > be
> > > >>>> good to discuss this centrally.
> > > >>>>
> > > >>>> Thanks,
> > > >>>>
> > > >>>> Gj
> > > >>>>
> > > >>>
> > > >>
> > >
> > > Craig L Russell
> > > Secretary, Apache Software Foundation
> > > clr@apache.org http://db.apache.org/jdo
> > >
> > >
> >
>
>
AW: Allow code contributions or focus on release only?
Posted by Christian Lenz <ch...@gmx.net>.
So I should not doing any PR (my #3 PR will not be merged, right?) and I should do it on Feature Branches? How is the process for Review and merging? If we have 19275 feature branches, no one knows, when the Feature is finish. Maybe we should have a release branch where we should merge the stuff from Feature into release or whatever to make it clear: my Feature is ready for Review/use etc.
Gesendet von Mail für Windows 10
Von: Geertjan Wielenga
Gesendet: Mittwoch, 27. September 2017 00:28
An: dev@netbeans.incubator.apache.org
Betreff: Re: Allow code contributions or focus on release only?
Yup -- and corresponds with what we're doing.
I love it when a plan comes together.
Gj
On Wed, Sep 27, 2017 at 12:03 AM, Wade Chandler <wa...@apache.org>
wrote:
> That all sounds like a good strategy to me.
>
> +1
>
> Wade
>
> On Sep 26, 2017 17:44, "Craig Russell" <ap...@gmail.com> wrote:
>
> > I have no dog in this particular hunt, but if it were up to me I'd
> > prioritize:
> >
> > getting code into repositories with clean RAT reports
> > getting Netbeans to build and run
> > creating release(s) for major platforms
> > ...
> > serious bug reports
> > ...
> > features (in branches)
> >
> > Craig
> >
> > > On Sep 26, 2017, at 1:16 PM, Sven Reimers <sv...@gmail.com>
> > wrote:
> > >
> > > Hi all,
> > >
> > > I fully agree with Jan..
> > >
> > > Let's try to get something released first so we know the process..
> > >
> > > Hope to have some time to review modules real soon now..
> > >
> > > -Sven
> > >
> > > Am 26.09.2017 22:13 schrieb "Jan Lahoda" <la...@gmail.com>:
> > >
> > >> +1 (I think that if we want to get some rest and fun, we could use
> > branches
> > >> to experiment with some new features (and I may do so at some point),
> > but
> > >> we should limit unnecessary changes to master, and use our code
> > >> review/discussion bandwidth as much as possible for working on a
> > release)
> > >>
> > >> I personally even think we could try to release just the platform
> (e.g.
> > >> NetBeans Platform 9.0 beta) once the platform modules are reviewed.
> That
> > >> would help us validate whether the approach we are taking makes sense
> > (and
> > >> what needs to be improved) and would help us learn about the release
> > >> process (and the platform is a useful thing on its own, so releasing
> it
> > >> wouldn't be just an artificial move).
> > >>
> > >> Jan
> > >>
> > >>
> > >> On Tue, Sep 26, 2017 at 8:23 PM, Michael Nascimento <
> misterm@gmail.com>
> > >> wrote:
> > >>
> > >>> Definitely we should focus on getting an Apache NetBeans release.
> > >>> Sincerely, at this point, I think we should maybe have a Apache
> > NetBeans
> > >>> 9.0 Java edition, so we can have something release and then a full
> > Apache
> > >>> NB 9.0. Otherwise, sounds like we'll get no release this year, which
> > >> would
> > >>> be pretty sad.
> > >>>
> > >>> Regards,
> > >>> Michael
> > >>>
> > >>> <http://www.avg.com/email-signature?utm_medium=email&
> > >>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > >>> Virus-free.
> > >>> www.avg.com
> > >>> <http://www.avg.com/email-signature?utm_medium=email&
> > >>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > >>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > >>>
> > >>> On Tue, Sep 26, 2017 at 4:17 AM, Geertjan Wielenga <
> > >>> geertjan.wielenga@googlemail.com> wrote:
> > >>>
> > >>>> Hi all,
> > >>>>
> > >>>> We need to discuss something, I think -- do we begin accepting pull
> > >>>> requests, and thereby encourage pull requests to be created -- or do
> > we
> > >>>> focus very narrowly on preparing Apache NetBeans for its first
> > >> incubator
> > >>>> release?
> > >>>>
> > >>>> If we were to focus narrowly on preparing the Apache release, then
> > this
> > >>> is
> > >>>> what we would focus on, nothing else:
> > >>>>
> > >>>> https://cwiki.apache.org/confluence/display/NETBEANS/
> > >>>> List+of+Modules+to+Review
> > >>>>
> > >>>> At the same time, of course, people want to add their mark to Apache
> > >>>> NetBeans. And that means code or an icon, a menu item, a new UI
> thing
> > >> to
> > >>>> point at and say -- see, I did that! These kinds of enhancements
> could
> > >> be
> > >>>> done at the same time as the above, and would require that some
> people
> > >>>> split their time between doing the module reviews and reviewing pull
> > >>>> requests.
> > >>>>
> > >>>> I'm not stating a preference here, just putting the discussion out
> > >> there,
> > >>>> since I've seen conflicting opinions about this and I think it would
> > be
> > >>>> good to discuss this centrally.
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> Gj
> > >>>>
> > >>>
> > >>
> >
> > Craig L Russell
> > Secretary, Apache Software Foundation
> > clr@apache.org http://db.apache.org/jdo
> >
> >
>
Re: Allow code contributions or focus on release only?
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Yup -- and corresponds with what we're doing.
I love it when a plan comes together.
Gj
On Wed, Sep 27, 2017 at 12:03 AM, Wade Chandler <wa...@apache.org>
wrote:
> That all sounds like a good strategy to me.
>
> +1
>
> Wade
>
> On Sep 26, 2017 17:44, "Craig Russell" <ap...@gmail.com> wrote:
>
> > I have no dog in this particular hunt, but if it were up to me I'd
> > prioritize:
> >
> > getting code into repositories with clean RAT reports
> > getting Netbeans to build and run
> > creating release(s) for major platforms
> > ...
> > serious bug reports
> > ...
> > features (in branches)
> >
> > Craig
> >
> > > On Sep 26, 2017, at 1:16 PM, Sven Reimers <sv...@gmail.com>
> > wrote:
> > >
> > > Hi all,
> > >
> > > I fully agree with Jan..
> > >
> > > Let's try to get something released first so we know the process..
> > >
> > > Hope to have some time to review modules real soon now..
> > >
> > > -Sven
> > >
> > > Am 26.09.2017 22:13 schrieb "Jan Lahoda" <la...@gmail.com>:
> > >
> > >> +1 (I think that if we want to get some rest and fun, we could use
> > branches
> > >> to experiment with some new features (and I may do so at some point),
> > but
> > >> we should limit unnecessary changes to master, and use our code
> > >> review/discussion bandwidth as much as possible for working on a
> > release)
> > >>
> > >> I personally even think we could try to release just the platform
> (e.g.
> > >> NetBeans Platform 9.0 beta) once the platform modules are reviewed.
> That
> > >> would help us validate whether the approach we are taking makes sense
> > (and
> > >> what needs to be improved) and would help us learn about the release
> > >> process (and the platform is a useful thing on its own, so releasing
> it
> > >> wouldn't be just an artificial move).
> > >>
> > >> Jan
> > >>
> > >>
> > >> On Tue, Sep 26, 2017 at 8:23 PM, Michael Nascimento <
> misterm@gmail.com>
> > >> wrote:
> > >>
> > >>> Definitely we should focus on getting an Apache NetBeans release.
> > >>> Sincerely, at this point, I think we should maybe have a Apache
> > NetBeans
> > >>> 9.0 Java edition, so we can have something release and then a full
> > Apache
> > >>> NB 9.0. Otherwise, sounds like we'll get no release this year, which
> > >> would
> > >>> be pretty sad.
> > >>>
> > >>> Regards,
> > >>> Michael
> > >>>
> > >>> <http://www.avg.com/email-signature?utm_medium=email&
> > >>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > >>> Virus-free.
> > >>> www.avg.com
> > >>> <http://www.avg.com/email-signature?utm_medium=email&
> > >>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > >>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> > >>>
> > >>> On Tue, Sep 26, 2017 at 4:17 AM, Geertjan Wielenga <
> > >>> geertjan.wielenga@googlemail.com> wrote:
> > >>>
> > >>>> Hi all,
> > >>>>
> > >>>> We need to discuss something, I think -- do we begin accepting pull
> > >>>> requests, and thereby encourage pull requests to be created -- or do
> > we
> > >>>> focus very narrowly on preparing Apache NetBeans for its first
> > >> incubator
> > >>>> release?
> > >>>>
> > >>>> If we were to focus narrowly on preparing the Apache release, then
> > this
> > >>> is
> > >>>> what we would focus on, nothing else:
> > >>>>
> > >>>> https://cwiki.apache.org/confluence/display/NETBEANS/
> > >>>> List+of+Modules+to+Review
> > >>>>
> > >>>> At the same time, of course, people want to add their mark to Apache
> > >>>> NetBeans. And that means code or an icon, a menu item, a new UI
> thing
> > >> to
> > >>>> point at and say -- see, I did that! These kinds of enhancements
> could
> > >> be
> > >>>> done at the same time as the above, and would require that some
> people
> > >>>> split their time between doing the module reviews and reviewing pull
> > >>>> requests.
> > >>>>
> > >>>> I'm not stating a preference here, just putting the discussion out
> > >> there,
> > >>>> since I've seen conflicting opinions about this and I think it would
> > be
> > >>>> good to discuss this centrally.
> > >>>>
> > >>>> Thanks,
> > >>>>
> > >>>> Gj
> > >>>>
> > >>>
> > >>
> >
> > Craig L Russell
> > Secretary, Apache Software Foundation
> > clr@apache.org http://db.apache.org/jdo
> >
> >
>
Re: Allow code contributions or focus on release only?
Posted by Wade Chandler <wa...@apache.org>.
That all sounds like a good strategy to me.
+1
Wade
On Sep 26, 2017 17:44, "Craig Russell" <ap...@gmail.com> wrote:
> I have no dog in this particular hunt, but if it were up to me I'd
> prioritize:
>
> getting code into repositories with clean RAT reports
> getting Netbeans to build and run
> creating release(s) for major platforms
> ...
> serious bug reports
> ...
> features (in branches)
>
> Craig
>
> > On Sep 26, 2017, at 1:16 PM, Sven Reimers <sv...@gmail.com>
> wrote:
> >
> > Hi all,
> >
> > I fully agree with Jan..
> >
> > Let's try to get something released first so we know the process..
> >
> > Hope to have some time to review modules real soon now..
> >
> > -Sven
> >
> > Am 26.09.2017 22:13 schrieb "Jan Lahoda" <la...@gmail.com>:
> >
> >> +1 (I think that if we want to get some rest and fun, we could use
> branches
> >> to experiment with some new features (and I may do so at some point),
> but
> >> we should limit unnecessary changes to master, and use our code
> >> review/discussion bandwidth as much as possible for working on a
> release)
> >>
> >> I personally even think we could try to release just the platform (e.g.
> >> NetBeans Platform 9.0 beta) once the platform modules are reviewed. That
> >> would help us validate whether the approach we are taking makes sense
> (and
> >> what needs to be improved) and would help us learn about the release
> >> process (and the platform is a useful thing on its own, so releasing it
> >> wouldn't be just an artificial move).
> >>
> >> Jan
> >>
> >>
> >> On Tue, Sep 26, 2017 at 8:23 PM, Michael Nascimento <mi...@gmail.com>
> >> wrote:
> >>
> >>> Definitely we should focus on getting an Apache NetBeans release.
> >>> Sincerely, at this point, I think we should maybe have a Apache
> NetBeans
> >>> 9.0 Java edition, so we can have something release and then a full
> Apache
> >>> NB 9.0. Otherwise, sounds like we'll get no release this year, which
> >> would
> >>> be pretty sad.
> >>>
> >>> Regards,
> >>> Michael
> >>>
> >>> <http://www.avg.com/email-signature?utm_medium=email&
> >>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> >>> Virus-free.
> >>> www.avg.com
> >>> <http://www.avg.com/email-signature?utm_medium=email&
> >>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> >>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >>>
> >>> On Tue, Sep 26, 2017 at 4:17 AM, Geertjan Wielenga <
> >>> geertjan.wielenga@googlemail.com> wrote:
> >>>
> >>>> Hi all,
> >>>>
> >>>> We need to discuss something, I think -- do we begin accepting pull
> >>>> requests, and thereby encourage pull requests to be created -- or do
> we
> >>>> focus very narrowly on preparing Apache NetBeans for its first
> >> incubator
> >>>> release?
> >>>>
> >>>> If we were to focus narrowly on preparing the Apache release, then
> this
> >>> is
> >>>> what we would focus on, nothing else:
> >>>>
> >>>> https://cwiki.apache.org/confluence/display/NETBEANS/
> >>>> List+of+Modules+to+Review
> >>>>
> >>>> At the same time, of course, people want to add their mark to Apache
> >>>> NetBeans. And that means code or an icon, a menu item, a new UI thing
> >> to
> >>>> point at and say -- see, I did that! These kinds of enhancements could
> >> be
> >>>> done at the same time as the above, and would require that some people
> >>>> split their time between doing the module reviews and reviewing pull
> >>>> requests.
> >>>>
> >>>> I'm not stating a preference here, just putting the discussion out
> >> there,
> >>>> since I've seen conflicting opinions about this and I think it would
> be
> >>>> good to discuss this centrally.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> Gj
> >>>>
> >>>
> >>
>
> Craig L Russell
> Secretary, Apache Software Foundation
> clr@apache.org http://db.apache.org/jdo
>
>
Re: Allow code contributions or focus on release only?
Posted by Craig Russell <ap...@gmail.com>.
I have no dog in this particular hunt, but if it were up to me I'd prioritize:
getting code into repositories with clean RAT reports
getting Netbeans to build and run
creating release(s) for major platforms
...
serious bug reports
...
features (in branches)
Craig
> On Sep 26, 2017, at 1:16 PM, Sven Reimers <sv...@gmail.com> wrote:
>
> Hi all,
>
> I fully agree with Jan..
>
> Let's try to get something released first so we know the process..
>
> Hope to have some time to review modules real soon now..
>
> -Sven
>
> Am 26.09.2017 22:13 schrieb "Jan Lahoda" <la...@gmail.com>:
>
>> +1 (I think that if we want to get some rest and fun, we could use branches
>> to experiment with some new features (and I may do so at some point), but
>> we should limit unnecessary changes to master, and use our code
>> review/discussion bandwidth as much as possible for working on a release)
>>
>> I personally even think we could try to release just the platform (e.g.
>> NetBeans Platform 9.0 beta) once the platform modules are reviewed. That
>> would help us validate whether the approach we are taking makes sense (and
>> what needs to be improved) and would help us learn about the release
>> process (and the platform is a useful thing on its own, so releasing it
>> wouldn't be just an artificial move).
>>
>> Jan
>>
>>
>> On Tue, Sep 26, 2017 at 8:23 PM, Michael Nascimento <mi...@gmail.com>
>> wrote:
>>
>>> Definitely we should focus on getting an Apache NetBeans release.
>>> Sincerely, at this point, I think we should maybe have a Apache NetBeans
>>> 9.0 Java edition, so we can have something release and then a full Apache
>>> NB 9.0. Otherwise, sounds like we'll get no release this year, which
>> would
>>> be pretty sad.
>>>
>>> Regards,
>>> Michael
>>>
>>> <http://www.avg.com/email-signature?utm_medium=email&
>>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>>> Virus-free.
>>> www.avg.com
>>> <http://www.avg.com/email-signature?utm_medium=email&
>>> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
>>> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>> On Tue, Sep 26, 2017 at 4:17 AM, Geertjan Wielenga <
>>> geertjan.wielenga@googlemail.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> We need to discuss something, I think -- do we begin accepting pull
>>>> requests, and thereby encourage pull requests to be created -- or do we
>>>> focus very narrowly on preparing Apache NetBeans for its first
>> incubator
>>>> release?
>>>>
>>>> If we were to focus narrowly on preparing the Apache release, then this
>>> is
>>>> what we would focus on, nothing else:
>>>>
>>>> https://cwiki.apache.org/confluence/display/NETBEANS/
>>>> List+of+Modules+to+Review
>>>>
>>>> At the same time, of course, people want to add their mark to Apache
>>>> NetBeans. And that means code or an icon, a menu item, a new UI thing
>> to
>>>> point at and say -- see, I did that! These kinds of enhancements could
>> be
>>>> done at the same time as the above, and would require that some people
>>>> split their time between doing the module reviews and reviewing pull
>>>> requests.
>>>>
>>>> I'm not stating a preference here, just putting the discussion out
>> there,
>>>> since I've seen conflicting opinions about this and I think it would be
>>>> good to discuss this centrally.
>>>>
>>>> Thanks,
>>>>
>>>> Gj
>>>>
>>>
>>
Craig L Russell
Secretary, Apache Software Foundation
clr@apache.org http://db.apache.org/jdo
Re: Allow code contributions or focus on release only?
Posted by Sven Reimers <sv...@gmail.com>.
Hi all,
I fully agree with Jan..
Let's try to get something released first so we know the process..
Hope to have some time to review modules real soon now..
-Sven
Am 26.09.2017 22:13 schrieb "Jan Lahoda" <la...@gmail.com>:
> +1 (I think that if we want to get some rest and fun, we could use branches
> to experiment with some new features (and I may do so at some point), but
> we should limit unnecessary changes to master, and use our code
> review/discussion bandwidth as much as possible for working on a release)
>
> I personally even think we could try to release just the platform (e.g.
> NetBeans Platform 9.0 beta) once the platform modules are reviewed. That
> would help us validate whether the approach we are taking makes sense (and
> what needs to be improved) and would help us learn about the release
> process (and the platform is a useful thing on its own, so releasing it
> wouldn't be just an artificial move).
>
> Jan
>
>
> On Tue, Sep 26, 2017 at 8:23 PM, Michael Nascimento <mi...@gmail.com>
> wrote:
>
> > Definitely we should focus on getting an Apache NetBeans release.
> > Sincerely, at this point, I think we should maybe have a Apache NetBeans
> > 9.0 Java edition, so we can have something release and then a full Apache
> > NB 9.0. Otherwise, sounds like we'll get no release this year, which
> would
> > be pretty sad.
> >
> > Regards,
> > Michael
> >
> > <http://www.avg.com/email-signature?utm_medium=email&
> > utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > Virus-free.
> > www.avg.com
> > <http://www.avg.com/email-signature?utm_medium=email&
> > utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> > <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
> >
> > On Tue, Sep 26, 2017 at 4:17 AM, Geertjan Wielenga <
> > geertjan.wielenga@googlemail.com> wrote:
> >
> > > Hi all,
> > >
> > > We need to discuss something, I think -- do we begin accepting pull
> > > requests, and thereby encourage pull requests to be created -- or do we
> > > focus very narrowly on preparing Apache NetBeans for its first
> incubator
> > > release?
> > >
> > > If we were to focus narrowly on preparing the Apache release, then this
> > is
> > > what we would focus on, nothing else:
> > >
> > > https://cwiki.apache.org/confluence/display/NETBEANS/
> > > List+of+Modules+to+Review
> > >
> > > At the same time, of course, people want to add their mark to Apache
> > > NetBeans. And that means code or an icon, a menu item, a new UI thing
> to
> > > point at and say -- see, I did that! These kinds of enhancements could
> be
> > > done at the same time as the above, and would require that some people
> > > split their time between doing the module reviews and reviewing pull
> > > requests.
> > >
> > > I'm not stating a preference here, just putting the discussion out
> there,
> > > since I've seen conflicting opinions about this and I think it would be
> > > good to discuss this centrally.
> > >
> > > Thanks,
> > >
> > > Gj
> > >
> >
>
Re: Allow code contributions or focus on release only?
Posted by Jan Lahoda <la...@gmail.com>.
+1 (I think that if we want to get some rest and fun, we could use branches
to experiment with some new features (and I may do so at some point), but
we should limit unnecessary changes to master, and use our code
review/discussion bandwidth as much as possible for working on a release)
I personally even think we could try to release just the platform (e.g.
NetBeans Platform 9.0 beta) once the platform modules are reviewed. That
would help us validate whether the approach we are taking makes sense (and
what needs to be improved) and would help us learn about the release
process (and the platform is a useful thing on its own, so releasing it
wouldn't be just an artificial move).
Jan
On Tue, Sep 26, 2017 at 8:23 PM, Michael Nascimento <mi...@gmail.com>
wrote:
> Definitely we should focus on getting an Apache NetBeans release.
> Sincerely, at this point, I think we should maybe have a Apache NetBeans
> 9.0 Java edition, so we can have something release and then a full Apache
> NB 9.0. Otherwise, sounds like we'll get no release this year, which would
> be pretty sad.
>
> Regards,
> Michael
>
> <http://www.avg.com/email-signature?utm_medium=email&
> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> Virus-free.
> www.avg.com
> <http://www.avg.com/email-signature?utm_medium=email&
> utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Tue, Sep 26, 2017 at 4:17 AM, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
> > Hi all,
> >
> > We need to discuss something, I think -- do we begin accepting pull
> > requests, and thereby encourage pull requests to be created -- or do we
> > focus very narrowly on preparing Apache NetBeans for its first incubator
> > release?
> >
> > If we were to focus narrowly on preparing the Apache release, then this
> is
> > what we would focus on, nothing else:
> >
> > https://cwiki.apache.org/confluence/display/NETBEANS/
> > List+of+Modules+to+Review
> >
> > At the same time, of course, people want to add their mark to Apache
> > NetBeans. And that means code or an icon, a menu item, a new UI thing to
> > point at and say -- see, I did that! These kinds of enhancements could be
> > done at the same time as the above, and would require that some people
> > split their time between doing the module reviews and reviewing pull
> > requests.
> >
> > I'm not stating a preference here, just putting the discussion out there,
> > since I've seen conflicting opinions about this and I think it would be
> > good to discuss this centrally.
> >
> > Thanks,
> >
> > Gj
> >
>
Re: Allow code contributions or focus on release only?
Posted by Michael Nascimento <mi...@gmail.com>.
Definitely we should focus on getting an Apache NetBeans release.
Sincerely, at this point, I think we should maybe have a Apache NetBeans
9.0 Java edition, so we can have something release and then a full Apache
NB 9.0. Otherwise, sounds like we'll get no release this year, which would
be pretty sad.
Regards,
Michael
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
On Tue, Sep 26, 2017 at 4:17 AM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> Hi all,
>
> We need to discuss something, I think -- do we begin accepting pull
> requests, and thereby encourage pull requests to be created -- or do we
> focus very narrowly on preparing Apache NetBeans for its first incubator
> release?
>
> If we were to focus narrowly on preparing the Apache release, then this is
> what we would focus on, nothing else:
>
> https://cwiki.apache.org/confluence/display/NETBEANS/
> List+of+Modules+to+Review
>
> At the same time, of course, people want to add their mark to Apache
> NetBeans. And that means code or an icon, a menu item, a new UI thing to
> point at and say -- see, I did that! These kinds of enhancements could be
> done at the same time as the above, and would require that some people
> split their time between doing the module reviews and reviewing pull
> requests.
>
> I'm not stating a preference here, just putting the discussion out there,
> since I've seen conflicting opinions about this and I think it would be
> good to discuss this centrally.
>
> Thanks,
>
> Gj
>
Re: Allow code contributions or focus on release only?
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Also, do take note of the advice earlier in this thread from Craig Russell:
I have no dog in this particular hunt, but if it were up to me I'd
> prioritize:
>
> getting code into repositories with clean RAT reports
> getting Netbeans to build and run
> creating release(s) for major platforms
> ...
> serious bug reports
> ...
> features (in branches)
>
However, sure, we can take a different path.
Gj
On Wed, Sep 27, 2017 at 9:35 AM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> Sure, this is why I opened this discussion thread, to see how people feel
> about this. I.e., this is precisely the discussion, do people think we
> should focus narrowly on getting the Apache NetBeans release done or should
> we focus on bug fixes and features too. All options are open.
>
> Gj
>
> On Wed, Sep 27, 2017 at 9:33 AM, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
>> There's heaps of improvements: https://cwiki.ap
>> ache.org/confluence/display/NETBEANS/NetBeans+9.0+-+New+and+Noteworthy
>>
>> Gj
>>
>> On Wed, Sep 27, 2017 at 9:27 AM, Emilian Bold <em...@gmail.com>
>> wrote:
>>
>>> We should also allow some new features and improvements. We cannot have
>>> NetBeans under Apache for 1 year and basically have no Apache-contributed
>>> feature to show for, only IP cleanup and stuff like that.
>>>
>>> There's a whole lot of contributors and committers: does everybody want
>>> to
>>> do only this? Because I don't!
>>>
>>> BTW, how many are being involved in the new Apache build system or IP
>>> clearance, etc.? I don't see people jumping in on this rather boring job.
>>>
>>> So, I *am* doing IP cleanup, but I would most certainly want to commit
>>> new
>>> features and bugfixes! I found and fixed a few bugs just these weeks
>>> while
>>> working on yameter.com
>>>
>>> I don't remember agreeing on a feature freeze within Apache, we just got
>>> the codebase donated.
>>>
>>> The community should be able to walk and chew bubble gum at the same
>>> time.
>>> If some people are focusing on the build system I don't see why other
>>> people can't focus on something else as long as they don't break
>>> something
>>> or get in the way?
>>>
>>> The real question is: are we really distributing the load *and trust*
>>> among
>>> committers or not? Because it seems to me everybody is very willing to
>>> heavily restrict what we should be allowed to do.
>>>
>>>
>>>
>>> --emi
>>>
>>> On Tue, Sep 26, 2017 at 9:14 PM, Matthias Bläsing <
>>> mblaesing@doppel-helix.eu
>>> > wrote:
>>>
>>> > Hey,
>>> >
>>> > Am Dienstag, den 26.09.2017, 09:17 +0200 schrieb Geertjan Wielenga:
>>> > > [Discuss-Request: Focus on getting a release out or adding functions]
>>> >
>>> > if I'm not mistaken, the netbeans 9 feature freeze had already happened
>>> > when the migration to apache began. I would focus on bugfixing and
>>> > blocking new features.
>>> >
>>> > With the apache migration process there is enough development needed,
>>> > just to get the codebase releaseable. Libraries need to
>>> > removed/replaced, if the are incompatibe with the apache project
>>> > (SwingX is LGPL and so can't be distributed with apache netbeans) or
>>> > installers to get these libraries at runtime need to be implemented.
>>> >
>>> > While I agree, that adding new features would pull more potential
>>> > contributers, I would consider a stable base more important, to get
>>> > going from there. Java 9 is out and the excitement is already there and
>>> > people ask for netbeans 9, so I would prioritize that.
>>> >
>>> > My 2 cent
>>> >
>>> > Matthias
>>> >
>>> >
>>> >
>>>
>>
>>
>
Re: Allow code contributions or focus on release only?
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Yup, that's all true. However, the point is, there's many new features that
have not been released yet that are in the Apache NetBeans code base.
Again, I have no fixed opinion myself, and I agree it would be great to
have lots of new features and lots of bug fixes.
The only point I have, if any at all, is that we will never release those
bugs or features until we work through the Modules Review. And the
knowledge required to do that review is really minimal, it is not a code
review, just a license review. Without completing that, Apache NetBeans
will never be released and is, in fact, dead.
Gj
On Wed, Sep 27, 2017 at 9:39 AM, Christian Lenz <ch...@gmx.net>
wrote:
> The page will not show the list of any bug fixes. Only Features and I
> think or hope that this list is not completed yet, because it is only a
> countable amount of Features. When we have a look into older Major
> Releases, there was a lot of more AND the other, 2nd Code donation here is
> missing, so PHP too (I think) All, what is not Java will not coming in the
> first NB 9 release. Afaik. So no C/C++ Features and no PHP Support.
>
> Gesendet von Mail für Windows 10
>
> Von: Geertjan Wielenga
> Gesendet: Mittwoch, 27. September 2017 09:35
> An: dev@netbeans.incubator.apache.org
> Betreff: Re: Allow code contributions or focus on release only?
>
> Sure, this is why I opened this discussion thread, to see how people feel
> about this. I.e., this is precisely the discussion, do people think we
> should focus narrowly on getting the Apache NetBeans release done or should
> we focus on bug fixes and features too. All options are open.
>
> Gj
>
> On Wed, Sep 27, 2017 at 9:33 AM, Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
> > There's heaps of improvements: https://cwiki.
> > apache.org/confluence/display/NETBEANS/NetBeans+9.0+-+New+and+Noteworthy
> >
> > Gj
> >
> > On Wed, Sep 27, 2017 at 9:27 AM, Emilian Bold <em...@gmail.com>
> > wrote:
> >
> >> We should also allow some new features and improvements. We cannot have
> >> NetBeans under Apache for 1 year and basically have no
> Apache-contributed
> >> feature to show for, only IP cleanup and stuff like that.
> >>
> >> There's a whole lot of contributors and committers: does everybody want
> to
> >> do only this? Because I don't!
> >>
> >> BTW, how many are being involved in the new Apache build system or IP
> >> clearance, etc.? I don't see people jumping in on this rather boring
> job.
> >>
> >> So, I *am* doing IP cleanup, but I would most certainly want to commit
> new
> >> features and bugfixes! I found and fixed a few bugs just these weeks
> while
> >> working on yameter.com
> >>
> >> I don't remember agreeing on a feature freeze within Apache, we just got
> >> the codebase donated.
> >>
> >> The community should be able to walk and chew bubble gum at the same
> time.
> >> If some people are focusing on the build system I don't see why other
> >> people can't focus on something else as long as they don't break
> something
> >> or get in the way?
> >>
> >> The real question is: are we really distributing the load *and trust*
> >> among
> >> committers or not? Because it seems to me everybody is very willing to
> >> heavily restrict what we should be allowed to do.
> >>
> >>
> >>
> >> --emi
> >>
> >> On Tue, Sep 26, 2017 at 9:14 PM, Matthias Bläsing <
> >> mblaesing@doppel-helix.eu
> >> > wrote:
> >>
> >> > Hey,
> >> >
> >> > Am Dienstag, den 26.09.2017, 09:17 +0200 schrieb Geertjan Wielenga:
> >> > > [Discuss-Request: Focus on getting a release out or adding
> functions]
> >> >
> >> > if I'm not mistaken, the netbeans 9 feature freeze had already
> happened
> >> > when the migration to apache began. I would focus on bugfixing and
> >> > blocking new features.
> >> >
> >> > With the apache migration process there is enough development needed,
> >> > just to get the codebase releaseable. Libraries need to
> >> > removed/replaced, if the are incompatibe with the apache project
> >> > (SwingX is LGPL and so can't be distributed with apache netbeans) or
> >> > installers to get these libraries at runtime need to be implemented.
> >> >
> >> > While I agree, that adding new features would pull more potential
> >> > contributers, I would consider a stable base more important, to get
> >> > going from there. Java 9 is out and the excitement is already there
> and
> >> > people ask for netbeans 9, so I would prioritize that.
> >> >
> >> > My 2 cent
> >> >
> >> > Matthias
> >> >
> >> >
> >> >
> >>
> >
> >
>
>
AW: Allow code contributions or focus on release only?
Posted by Christian Lenz <ch...@gmx.net>.
The page will not show the list of any bug fixes. Only Features and I think or hope that this list is not completed yet, because it is only a countable amount of Features. When we have a look into older Major Releases, there was a lot of more AND the other, 2nd Code donation here is missing, so PHP too (I think) All, what is not Java will not coming in the first NB 9 release. Afaik. So no C/C++ Features and no PHP Support.
Gesendet von Mail für Windows 10
Von: Geertjan Wielenga
Gesendet: Mittwoch, 27. September 2017 09:35
An: dev@netbeans.incubator.apache.org
Betreff: Re: Allow code contributions or focus on release only?
Sure, this is why I opened this discussion thread, to see how people feel
about this. I.e., this is precisely the discussion, do people think we
should focus narrowly on getting the Apache NetBeans release done or should
we focus on bug fixes and features too. All options are open.
Gj
On Wed, Sep 27, 2017 at 9:33 AM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> There's heaps of improvements: https://cwiki.
> apache.org/confluence/display/NETBEANS/NetBeans+9.0+-+New+and+Noteworthy
>
> Gj
>
> On Wed, Sep 27, 2017 at 9:27 AM, Emilian Bold <em...@gmail.com>
> wrote:
>
>> We should also allow some new features and improvements. We cannot have
>> NetBeans under Apache for 1 year and basically have no Apache-contributed
>> feature to show for, only IP cleanup and stuff like that.
>>
>> There's a whole lot of contributors and committers: does everybody want to
>> do only this? Because I don't!
>>
>> BTW, how many are being involved in the new Apache build system or IP
>> clearance, etc.? I don't see people jumping in on this rather boring job.
>>
>> So, I *am* doing IP cleanup, but I would most certainly want to commit new
>> features and bugfixes! I found and fixed a few bugs just these weeks while
>> working on yameter.com
>>
>> I don't remember agreeing on a feature freeze within Apache, we just got
>> the codebase donated.
>>
>> The community should be able to walk and chew bubble gum at the same time.
>> If some people are focusing on the build system I don't see why other
>> people can't focus on something else as long as they don't break something
>> or get in the way?
>>
>> The real question is: are we really distributing the load *and trust*
>> among
>> committers or not? Because it seems to me everybody is very willing to
>> heavily restrict what we should be allowed to do.
>>
>>
>>
>> --emi
>>
>> On Tue, Sep 26, 2017 at 9:14 PM, Matthias Bläsing <
>> mblaesing@doppel-helix.eu
>> > wrote:
>>
>> > Hey,
>> >
>> > Am Dienstag, den 26.09.2017, 09:17 +0200 schrieb Geertjan Wielenga:
>> > > [Discuss-Request: Focus on getting a release out or adding functions]
>> >
>> > if I'm not mistaken, the netbeans 9 feature freeze had already happened
>> > when the migration to apache began. I would focus on bugfixing and
>> > blocking new features.
>> >
>> > With the apache migration process there is enough development needed,
>> > just to get the codebase releaseable. Libraries need to
>> > removed/replaced, if the are incompatibe with the apache project
>> > (SwingX is LGPL and so can't be distributed with apache netbeans) or
>> > installers to get these libraries at runtime need to be implemented.
>> >
>> > While I agree, that adding new features would pull more potential
>> > contributers, I would consider a stable base more important, to get
>> > going from there. Java 9 is out and the excitement is already there and
>> > people ask for netbeans 9, so I would prioritize that.
>> >
>> > My 2 cent
>> >
>> > Matthias
>> >
>> >
>> >
>>
>
>
Re: Allow code contributions or focus on release only?
Posted by Geertjan Wielenga <ge...@googlemail.com>.
Sure, this is why I opened this discussion thread, to see how people feel
about this. I.e., this is precisely the discussion, do people think we
should focus narrowly on getting the Apache NetBeans release done or should
we focus on bug fixes and features too. All options are open.
Gj
On Wed, Sep 27, 2017 at 9:33 AM, Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> There's heaps of improvements: https://cwiki.
> apache.org/confluence/display/NETBEANS/NetBeans+9.0+-+New+and+Noteworthy
>
> Gj
>
> On Wed, Sep 27, 2017 at 9:27 AM, Emilian Bold <em...@gmail.com>
> wrote:
>
>> We should also allow some new features and improvements. We cannot have
>> NetBeans under Apache for 1 year and basically have no Apache-contributed
>> feature to show for, only IP cleanup and stuff like that.
>>
>> There's a whole lot of contributors and committers: does everybody want to
>> do only this? Because I don't!
>>
>> BTW, how many are being involved in the new Apache build system or IP
>> clearance, etc.? I don't see people jumping in on this rather boring job.
>>
>> So, I *am* doing IP cleanup, but I would most certainly want to commit new
>> features and bugfixes! I found and fixed a few bugs just these weeks while
>> working on yameter.com
>>
>> I don't remember agreeing on a feature freeze within Apache, we just got
>> the codebase donated.
>>
>> The community should be able to walk and chew bubble gum at the same time.
>> If some people are focusing on the build system I don't see why other
>> people can't focus on something else as long as they don't break something
>> or get in the way?
>>
>> The real question is: are we really distributing the load *and trust*
>> among
>> committers or not? Because it seems to me everybody is very willing to
>> heavily restrict what we should be allowed to do.
>>
>>
>>
>> --emi
>>
>> On Tue, Sep 26, 2017 at 9:14 PM, Matthias Bläsing <
>> mblaesing@doppel-helix.eu
>> > wrote:
>>
>> > Hey,
>> >
>> > Am Dienstag, den 26.09.2017, 09:17 +0200 schrieb Geertjan Wielenga:
>> > > [Discuss-Request: Focus on getting a release out or adding functions]
>> >
>> > if I'm not mistaken, the netbeans 9 feature freeze had already happened
>> > when the migration to apache began. I would focus on bugfixing and
>> > blocking new features.
>> >
>> > With the apache migration process there is enough development needed,
>> > just to get the codebase releaseable. Libraries need to
>> > removed/replaced, if the are incompatibe with the apache project
>> > (SwingX is LGPL and so can't be distributed with apache netbeans) or
>> > installers to get these libraries at runtime need to be implemented.
>> >
>> > While I agree, that adding new features would pull more potential
>> > contributers, I would consider a stable base more important, to get
>> > going from there. Java 9 is out and the excitement is already there and
>> > people ask for netbeans 9, so I would prioritize that.
>> >
>> > My 2 cent
>> >
>> > Matthias
>> >
>> >
>> >
>>
>
>
Re: Allow code contributions or focus on release only?
Posted by Geertjan Wielenga <ge...@googlemail.com>.
There's heaps of improvements:
https://cwiki.apache.org/confluence/display/NETBEANS/NetBeans+9.0+-+New+and+Noteworthy
Gj
On Wed, Sep 27, 2017 at 9:27 AM, Emilian Bold <em...@gmail.com>
wrote:
> We should also allow some new features and improvements. We cannot have
> NetBeans under Apache for 1 year and basically have no Apache-contributed
> feature to show for, only IP cleanup and stuff like that.
>
> There's a whole lot of contributors and committers: does everybody want to
> do only this? Because I don't!
>
> BTW, how many are being involved in the new Apache build system or IP
> clearance, etc.? I don't see people jumping in on this rather boring job.
>
> So, I *am* doing IP cleanup, but I would most certainly want to commit new
> features and bugfixes! I found and fixed a few bugs just these weeks while
> working on yameter.com
>
> I don't remember agreeing on a feature freeze within Apache, we just got
> the codebase donated.
>
> The community should be able to walk and chew bubble gum at the same time.
> If some people are focusing on the build system I don't see why other
> people can't focus on something else as long as they don't break something
> or get in the way?
>
> The real question is: are we really distributing the load *and trust* among
> committers or not? Because it seems to me everybody is very willing to
> heavily restrict what we should be allowed to do.
>
>
>
> --emi
>
> On Tue, Sep 26, 2017 at 9:14 PM, Matthias Bläsing <
> mblaesing@doppel-helix.eu
> > wrote:
>
> > Hey,
> >
> > Am Dienstag, den 26.09.2017, 09:17 +0200 schrieb Geertjan Wielenga:
> > > [Discuss-Request: Focus on getting a release out or adding functions]
> >
> > if I'm not mistaken, the netbeans 9 feature freeze had already happened
> > when the migration to apache began. I would focus on bugfixing and
> > blocking new features.
> >
> > With the apache migration process there is enough development needed,
> > just to get the codebase releaseable. Libraries need to
> > removed/replaced, if the are incompatibe with the apache project
> > (SwingX is LGPL and so can't be distributed with apache netbeans) or
> > installers to get these libraries at runtime need to be implemented.
> >
> > While I agree, that adding new features would pull more potential
> > contributers, I would consider a stable base more important, to get
> > going from there. Java 9 is out and the excitement is already there and
> > people ask for netbeans 9, so I would prioritize that.
> >
> > My 2 cent
> >
> > Matthias
> >
> >
> >
>
Re: Allow code contributions or focus on release only?
Posted by Jan Lahoda <la...@gmail.com>.
Hi Emilian,
I appreciate your work on the cleanup.
I guess (virtually) everyone would like to work on new features (like in my
case (Java) Local Variable Type Inference support,
https://cwiki.apache.org/confluence/display/NETBEANS/JDK+Modules+Support+in+NetBeans+Module+System
and others).
But I suspect the first few releases will be very difficult, so my
suggestion would be to use master and code review bandwidth for the cleanup
and the first couple of (Platform and Java IDE) releases for now, and use
branches for features.
Jan
On Wed, Sep 27, 2017 at 9:27 AM, Emilian Bold <em...@gmail.com>
wrote:
> We should also allow some new features and improvements. We cannot have
> NetBeans under Apache for 1 year and basically have no Apache-contributed
> feature to show for, only IP cleanup and stuff like that.
>
> There's a whole lot of contributors and committers: does everybody want to
> do only this? Because I don't!
>
> BTW, how many are being involved in the new Apache build system or IP
> clearance, etc.? I don't see people jumping in on this rather boring job.
>
> So, I *am* doing IP cleanup, but I would most certainly want to commit new
> features and bugfixes! I found and fixed a few bugs just these weeks while
> working on yameter.com
>
> I don't remember agreeing on a feature freeze within Apache, we just got
> the codebase donated.
>
> The community should be able to walk and chew bubble gum at the same time.
> If some people are focusing on the build system I don't see why other
> people can't focus on something else as long as they don't break something
> or get in the way?
>
> The real question is: are we really distributing the load *and trust* among
> committers or not? Because it seems to me everybody is very willing to
> heavily restrict what we should be allowed to do.
>
>
>
> --emi
>
> On Tue, Sep 26, 2017 at 9:14 PM, Matthias Bläsing <
> mblaesing@doppel-helix.eu
> > wrote:
>
> > Hey,
> >
> > Am Dienstag, den 26.09.2017, 09:17 +0200 schrieb Geertjan Wielenga:
> > > [Discuss-Request: Focus on getting a release out or adding functions]
> >
> > if I'm not mistaken, the netbeans 9 feature freeze had already happened
> > when the migration to apache began. I would focus on bugfixing and
> > blocking new features.
> >
> > With the apache migration process there is enough development needed,
> > just to get the codebase releaseable. Libraries need to
> > removed/replaced, if the are incompatibe with the apache project
> > (SwingX is LGPL and so can't be distributed with apache netbeans) or
> > installers to get these libraries at runtime need to be implemented.
> >
> > While I agree, that adding new features would pull more potential
> > contributers, I would consider a stable base more important, to get
> > going from there. Java 9 is out and the excitement is already there and
> > people ask for netbeans 9, so I would prioritize that.
> >
> > My 2 cent
> >
> > Matthias
> >
> >
> >
>
Re: Allow code contributions or focus on release only?
Posted by Emilian Bold <em...@gmail.com>.
We should also allow some new features and improvements. We cannot have
NetBeans under Apache for 1 year and basically have no Apache-contributed
feature to show for, only IP cleanup and stuff like that.
There's a whole lot of contributors and committers: does everybody want to
do only this? Because I don't!
BTW, how many are being involved in the new Apache build system or IP
clearance, etc.? I don't see people jumping in on this rather boring job.
So, I *am* doing IP cleanup, but I would most certainly want to commit new
features and bugfixes! I found and fixed a few bugs just these weeks while
working on yameter.com
I don't remember agreeing on a feature freeze within Apache, we just got
the codebase donated.
The community should be able to walk and chew bubble gum at the same time.
If some people are focusing on the build system I don't see why other
people can't focus on something else as long as they don't break something
or get in the way?
The real question is: are we really distributing the load *and trust* among
committers or not? Because it seems to me everybody is very willing to
heavily restrict what we should be allowed to do.
--emi
On Tue, Sep 26, 2017 at 9:14 PM, Matthias Bläsing <mblaesing@doppel-helix.eu
> wrote:
> Hey,
>
> Am Dienstag, den 26.09.2017, 09:17 +0200 schrieb Geertjan Wielenga:
> > [Discuss-Request: Focus on getting a release out or adding functions]
>
> if I'm not mistaken, the netbeans 9 feature freeze had already happened
> when the migration to apache began. I would focus on bugfixing and
> blocking new features.
>
> With the apache migration process there is enough development needed,
> just to get the codebase releaseable. Libraries need to
> removed/replaced, if the are incompatibe with the apache project
> (SwingX is LGPL and so can't be distributed with apache netbeans) or
> installers to get these libraries at runtime need to be implemented.
>
> While I agree, that adding new features would pull more potential
> contributers, I would consider a stable base more important, to get
> going from there. Java 9 is out and the excitement is already there and
> people ask for netbeans 9, so I would prioritize that.
>
> My 2 cent
>
> Matthias
>
>
>
Re: Allow code contributions or focus on release only?
Posted by Neil C Smith <ne...@googlemail.com>.
Hi,
On Tue, Sep 26, 2017 at 7:15 PM Matthias Bläsing <mb...@doppel-helix.eu>
wrote:
> if I'm not mistaken, the netbeans 9 feature freeze had already happened
> when the migration to apache began. I would focus on bugfixing and
> blocking new features.
>
> With the apache migration process there is enough development needed,
> just to get the codebase releaseable.
>
Mainly just a +1 to this (+10 if I could!)
There may be a wider discussion to be had once NetBeans 9 is out of the
door about how quickly releases happen? With the changes to the Java
release schedule on the horizon, maybe smaller more often releases of
NetBeans are the way to go (which is also a way of saying those new feature
PRs are still welcome, and might get in soonish, just not right now)?
Best wishes,
Neil
--
Neil C Smith
Artist & Technologist
www.neilcsmith.net
Praxis LIVE - hybrid visual IDE for creative coding - www.praxislive.org
Re: Allow code contributions or focus on release only?
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
Hey,
Am Dienstag, den 26.09.2017, 09:17 +0200 schrieb Geertjan Wielenga:
> [Discuss-Request: Focus on getting a release out or adding functions]
if I'm not mistaken, the netbeans 9 feature freeze had already happened
when the migration to apache began. I would focus on bugfixing and
blocking new features.
With the apache migration process there is enough development needed,
just to get the codebase releaseable. Libraries need to
removed/replaced, if the are incompatibe with the apache project
(SwingX is LGPL and so can't be distributed with apache netbeans) or
installers to get these libraries at runtime need to be implemented.
While I agree, that adding new features would pull more potential
contributers, I would consider a stable base more important, to get
going from there. Java 9 is out and the excitement is already there and
people ask for netbeans 9, so I would prioritize that.
My 2 cent
Matthias