Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jdt-dev] ] Re: Bug Creation, Description and more...JDT.Core

I like the idea Mickael suggested. If we can have a CI job checking the commits that would be great. 

Best regards,
Gayan

On Mon, 22 Mar 2021 at 18:53, Sarika Sinha <sarika.sinha@xxxxxxxxxx> wrote:
Also, in some cases I have observed that old Bug numbers ( which were closed couple of releases before) are used for new gerrits in JDT Debug.
We all have to be careful and follow the process.
 
Thanks & Regards,
Sarika
 
----- Original message -----
From: Mickael Istria <mistria@xxxxxxxxxx>
Sent by: "jdt-dev" <jdt-dev-bounces@xxxxxxxxxxx>
To: "Eclipse JDT general developers list." <jdt-dev@xxxxxxxxxxx>
Cc:
Subject: [EXTERNAL] Re: [jdt-dev] Bug Creation, Description and more...JDT.Core
Date: Mon, Mar 22, 2021 9:47 PM
 
> gerrit patches without bug number
 
If it's happening frequently, it's worth adding a CI job that checks for Gerrit patch and verifies (eg in a bash script) that the message contains the proper bug reference and vote -1 automatically if it's missing. It's good the JDT has some processes in place to enforce some traceability which is proven to be useful for JDT Core, but it would be even better if those process were somehow automated and enforced by infrastructure.
_______________________________________________
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

Back to the top