Re: [openssl-project] Late thoughts on the 1.1.1 release - are we fooling ourselves?
On 17/08/18 17:44, Benjamin Kaduk wrote: > On Fri, Aug 17, 2018 at 06:39:54PM +0200, Richard Levitte wrote: >> In message <20180817162909.ga10...@roeckx.be> on Fri, 17 Aug 2018 18:29:09 >> +0200, Kurt Roeckx said: >> >> kurt> On Fri, Aug 17, 2018 at 01:55:13PM +0200, Richard Levitte wrote: >> kurt> > Personally, I see this as a showstopper re a release on Tuesday >> kurt> >> kurt> You mean a beta release? >> >> ... >> >> D'oh. For some reason, I got mixed up and imagined a live release on >> Tuesday. >> >> So ok, not a showstopper per se, even though I would have *liked* to >> see as much of the applicable issues fixed and PRs (and that includes >> those I'm talking about) applied as possible. >> >> However, I think we need to go over the "Assessed" milestone stuff and >> make an actual assessment on them (i.e. labeling them correctly). The >> final release will probably not be very far away, and I'd hate to have >> to call showstopper again by then. > > I agree. And, if we make a bunch of (bugfix) changes between a beta > release and the scheduled final release, it may be more appropriate to do > another beta than to do a final release with "many" (vaguely defined) > changes since the last beta. I don't really see why an issue that is currently in 1.1.0 should prevent us from issuing 1.1.1 with the same issue. 1.1.0 has been out for sometime now. Any truly serious issues should have been already fixed. That's not to say we should just ignore 1.1.0 issues - of course we should try and fix them. It's just that I don't see a dependency on fixing those issues for releasing 1.1.1. That at least was the thinking that went into the reclassification of many issues to "Assessed". Matt > > -Ben > >> See this thread as an early warning ;-) > ___ > openssl-project mailing list > openssl-project@openssl.org > https://mta.openssl.org/mailman/listinfo/openssl-project > ___ openssl-project mailing list openssl-project@openssl.org https://mta.openssl.org/mailman/listinfo/openssl-project
Re: [openssl-project] Late thoughts on the 1.1.1 release - are we fooling ourselves?
> I believe that we need to go through those issues and PRs and make an > actual assessment, i.e. label the appropriately, and for anything > that's a bug in current 1.1.1 code (*), they need to be fixed before > the release. If it's something which can be postponed until after the release, should it be labelled 'after 1.1.1.' or moved to the 'Post 1.1.1' milestone or both? I have to admit that I still don't quite understand the different semantics of the label vs. the milestone. Matthias ___ openssl-project mailing list openssl-project@openssl.org https://mta.openssl.org/mailman/listinfo/openssl-project
Re: [openssl-project] Late thoughts on the 1.1.1 release - are we fooling ourselves?
On Fri, Aug 17, 2018 at 06:39:54PM +0200, Richard Levitte wrote: > In message <20180817162909.ga10...@roeckx.be> on Fri, 17 Aug 2018 18:29:09 > +0200, Kurt Roeckx said: > > kurt> On Fri, Aug 17, 2018 at 01:55:13PM +0200, Richard Levitte wrote: > kurt> > Personally, I see this as a showstopper re a release on Tuesday > kurt> > kurt> You mean a beta release? > > ... > > D'oh. For some reason, I got mixed up and imagined a live release on > Tuesday. > > So ok, not a showstopper per se, even though I would have *liked* to > see as much of the applicable issues fixed and PRs (and that includes > those I'm talking about) applied as possible. > > However, I think we need to go over the "Assessed" milestone stuff and > make an actual assessment on them (i.e. labeling them correctly). The > final release will probably not be very far away, and I'd hate to have > to call showstopper again by then. I agree. And, if we make a bunch of (bugfix) changes between a beta release and the scheduled final release, it may be more appropriate to do another beta than to do a final release with "many" (vaguely defined) changes since the last beta. -Ben > See this thread as an early warning ;-) ___ openssl-project mailing list openssl-project@openssl.org https://mta.openssl.org/mailman/listinfo/openssl-project
Re: [openssl-project] Late thoughts on the 1.1.1 release - are we fooling ourselves?
In message <20180817162909.ga10...@roeckx.be> on Fri, 17 Aug 2018 18:29:09 +0200, Kurt Roeckx said: kurt> On Fri, Aug 17, 2018 at 01:55:13PM +0200, Richard Levitte wrote: kurt> > Personally, I see this as a showstopper re a release on Tuesday kurt> kurt> You mean a beta release? ... D'oh. For some reason, I got mixed up and imagined a live release on Tuesday. So ok, not a showstopper per se, even though I would have *liked* to see as much of the applicable issues fixed and PRs (and that includes those I'm talking about) applied as possible. However, I think we need to go over the "Assessed" milestone stuff and make an actual assessment on them (i.e. labeling them correctly). The final release will probably not be very far away, and I'd hate to have to call showstopper again by then. See this thread as an early warning ;-) Cheers, Richard -- Richard Levitte levi...@openssl.org OpenSSL Project http://www.openssl.org/~levitte/ ___ openssl-project mailing list openssl-project@openssl.org https://mta.openssl.org/mailman/listinfo/openssl-project
Re: [openssl-project] Late thoughts on the 1.1.1 release - are we fooling ourselves?
On Fri, Aug 17, 2018 at 01:55:13PM +0200, Richard Levitte wrote: > Personally, I see this as a showstopper re a release on Tuesday You mean a beta release? Kurt ___ openssl-project mailing list openssl-project@openssl.org https://mta.openssl.org/mailman/listinfo/openssl-project
[openssl-project] Late thoughts on the 1.1.1 release - are we fooling ourselves?
At first sight, if you search through github issues and PRs by filtering on the "1.1.1" milestone or the "1,1,1" label, it looks like a fairly small amount of work left. However, there's been a move done that I think has lead us astray; any issue or PR that had the milestone "1.1.1" and were determined to be applicable to 1.1.0 as well (i.e. not being a 1.1.1 only milestone, and I agree with that assessment) were changed to the milestone "Assessed" *with no further labeling*. Unfortunately, judging from activity, it seems the "Assessed" milestone has in large part become "the 'ignore for now'" bin... I believe that we need to go through those issues and PRs and make an actual assessment, i.e. label the appropriately, and for anything that's a bug in current 1.1.1 code (*), they need to be fixed before the release. At this moment, I count 132 issues and PRs in the "Assessed" milestone with no further labeling. Personally, I see this as a showstopper re a release on Tuesday, but I think it's on all of us to come to an agreement, that is unless we actually do label and fix everything that needs fixing 'til Monday evening (Euro time)... Cheers, Richard (*) I'm sure some of the issues and PRs in this milestone are 1.1.0 only or 1.0.2 only. They can safely be ignored for the moment, but still need to be labeled as such. -- Richard Levitte levi...@openssl.org OpenSSL Project http://www.openssl.org/~levitte/ ___ openssl-project mailing list openssl-project@openssl.org https://mta.openssl.org/mailman/listinfo/openssl-project
