On Fri, 14 Jan 2022, 20:42 Eric Bresie, wrote:
> (2) it is different for a "Feature",
>
Yes, the forms are quite different.
Neil
> we will not have this.
> > I think it will be just fine to talk to the people and let them know
> enough that they shouldn't expect anything at all.
> >
> >
> > Cheers
> >
> > Chris
> >
> >> Gesendet: Freitag, 14. Januar 2022 um 12:19 U
anything at all.
Cheers
Chris
Gesendet: Freitag, 14. Januar 2022 um 12:19 Uhr
Von: "Neil C Smith"
An: dev@netbeans.apache.org
Betreff: Re: GitHub issues - initial templates and labels
On Wed, 12 Jan 2022 at 21:09, Benjamin Asbach wrote:
I'm a little bit curious how this "l
um 12:19 Uhr
> Von: "Neil C Smith"
> An: dev@netbeans.apache.org
> Betreff: Re: GitHub issues - initial templates and labels
>
> On Wed, 12 Jan 2022 at 21:09, Benjamin Asbach wrote:
> > I'm a little bit curious how this "latest Release" field is suppos
On Wed, 12 Jan 2022 at 21:09, Benjamin Asbach wrote:
> I'm a little bit curious how this "latest Release" field is supposed to
> work? Is this moved automatically when a new release was pumped out?
No, nothing is moved automatically. Bear in mind that the forms here
only structure the text that
I'm a little bit curious how this "latest Release" field is supposed to
work? Is this moved automatically when a new release was pumped out?
On 2022-01-12 13:04, Neil C Smith wrote:
On Mon, 10 Jan 2022 at 14:28, Neil C Smith
wrote:
Just a note that, if you haven't noticed already, GitHub Disc
On Mon, 10 Jan 2022 at 14:28, Neil C Smith wrote:
> Just a note that, if you haven't noticed already, GitHub Discussions
> is now enabled.
...
> As this required manual setup, I had this done in advance of merging
> the issues enabling PR to check linking is working correctly.
The rest of the ini
On Thu, 6 Jan 2022 at 16:41, Matthias Bläsing wrote:
> Maybe I'm missing something obvious, but IMHO the focus should be how
> to streamline fixes from drive-by contributors. For this we need a
> form, where people can document, that they agree to the donation
> without having an ICLA on file. Tha
On Thu, 6 Jan 2022 at 15:38, Neil C Smith wrote:
> I'll contact infra@ about enabling discussions - links to that will
> 404 at the moment.
Just a note that, if you haven't noticed already, GitHub Discussions
is now enabled. It seems to have been a surprise to some, even though
it was explicitly
On Sun, 9 Jan 2022, 15:34 Matthias Bläsing,
wrote:
> So people asking for an open tracker have to answer the question:
>
> - Who triages issues?
> - Who ensures bugfixes are tied to their issue reports?
> - Who ensures that issues are checked if they are gone in newer
> versions?
>
Every committ
thias Bläsing
> Gesendet: Donnerstag, 6. Januar 2022 17:41
> An: dev@netbeans.apache.org
> Betreff: Re: GitHub issues - initial templates and labels
>
> Hi,
>
> Am Donnerstag, dem 06.01.2022 um 10:04 -0600 schrieb Glenn Holmer:
> > On 1/6/22 09:38, Neil C Smith wrote:
>
than saying nothing, or saying „it works on my machine“ and leave them
alone. That is much more frustrating than a good explained comment.
Cheers
Chris
Von: Matthias Bläsing
Gesendet: Donnerstag, 6. Januar 2022 17:41
An: dev@netbeans.apache.org
Betreff: Re: GitHub issues - initial templates and
On Thu, 6 Jan 2022, 19:30 Eric Bresie, wrote:
> So would “critical” be used to address “show / release stopper” level
> issues ...
>
Yes, basically replacing how we (say we) treat blocker now.
>
> Is there a “default” for this?
>
No label (for priority, other labels are added by the form)
G
@netbeans.apache.org; Neil C Smith
*Subject:* Re: GitHub issues - initial templates and labels
On 06.01.22 16:38, Neil C Smith wrote:
> ## Priorities
>
> priority:critical
> priority:high
>
> I'm only thinking of adding those two for now. With critical reserved
> for &qu
On Thu, 6 Jan 2022 at 17:07, Neil C Smith wrote:
> > Maybe I'm missing something obvious, but IMHO the focus should be how
> > to streamline fixes from drive-by contributors. For this we need a
> > form, where people can document, that they agree to the donation
> > without having an ICLA on file.
On Thu, 6 Jan 2022 at 16:41, Matthias Bläsing wrote:
> Do we really want to encourage people to file issues?! My take on the
> current situation is, that there is no one really working on fixing
> issues, apart from the issues relevant to them (which is OK!).
Actually we're trying to discourage t
Hi,
Am Donnerstag, dem 06.01.2022 um 10:04 -0600 schrieb Glenn Holmer:
> On 1/6/22 09:38, Neil C Smith wrote:
> > Following the lazy consensus thread I've started work on porting
> > Airflow's issue forms for NetBeans, making changes where necessary.
> >
> > There is an in progress PR at https://
On 06.01.22 17:09, Neil C Smith wrote:
On Thu, 6 Jan 2022 at 15:52, Michael Bien wrote:
On 06.01.22 16:38, Neil C Smith wrote:
## Priorities
priority:critical
priority:high
I'm only thinking of adding those two for now. With critical reserved
for "must address in next release" issues / PRs.
On Thu, 6 Jan 2022 at 16:05, Glenn Holmer wrote:
>
> On 1/6/22 09:38, Neil C Smith wrote:
> > Following the lazy consensus thread I've started work on porting
> > Airflow's issue forms for NetBeans, making changes where necessary.
> >
> > There is an in progress PR at https://github.com/apache/net
On Thu, 6 Jan 2022 at 15:52, Michael Bien wrote:
>
> On 06.01.22 16:38, Neil C Smith wrote:
> > ## Priorities
> >
> > priority:critical
> > priority:high
> >
> > I'm only thinking of adding those two for now. With critical reserved
> > for "must address in next release" issues / PRs. Rather than
On 1/6/22 09:38, Neil C Smith wrote:
> Following the lazy consensus thread I've started work on porting
> Airflow's issue forms for NetBeans, making changes where necessary.
>
> There is an in progress PR at https://github.com/apache/netbeans/pull/3415
The bug report form is excellent. It looks w
On 06.01.22 16:38, Neil C Smith wrote:
## Priorities
priority:critical
priority:high
I'm only thinking of adding those two for now. With critical reserved
for "must address in next release" issues / PRs. Rather than low
priority, maybe we can add a contribution-welcome or similar?
I think th
Hi All,
Following the lazy consensus thread I've started work on porting
Airflow's issue forms for NetBeans, making changes where necessary.
There is an in progress PR at https://github.com/apache/netbeans/pull/3415
I've set up a temporary repository so these can be looked at
https://github.com/
23 matches
Mail list logo
