Ceph Leadership Team Meeting

[Ernesto Puerta <epuertat@xxxxxxxxxx>]

Hi Cephers,

These are the topics discussed in today's meeting:

• Change in the release process

• Patrick suggesting version bump PRs vs current commit push approach

• Commits are not signed

• Avoids freezing the branch during hotfixes

• Both for hotfixes and regular dot releases

• Needs further discussion

• https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow <-- more closely matches current model + proposed changes re: PRs, with the addition of a development branch
• https://www.atlassian.com/continuous-delivery/continuous-integration/trunk-based-development

• ceph-Jenkins account needs admin privs to ceph.git in order to push directly to branches

• doesn't apply to PR version bump

• publishing (Windows) binaries signed by cloudbase?

• Issues with Linux/Ceph Foundation

• RH might provide the signed binaries

• Probably don't publish binaries signed by Cloudbase b/c we wouldn't get telemetry data back from crashes etc.

• master-main rename

• rename completed
• there are still issues with some Jenkins jobs
  

• quincy blogs

• 17.2.1 readiness

• 3 PRs left

• release candidate by Jun 1st week

• 16.2.8 issue retrospective: https://docs.google.com/presentation/d/1hbwo_GW48O4nnM78US2ghVXglxZw5TRwmWUOy_oxam8/ 

• scale testing

• stricter backport policy

• lack of reviews in the backport

• mgr component is orphaned (RADOS, lack of experience in other teams)

• conflict solving was not properly documented

• mgr has become too critical (due to cephadm it is now key)

• don't merge with 1 approval

• reviewers on sensitive PRs/files should acknowledge they understand the code changes

• different standards across teams

• try out requiring reviews from CODEOWNERS on the pacific branch

Kind Regards,

Ernesto

_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx