Re: [jdt-dev] Buffer overflow

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

> Maybe
JDT can ask the webmaster to only ping one or two bugs per day? Would that
be manageable?

That should be
manageable. Stephan?

Plus no auto-closing.

Dani



From:
       Lars
Vogel <lars.vogel@xxxxxxxxxxx>
To:
       "Eclipse
JDT general developers list." <jdt-dev@xxxxxxxxxxx>
Date:
       15.05.2020
09:50
Subject:
       [EXTERNAL]
Re: [jdt-dev] Buffer overflow
Sent
by:        jdt-dev-bounces@xxxxxxxxxxx

---

Maybe JDT can ask the webmaster to
only ping one or two bugs per day?
Would that be manageable?

I'm not sure that the current number is for JDT but I think it is
either 5 or 8 bugs per day.

On Fri, May 15, 2020 at 9:40 AM Daniel Megert <daniel_megert@xxxxxxxxxx>
wrote:
>
> > For old bugs with no activity, only notifying the author is not
right in my view as the action could be pending on the committers' side
as well.
> Good point.
>
> > I am seeing a flood of notifications for auto-closing but I don't
remember it being so bad earlier. I am not sure if changing the frequency
or criteria for such updates will help here.
> There can be several reasons. For example, if there was lots a of
activity in the time frame we get more notifications. It's also a tradeoff
between getting lots of notifications in one day or less spread over days.
>
> The majority seems to vote for
> - stop auto-closing
> - add [stale] to the subject, so that everyone who wants can filter
the notifications
>
> Dani
>
>
>
> From:        "Noopur Gupta" <noopur_gupta@xxxxxxxxxx>
> To:        jdt-dev@xxxxxxxxxxx
> Cc:        jdt-dev@xxxxxxxxxxx
> Date:        14.05.2020 19:13
> Subject:        [EXTERNAL] Re: [jdt-dev] Buffer
overflow
> Sent by:        jdt-dev-bounces@xxxxxxxxxxx
> ________________________________
>
>
>
> +1 to stop auto-closing the bugs.
>
> For old bugs with no activity, only notifying the author is not right
in my view as the action could be pending on the committers' side as well.
>
> If a stale comment is added on the bug report, then anyone who is
still interested in the bug can respond to it including others in the cc
list.
>
> I am seeing a flood of notifications for auto-closing but I don't
remember it being so bad earlier. I am not sure if changing the frequency
or criteria for such updates will help here.
>
> Another option to not touch or notify anyone about the stale bugs
is also fine.
>
> Regards,
> Noopur
>
> PS: Some discussion threads from Twitter on this:
> https://twitter.com/lukaseder/status/1241023010674479106
> https://twitter.com/odrotbohm/status/1237104742670766088
>
> ----- Original message -----
> From: "Daniel Megert" <daniel_megert@xxxxxxxxxx>
> Sent by: jdt-dev-bounces@xxxxxxxxxxx
> To: "Eclipse JDT general developers list." <jdt-dev@xxxxxxxxxxx>
> Cc:
> Subject: [EXTERNAL] Re: [jdt-dev] Buffer overflow
> Date: Thu, May 14, 2020 10:04 PM
>
> That would be acceptable as well.
>
> Stephan, can you open a bug report and share it here? You can mention
the idea I raised and also the one from Mickael.
>
> Dani
>
>
>
> From:        Mickael Istria <mistria@xxxxxxxxxx>
> To:        "Eclipse JDT general developers
list." <jdt-dev@xxxxxxxxxxx>
> Date:        14.05.2020 18:23
> Subject:        [EXTERNAL] Re: [jdt-dev] Buffer
overflow
> Sent by:        jdt-dev-bounces@xxxxxxxxxxx
> ________________________________
>
>
>
>
>
> On Thu, May 14, 2020 at 6:13 PM Daniel Megert <daniel_megert@xxxxxxxxxx>
wrote:
> I am also not a fan of auto-closing but I like the idea to ping the
author to verify whether the bug is still relevant. I'm not sure whether
the webmaster can do this, but maybe we could add a comment, mark it stale
(not in subject) and only send a note to the author.
>
> I imagine the same bot that does add a Bugzilla comment or change
bug status could be tweaked to directly send a mail to the author to ask
them for verification with comment or closing action, without directly
touching the bug (then avoiding notifications).
> What do you think?_______________________________________________
> jdt-dev mailing list
> jdt-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
>
>
>
> _______________________________________________
> jdt-dev mailing list
> jdt-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
>
> _______________________________________________
> jdt-dev mailing list
> jdt-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
>
>
>
> _______________________________________________
> jdt-dev mailing list
> jdt-dev@xxxxxxxxxxx
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev



-- 
Eclipse Platform project co-lead
CEO vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev