# 20221027_FCOS-37-rebase-schedule

## Option 1a: bake OpenSSL fix in promoted testing
## Option 1a: Normal Testing Promotion (+fix); Delay; Normal Stable Promotion (+fix)

- ship PROMOTED testing with openssl fix
- promote previous testing (as usual, but with openssl fix) to stable and ship shortly after (24h?)

Pros:
- some bake time
- 0 extra release
Cons:
- fix delayed for users of `stable`
- OpenSSL fix for `stable` doesn't bake alongside the rest of its package set

## Option 1b: bake OpenSSL fix in unpromoted testing, promote testing later in the week
## Option 1b: OOB Testing; Delay; Normal Stable Promotion; Normal Testing Promotion

**Preferred option if we can afford bake time**

- ship UNPROMOTED testing with openssl fix (treat like an async release)
- wait 24h
- ship stable and testing as usual (stable takes testing with baked openssl, testing gets new content)

Pros:
- some bake time
- easy to explain
- baking exactly what we ship
Cons:
- fix delayed for users of `stable`
- 1 extra release (testing)

## Option 2a: OpenSSL fix directly to stable promoted from testing
## Option 2a: Normal Testing Promotion (+fix); Normal Stable Promotion (+fix)

- ship PROMOTED testing with openssl fix
- concurrently ship PROMOTED stable with openssl fix

TL;DR - normal promotions + SSL fix in each one

Pros:
- fix ships to users in all streams faster
- 0 extra release
Cons:
- minimal bake time
- potential for any breakage from testing->stable promotion interfering with OpenSSL update

## Option 2b: OpenSSL fix directly to existing stable, promote testing later
## Option 2b: OOB Stable; Normal Testing (+fix); Delay; Normal Stable

- ship PROMOTED testing with openssl fix
- concurrently ship current (UN-PROMOTED) stable with openssl fix
- later (24 or 48h?) ship stable promoted from _previous_ testing (i.e. the one we'd normally have promoted from) with openssl fix

Pros:
- fix ships to users in all streams faster
- dedicated `stable` release for just the OpenSSL fix
Cons:
- minimal bake time
- 1 extra release (stable)
- note: can't promote `stable` from `testing` `HEAD`

## Option 2c: Async release for both stable and testing, then regular release
## Option 2c: OOB Stable; OOB Testing; Delay; Normal Testing Promotion; Normal Stable Promotion

**Preferred option if we cannot afford bake time**

- ship UNPROMOTED testing and stable with openssl fix (treat like async releases)
- wait 24h
- ship stable and testing as usual (stable takes testing with openssl fix + new content, testing gets new content)

Pros:
- dedicated releases for just the OpenSSL fix
- gets fix to stable fast
- easy to explain
Cons:
- 2 extra releases (stable, testing)