Re: [jdt-dev] ] Re: Bug Creation, Description and more...JDT.Core
If this is a frequent issue as well, it can also be automated similarly.
I agree a process is important, but the process implementation should care about contributors, not the other way round. Concretely that means the process implementation needs to plug as hints into vanilla contributor workflow (eg IDE, build, reviews...), instead of contributors being expected to know the process perfectly beforehand.
On Monday, March 22, 2021, Sarika Sinha <sarika.sinha@xxxxxxxxxx
> 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,
> ----- Original message -----
> From: Mickael Istria <mistria@xxxxxxxxxx
> Sent by: "jdt-dev" <jdt-dev-bounces@xxxxxxxxxxx
> To: "Eclipse JDT general developers list." <jdt-dev@xxxxxxxxxxx
> 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
> To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev