Matthias overcredits me: I just wanted to know his opinion about when we
should use labels and when milestones (and that is why I wrote to him
off-list, as a very confused and shy pupil asking a sensei for wisdom
pearls).
All the alleged convincing was self-inflicted :P
And now that my
I was not referring to this page in particular, but in general to the
various pages on github doc (and more in general among the first Google
results) about github labels and milestones and how to use them.
There seem to be, in the wild, different documented approaches, probably
even influenced
On 13/09/2020 15:16, Nicola Tuveri wrote:
> ... I still have very confused ideas regarding the "best" conventional
> usage of github features like labels, milestones and projects: I read
> the official documentation about them and I grasp the general ideas
> behind them, but too often the
Since we were able to collect some experiences working on the ‘3.0 New Core +
FIPS’ project, I think that’s a perfect subject
to be discussed on the face-to-face meeting. I will add it to the list of
proposed topics. As for the official documentation you
mentioned, are you talking about this
I added some issues mentioned in the 'Beta1 PR deadline' thread to the new
label.
Feel free to extend and modify the list as necessary.
That's a very nice summary, Matt.
when your time permits, could you please double-check whether all important
tickets
for beta1 were moved correctly from '3.0.0' to '3.0.0 beta1'?
Thanks,
Matthias
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:
> BTW: It took me all my force of will to resist the temptation of making a pun
> by naming the label [urgent: beta blocker].
Failed you have. Your training is not yet compete :)
Pauli
--
Dr Paul Dale | Distinguished Architect | Cryptographic Foundations
Phone +61 7 3031 7217
Oracle
Conversely, there were also pull requests associated with the '3.0.0' or '3.0.0
beta1' milestone,
without being associated to the '3.0 New Core + FIPS' project. This has been
fixed now.
> when your time permits, could you please double-check whether all important
> tickets
> for beta1 were moved correctly from '3.0.0' to '3.0.0 beta1'?
The '3.0 New Core + FIPS' project currently lists 21 open pull requests,
[is:open is:pr project:openssl/openssl/2]:
10 matches
Mail list logo
