Re: [jdt-dev] [eclipse-dev] Automate check to warn about freeze on Gerri

[Andrey Loskutov <loskutov@xxxxxx>]

Hmm, I forgot about "quiet" period just before M1 / M3.

The job should be probably also enabled at this time too.
 

Kind regards,
Andrey Loskutov

Спасение утопающих - дело рук самих утопающих

https://www.eclipse.org/user/aloskutov

 

 

Gesendet: Dienstag, 15. Dezember 2020 um 21:03 Uhr
Von: "Mickael Istria" <mistria@xxxxxxxxxx>
An: "Eclipse JDT general developers list." <jdt-dev@xxxxxxxxxxx>
Cc: "General development mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>
Betreff: Re: [eclipse-dev] [jdt-dev] Automate check to warn about freeze on Gerrit

Do I get it right that we only care about code freeze post-M3 now? The convention so far, built from the calendar, is that code is frozen every week before the milestone and the job is implemented to look at "stabilization" in the calendar. I don't mind getting rid of -1 and code freeze on milestones personally, nor do I mind getting rid of milestone stabilization week or of milestones in general; but in any case, we need to clarify when the job wants to vote -1 here, as it seems like there are different possible understandings.

_______________________________________________ eclipse-dev mailing list eclipse-dev@xxxxxxxxxxx To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-dev