docs: Add release timeline ADR #25
Conversation
arbrandes
added
priority:high
documentation
arbrandes
force-pushed
the
arbrandes/adr-release-timeline
branch
3 times, most recently
from
7601c3a
to
cae21bc
Compare
|
fwiw, this seems reasonable to me and I've already internalised this timeline and it's what I'm driving towards. I think we can always revise it during/after Lilac depending on how things go. |
| +---------------------------+------------------------------------------------+ | ||
| | Time prior to release day | Event | | ||
| +===========================+================================================+ | ||
| | 8 weeks | ``open-release/zebrawood.master`` branched off | |
There was a problem hiding this comment.
Raised during the BTR Meetup: This timeline means has the branch off release.master is due on the same day that the 3rd tag for the previous release is created. This can create a bit of confusion in terms of deadline and tasks due. Is it worth considering having it set to 7 weeks instead of 8?
There was a problem hiding this comment.
What we ended up doing is to stagger the tagging process across a couple of days. It seems to have worked, so I guess we can keep this schedule.
In any case, as discussed in the previous meeting, I removed the "RCs" from the schedule, and replaced them with milestones.
arbrandes
force-pushed
the
arbrandes/adr-release-timeline
branch
from
cae21bc
to
93ffb0d
Compare
No description provided.