On Wed, May 12, 2021 at 9:28 PM Loïc Dachary <loic@xxxxxxxxxxx> wrote: > > Hey, > > On 12/05/2021 21:18, Ilya Dryomov wrote: > > Hello, > > > > Highlights from this week: > > > > - release process improvements and coordination > > > > - currently ad-hoc email threads and #ceph-backports IRC channel > > - works well for David, but we did have a couple of instances of > > false "good to go" where some fixes intended for release were > > not in yet > > - want to give a heads up that the release is happening sooner > > - Yuri will email dev@xxxxxxx a week before locking the branch and > > starting validation > > - the team will keep track of upcoming releases in the CLT pad [1] > > - urgent release-related queries or concerns should go to clt@xxxxxxx > > > > - issues with generating release emails and blog posts > > - cephadm backports are done in batches, individual PRs are not > > listed > > - generated html requires manual edits > > - should be resolved with moving off WordPress > > > > - being able to release from a hotfix branch to avoid branch juggling > > - remains on David's list, Loic is interested too > > I confirm being interested. Would it be possible to get access to Jenkins ? With the goal to experiment with a copy of > > https://jenkins.ceph.com/job/ceph-build/ > > and verify that changes to > > https://github.com/ceph/ceph-build/tree/master/ceph-build > > to use a designated branch instead of the default actually works as intended? Obviously need to be careful to not disrupt PR builds but since release builds are separate it should be doable (after commenting out some steps perhaps). Adding David. Thanks, Ilya _______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
