releng/tickets

Update sop_two_week_atomic to include latest AutoCloud info #7099

Merged

jnsamyak merged 3 commits from sop into master

2026-06-08 03:12:18 +00:00

maxamillion commented

2017-10-17 22:23:32 +00:00

Contributor

In the past, AutoCloud was slated to be the authoritative place for
testing. However, this never actually panned out and there are now
some work arounds required at times. This pull request updates the
SOP to include documentation of those work arounds as well as
a description of current process and when work arounds are needed.

Signed-off-by: Adam Miller maxamillion@fedoraproject.org

In the past, AutoCloud was slated to be the authoritative place for testing. However, this never actually panned out and there are now some work arounds required at times. This pull request updates the SOP to include documentation of those work arounds as well as a description of current process and when work arounds are needed. Signed-off-by: Adam Miller <maxamillion@fedoraproject.org>

dustymabe commented

2017-10-18 13:16:05 +00:00

Member

such as???

such as???

dustymabe commented

2017-10-18 13:19:47 +00:00

Member

i'm not sure why we don't make the default behavior to be:

if user did not specify what to release then use latest good from autocloud
if user specified what to release then make sure it wasn't marked bad

We wouldn't have to "lie" to the script any longer.

i'm not sure why we don't make the default behavior to be: - if user did not specify what to release then use latest good from autocloud - if user specified what to release then make sure it wasn't marked bad We wouldn't have to "lie" to the script any longer.

maxamillion commented

2017-10-18 14:35:43 +00:00

Author

Contributor

Yeah, sorry ... when I originally wrote this section the example output followed that paragraph. I'll fix it up.

Yeah, sorry ... when I originally wrote this section the example output followed that paragraph. I'll fix it up.

maxamillion commented

2017-10-18 14:40:00 +00:00

Author

Contributor

Because the original goal of the Two-Week Atomic Release by specification was for there never to be a human element unless something went wrong. The goal was for the tests to be authoritative so that's how it was written as originally agreed upon. We could certainly alter it now to be in better shape, but this document is being updated including current "work arounds" simply to transition this stuff away from just me over to other members of RelEng since I'm in transition process to leave the Fedora Engineering Team. Basically, I wanted to document everything as it stands now for the benefit of Rob and Mohan.

Because the original goal of the Two-Week Atomic Release by specification was for there never to be a human element unless something went wrong. The goal was for the tests to be authoritative so that's how it was written as originally agreed upon. We could certainly alter it now to be in better shape, but this document is being updated including current "work arounds" simply to transition this stuff away from just me over to other members of RelEng since I'm in transition process to leave the Fedora Engineering Team. Basically, I wanted to document everything as it stands now for the benefit of Rob and Mohan.

maxamillion commented

2017-10-18 15:56:48 +00:00

Author

Contributor

1 new commit added

clarify about two-week-atomic example output

**1 new commit added** * clarify about two-week-atomic example output

dustymabe commented

2017-10-18 15:57:30 +00:00

Member

LGTM

LGTM

maxamillion commented

2017-10-19 16:28:41 +00:00

Author

Contributor

1 new commit added

add note about bad-composes that might need to be removed next two-week release

**1 new commit added** * add note about bad-composes that might need to be removed next two-week release

mohanboddu commented

2017-10-19 18:38:09 +00:00

Contributor

Pull-Request has been merged by mohanboddu

Pull-Request has been merged by mohanboddu

Sign in to join this conversation.

No reviewers

No labels

change-noreleng

Fixed with Explanation

Insufficient data

mini-initiative

waiting on external

No milestone

No project

No assignees

3 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

releng/tickets!7099

No description provided.