I have now also reviewed the PRs. We currently have 144 PRs open: PRs against 1.0.2: 6 PRs against 1.1.0: 7 PRs against 1.1.1: 55 PRs against 1.2.0: 9 PRs against Post 1.1.1: 63 PRs against Other: 2
I was quite strict about allocating PRs to a milestone. This might mean that some of those decisions are controversial. Basically if a PR was about adding a feature, and it wasn't directly TLSv1.3 related (which is the stated primary objective for the release) then I put it against the Post 1.1.1 milestone. This does *not* mean that I think that a PR flagged as "Post 1.1.1" shouldn't go into 1.1.1. It just means that it is not relevant as far as the release criteria go - if it makes it into the release then great; if it doesn't - well we're not going to hold up the release schedule for it. If there are individual cases where you think a PR absolutely *MUST* go into 1.1.1 for whatever reason (to the point that we should hold up the release schedule for it) then we can argue that out on a case-by-case basis and amend the milestones accordingly. Alternatively just make sure you get it reviewed and committed before feature freeze. Matt On 23/01/18 17:49, Matt Caswell wrote: > I completed my first pass review of all issues. I still need to look at > PRs. I have put all PRs against a milestone using the following criteria: > > If it only applies to 1.0.2 or below: 1.0.2 milestone > If it only applies to 1.1.0 or below: 1.1.0 milesone > If it's API/ABI breaking to fix: 1.2.0 milestone > If it's a feature request that we aren't already planning to do for > 1.1.1: Post 1.1.1 milestone > If it's something which is independent of a release (e.g. web issues, > policy/procedure etc): Other milestone > If it applies to master and doesn't fit into one of the categories > above: 1.1.1 milestone > > > Some stats: > > We now have 249 issues open. > Since I started this exercise we have closed 134 issues. > Issues against 1.0.2: 17 > Issues against 1.1.0: 3 > Issues against 1.1.1: 141 > Issues against 1.2.0: 15 > Issues against Post 1.1.1: 58 > Issues against Other: 15 > > > Matt > _______________________________________________ > openssl-project mailing list > [email protected] > https://mta.openssl.org/mailman/listinfo/openssl-project > _______________________________________________ openssl-project mailing list [email protected] https://mta.openssl.org/mailman/listinfo/openssl-project
