Skip to content

Clarify stabilization dates process for more predictability #12232

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
Mab879 merged 3 commits into from
Jul 30, 2024
Merged

Clarify stabilization dates process for more predictability #12232

Mab879 merged 3 commits into from
Jul 30, 2024

Conversation

@marcusburghardt
Copy link
Member

@marcusburghardt marcusburghardt commented Jul 29, 2024

Description:

The 10_stabilization_phase.md file is also referenced in release_process.md documentation.

Rationale:

Document agreement on a process to define the start of stabilization phase and consequently the releases.
This brings more predictability for the project releases.

Review Hints:

Just documentation.

@marcusburghardt
Clarify stabilization dates process for more predictability
c4be064 
The 10_stabilization_phase.md file is also referenced in
release_process.md documentation.

Signed-off-by: Marcus Burghardt <maburgha@redhat.com>
@marcusburghardt marcusburghardt added the Documentation Update in project documentation. label Jul 29, 2024
@marcusburghardt marcusburghardt added this to the 0.1.74 milestone Jul 29, 2024
@github-actions
Copy link

github-actions bot commented Jul 29, 2024

Start a new ephemeral environment with changes proposed in this pull request:

Fedora Environment
Open in Gitpod

Oracle Linux 8 Environment
Open in Gitpod

@Mab879 Mab879 self-assigned this Jul 29, 2024
Mab879
Mab879 approved these changes Jul 29, 2024
View reviewed changes
Copy link
Member

@Mab879 Mab879 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Mab879
Mab879 requested changes Jul 29, 2024
View reviewed changes
@marcusburghardt @Mab879
Update docs/manual/developer/10_stabilization_phase.md
7090745 
Co-authored-by: Matthew Burket <m@tthewburket.com>
@marcusburghardt marcusburghardt requested a review from Mab879 July 29, 2024 14:24
@Mab879
Copy link
Member

Mab879 commented Jul 29, 2024

/test 4.13-images

@github-actions
Copy link

github-actions bot commented Jul 29, 2024 •
edited
Loading

🤖 A k8s content image for this PR is available at:
ghcr.io/complianceascode/k8scontent:12232
This image was built from commit: 3faef3a

Click here to see how to deploy it

If you alread have Compliance Operator deployed:
utils/build_ds_container.py -i ghcr.io/complianceascode/k8scontent:12232

Otherwise deploy the content and operator together by checking out ComplianceAsCode/compliance-operator and:
CONTENT_IMAGE=ghcr.io/complianceascode/k8scontent:12232 make deploy-local

@jan-cerny
Copy link
Collaborator

jan-cerny commented Jul 29, 2024

Can you update the Duration section as well? It still talks about 2 month cadence but we have switched to quarterly releases.

@Mab879 Mab879 modified the milestones: 0.1.74, 0.1.75 Jul 29, 2024
@marcusburghardt
Copy link
Member Author

marcusburghardt commented Jul 30, 2024

Can you update the Duration section as well? It still talks about 2 month cadence but we have switched to quarterly releases.

Sure. I thought this part was already updated in the past. Let me check.

@marcusburghardt
Review and update the duration section
3faef3a 
Signed-off-by: Marcus Burghardt <maburgha@redhat.com>
@marcusburghardt
Copy link
Member Author

marcusburghardt commented Jul 30, 2024

Can you update the Duration section as well? It still talks about 2 month cadence but we have switched to quarterly releases.

Sure. I thought this part was already updated in the past. Let me check.

Done.

@qlty-cloud-legacy
Copy link

qlty-cloud-legacy bot commented Jul 30, 2024

Code Climate has analyzed commit 3faef3a and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 59.4% (0.0% change).

View more on Code Climate.

@jan-cerny
Copy link
Collaborator

jan-cerny commented Jul 30, 2024

Thanks!

@marcusburghardt marcusburghardt mentioned this pull request Jul 30, 2024
Merged
@Mab879 Mab879 merged commit 6818398 into ComplianceAsCode:master Jul 30, 2024
@marcusburghardt marcusburghardt deleted the stabilization_date branch July 30, 2024 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Mab879 Mab879 Mab879 approved these changes

Assignees

@Mab879 Mab879

Labels

Documentation Update in project documentation.

Projects

None yet

Milestone

0.1.75

Development

Successfully merging this pull request may close these issues.

3 participants

@marcusburghardt @Mab879 @jan-cerny