2024年4月9日(火) 8:06 Laura Flores <lflores(a)redhat.com>om>:
I've added them!
I have a question about the role of github milestones.
The two PRs in the v18.2.3 milestone are essential for debian package users
as I described before. Are these PRs release blocker for v18.2.3 release?
Or is the merging work done as best-effort?
https://github.com/ceph/ceph/pull/56541
I want to know this because of two reasons.
First, I'd like to upgrade my v17.2 cluster to v18.2. It's blocked for now
due to the above-mentioned two PRs. I don't want to suspend upgrading by
the release of v18.2.4.
Second, I'd like to plan the timing of my clusters as precise as possible.
To accomplish this, which PRs will be in the next stable release is the
essential information. Although I've read official documents, PRs, issues,
and slack channels to know the information for several years, I couldn't
find the strict role of milestones yet.
Of course, I read the following document.
https://github.com/ceph/ceph/blob/dbd161df82a5b6079484649873438185aa7e1b76/…
Once your backport PR is open and the Milestone
is set properly, the Stable
Releases and Backports team will take care of getting the PR reviewed and
tested. Once the PR is reviewed and tested, it will be merged.
However, these PRs are not reviewed yet and the milestone is not mentioned
in neither the release tracker issue nor the thread for the v18.2.3 release.
https://tracker.ceph.com/issues/65393
Best,
Satoru
> cc @Yuri Weinstein <yweinste(a)redhat.com
> On Mon, Apr 8, 2024 at 5:39 PM Satoru
Takeuchi <satoru.takeuchi(a)gmail.com
> wrote:
>> 2024年4月9日(火) 0:43 Laura Flores
<lflores(a)redhat.com>om>:
>
>>> Hi all,
>>
>>> Today we
discussed:
>>
>>>
2024/04/08
>>
>>> -
[Zac] CQ#4 is going out this week -
>>>
https://pad.ceph.com/p/ceph_quarterly_2024_04
>>
>>
>>> - Last chance to review!
>>
>>
>>> - [Zac] IcePic Initiative -
context-sensitive help - do we regard
>>> the docs as a part of the online help?
>>
>>
>>> -
https://pad.ceph.com/p/2024_04_08_cephadm_context_sensitive_help
>>
>>
>>> -
docs.ceph.com should be main
source of truth; can link to this or
>>> reference it generally as "see docs.ceph.com"
>>
>>
>>> - Squid RC status
>>
>>
>>> - Blockers tracked in:
https://pad.ceph.com/p/squid-upgrade-failures
>>
>>
>>> - rgw: topic changes merged to
main, but introduced some test
>>> failures. account changes blocked on topics
>>
>>
>>> - Non-blocker for RC0
>>
>>
>>> - centos 9 containerization
(status unknown?)
>>
>>
>>> - Non-blocker for RC0
>>
>>
>>> - Follow up with Dan /
Guillaume
>>
>>
>>> - RADOS has one outstanding
blocker awaiting QA
>>
>>
>>> - Failing to register new
account at Ceph tracker - error 404.
>>
>>
>>> - Likely related to Redmine
upgrade over the weekend
>>
>>
>>> - Pacific eol:
>>
>>
>>> - Action item: in
https://docs.ceph.com/en/latest/releases/, move to
>>> "archived"
>>
>>
>>> - 18.2.3
>>
>>
>>> - one or two PRs from cephfs
left
>>
>>
>>> - Milestone:
https://github.com/ceph/ceph/milestone/19
>>
>>
>> Could you add the following PRs to
18.2.3 milestone? Without these PRs,
>> debian package users
>> can't use metrics from ceph-exporter at all.
>
>> reef: debian: add ceph-exporter package
#56541
>>
https://github.com/ceph/ceph/pull/56541
>
>> reef: debian: add missing bcrypt to
ceph-mgr .requires to fix resulting
>> package dependencies #54662
>>
https://github.com/ceph/ceph/pull/54662
>
>> Thanks,
>> Satoru
>
>
>>
>>> Thanks,
>>> Laura
>>> --
>>
>>> Laura
Flores
>>
>>>
She/Her/Hers
>>
>>> Software
Engineer, Ceph Storage <https://ceph.io
>>
>>> Chicago,
IL
>>
>>>
lflores(a)ibm.com | lflores(a)redhat.com <lflores(a)redhat.com
>>> M: +17087388804
>>
>>
>>>
_______________________________________________
>>> Dev mailing list -- dev(a)ceph.io
>>> To unsubscribe send an email to dev-leave(a)ceph.io
>>
>
> --
> Laura Flores
> She/Her/Hers
> Software Engineer, Ceph Storage
<https://ceph.io
> Chicago, IL
> lflores(a)ibm.com | lflores(a)redhat.com
<lflores(a)redhat.com
> M: +17087388804