I think things are moving along pretty swimmingly, but I wanted to
re-send the reminder about the timing on starting to create the branch
and tag for 0.6.0.
<snip>
I'd like to propose that anything that needs review should be on
the
list by Wed, Nov 9 @ 5 PM EST. Then we cut a tag and a branch at a
pre-defined time on Thursday Nov 10, say 3PM EST and anything that
hasn't made it to master will need to explicitly cherry-picked into the
branch for inclusion in the release. Any blocker bugs would be
cherry-picked, but other patches can be discussed on an as-needed basis
on list.
The time after the branch is created will give us some amount of time to
start digging into urgent bug fixes, do dry runs of the demo to, and to
prepare more thoroughly for planning the next sprint. Also a fine time
for 'out of band' activities that we tend to forget about like updated
the Aeolus site.
If there are things that we know aren't get completely reviewed & acked
by 3PM EST please feel free to raise it so we have a candidate list for
things we might want to cherry pick into to the maintenance branch.
Thanks in advance,
Mike