How are bugs on the RC tracked?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

How are bugs on the RC tracked?

David Anthoff

The 0.4.0 milestone is closed, so apparently that is not where stuff that has to be fixed before a release is being tracked.

 

There is a label “backport pending 0.4”, what does that mean? Backport into any 0.4.x release, or are these the things that need to be fixed for 0.4.0? At least one of these issues with that label is a regression over 0.3, so I assume those are the things that still need to be fixed before a 0.4.0 release?

 

May I suggest to just use the 0.4.0 milestone to track anything that still needs to be done before a 0.4.0 release, and close it once the release is done. Seems much easier for everyone to understand.

 

Cheers,

David

 

--

David Anthoff

University of California, Berkeley

 

http://www.david-anthoff.com

 

Reply | Threaded
Open this post in threaded view
|

Re: How are bugs on the RC tracked?

Tony Kelman
The meaning of "backport pending 0.4" differs depending on which issue it's used for. For things that aren't yet merged or closed it means "we need to fix this on master, then once it's stable for a few days we'll backport it to release-0.4." Not all of those are release-critical but if they're ready and non-disruptive we may as well get them in. I've been doing a series of backport rollup PR's (#13107 is the current one) to keep release-0.4 up to date with anything non-feature from master, but I'm also being careful about building binaries off the branch ahead of time and testing against PackageEvaluator before merging backports.

The plan right now is to do one RC a week until there's nothing release-blocking. If nothing release-blocking comes up for a few days to a week after an RC we'll tag final. There was a build issue related to ccalltest that I've included in #13107 that I think is the only thing that I'd consider final-release-blocking at this moment. I could also use some help debugging #12907 which is a likely openblas bug (not release-blocking, but worrisome).


On Monday, September 14, 2015 at 10:35:33 AM UTC-7, David Anthoff wrote:

The 0.4.0 milestone is closed, so apparently that is not where stuff that has to be fixed before a release is being tracked.

 

There is a label “backport pending 0.4”, what does that mean? Backport into any 0.4.x release, or are these the things that need to be fixed for 0.4.0? At least one of these issues with that label is a regression over 0.3, so I assume those are the things that still need to be fixed before a 0.4.0 release?

 

May I suggest to just use the 0.4.0 milestone to track anything that still needs to be done before a 0.4.0 release, and close it once the release is done. Seems much easier for everyone to understand.

 

Cheers,

David

 

--

David Anthoff

University of California, Berkeley

 

<a href="http://www.david-anthoff.com" target="_blank" rel="nofollow" onmousedown="this.href=&#39;http://www.google.com/url?q\75http%3A%2F%2Fwww.david-anthoff.com\46sa\75D\46sntz\0751\46usg\75AFQjCNHPDijM7QgcCRbDWt_-VR5r_HnDGg&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\75http%3A%2F%2Fwww.david-anthoff.com\46sa\75D\46sntz\0751\46usg\75AFQjCNHPDijM7QgcCRbDWt_-VR5r_HnDGg&#39;;return true;">http://www.david-anthoff.com