New GitHub label for release blockers

[Dr. Matthias St. Pierre]

Nicola suggested and convinced me, that it would be better to have a dedicated
milestone for the 3.0.0 beta1 release instead of adding a new label.

So here it is, I already added all the tickets with the release blocker label and will
remove the label again.

https://github.com/openssl/openssl/milestone/17

Matthias



> -----Original Message-----
> From: Dr. Matthias St. Pierre
> Sent: Sunday, September 13, 2020 3:17 PM
> To: openssl-project at openssl.org
> Subject: New GitHub label for release blockers
> 
> Hi all,
> 
> taking up again the discussion from openssl-project where I suggested to (ab)use
> the 3.0.0 milestone for release blockers, (see link and citation at the end of the mail),
> I propose to add a new label for this purpose instead. In fact, I already created the label
> 
> 	[urgent: release blocker]   (see link below)
> 
> and will add the mentioned tickets within shortly. So you can take a look and tell
> me whether you like it or not. (If not, no problem. I'll just delete the label again.)
> 
> Matthias
> 
> 
> BTW: It took me all my force of will to resist the temptation of making a pun
>      by naming the label [urgent: beta blocker].
> 
> 
> References:
> ==========
> 
> [urgent: release blocker]:
> 	https://github.com/openssl/openssl/labels/urgent%3A%20release%20blocker
> 
> [openssl-project message]:
> 	https://mta.openssl.org/pipermail/openssl-project/2020-September/002191.html
> 
> 
> > > > For a more accurate and timely public overview over the current state of the blockers,
> > > > it might be helpful to manage them via the 3.0.0  milestone
> > > >
> > > > https://github.com/openssl/openssl/milestone/15
> > > >
> > > > Some of the tickets listed below were already associated to the milestone, the others
> > > > were added by me now.
> > >
> > > I think the 3.0.0 milestone is what we expect to be in the
> > > 3.0.0 release, not the beta release. That is bug fixes don't need
> > > to be in the beta release, but if it adds new functionallity it
> > > needs to be in the beta release.
> >
> > I was aware of this subtlety but I thought that we just could (ab-)use the milestone for
> > the beta1 release and reuse it later for the final release, instead of creating a new milestone.
> >
> > Practically all of the relevant PRs are associated to the [3.0 New Core + FIPS] GitHub Project
> > anyway, so it would be possible to remove the post-beta PRs from the milestone and restore
> > them later.  (In my mind, I see project managers running away screeming...)
> >
> > Matthias
> >
> >
> > [3.0 New Core + FIPS]:  https://github.com/openssl/openssl/projects/2