Hey Ken, yes that's the plan. I'll reset pacific to master on the 15th
at 17:00 PT. Anything after that will go to master first, and important
bug fixes will be cherry-picked to pacific like a usual stable branch.
Josh
On 1/12/21 10:37 AM, Ken Dreyer wrote:
Hi Josh,
We have a "pacific" branch in GitHub today that is 7444 commits behind
master. Just to confirm, are you going to reset that branch to the tip
of master on Jan 15th?
I think it's a good idea to cherry-pick everything past that point.
- Ken
On Wed, Dec 16, 2020 at 4:29 PM Josh Durgin <jdurgin@xxxxxxxxxx> wrote:
Hey folks, we're getting towards the end of the pacific cycle.
The component leads discussed and decided this time we're going to do a
hard feature freeze on January 15th, 2021.
After that, we'll branch off pacific from master, and use the usual
backport process to merge bug fixes - first going to master,
then backporting to the pacific branch. Since this is the same
procedure as the rest of the development cycle, it should cause
less confusion.
This will let us focus on stabilizing pacific and improving the test
suites, and make sure only changes consciously targeted for pacific are
merged there. As usual, we're targeting the release for March, so we'll
have ~2 months of stabilization.
Josh
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
