2024-11-08T05:27:38.577Z | <Kyle Bader> I usually always have a tab open to src/common/options, it has all the things |
2024-11-08T14:29:02.531Z | <Frédéric Nass> Hi everyone. If I want to see if a PR made it to a point release like v17.2.7, I just have to look at the release note. But what if I want to know if a particular PR will make it to the next minor release? Where reliable source should I look at? Any of those : <https://tracker.ceph.com/versions/679>, <https://github.com/ceph/ceph/milestone/15> ? |
2024-11-08T14:29:29.428Z | <Frédéric Nass> Hi everyone. If I want to see if a PR made it to a point release like v17.2.7, I just have to look at the release note. But what if I want to know if a particular PR will make it to the next minor release? What reliable source should I look at? Any of those : <https://tracker.ceph.com/versions/679>, <https://github.com/ceph/ceph/milestone/15> ? |
2024-11-08T14:31:31.638Z | <Casey Bodley> which pr? the pr should have an associated tracker issue, and that tracker should have associated backport trackers |
2024-11-08T14:32:32.284Z | <Frédéric Nass> Hi Casey, thank you for your time. This one for example: <https://github.com/ceph/ceph/pull/56222> |
2024-11-08T14:32:52.152Z | <Frédéric Nass> And this one: <https://github.com/ceph/ceph/pull/55534> |
2024-11-08T14:35:03.162Z | <Frédéric Nass> tracker for the later one has quincy backport <https://tracker.ceph.com/issues/64645> associated to it. Is the 'Resolved' status enough to consider that it will be part of next release which is v17.2.8? |
2024-11-08T14:36:09.601Z | <Casey Bodley> these both merged to the 'quincy' branch early enough to be part of 17.2.8, yeah |
2024-11-08T14:36:52.956Z | <Casey Bodley> i set target version=17.2.8 on <https://tracker.ceph.com/issues/64645> |
2024-11-08T14:37:15.349Z | <Frédéric Nass> Ok, thank you Casey. It just sounded weird that the later was merged 8 months ago and was not part of 17.2.7. |
2024-11-08T14:37:39.944Z | <Casey Bodley> i think it's been over a year since 17.2.7 |
2024-11-08T14:38:20.565Z | <Frédéric Nass> Oh I see. Hum.. Didn't expect that. |
2024-11-08T14:38:30.130Z | <Casey Bodley> yeah, not great |
2024-11-08T14:38:50.937Z | <Frédéric Nass> So when it's merged in Quincy branch, any new tag/release will embed the fix, right? |
2024-11-08T14:40:37.962Z | <Casey Bodley> generally yes. at some point during the release process, we fork the 'quincy' branch to a 'quincy-release' branch and test/release the latter. so anything that merges before that makes it in |
2024-11-08T14:41:37.675Z | <Frédéric Nass> I get it, I saw this quincy-release branch before. Thank you for your time and your help. 👍 |