Add Core-Setup stages-based publish expected completion#3630
Merged
2 commits merged intoAug 9, 2019
Merged
Conversation
ghost
merged commit 
dleeapho
reviewed
Aug 9, 2019
dleeapho
left a comment
dleeapho
left a comment
There was a problem hiding this comment.
Correct per our planning discussions.
This pull request was closed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Expected completion date of 8/21 is based on the plan I sent out, with a few days of work being done. Note that 8/21 is later than the target date of 8/13.
The current plan is going with custom publishing steps, therefore no blockers. If #3607 is done very quickly and it seems like changing core-setup to use it will cause no delay, I will, but I'm not planning to wait for it to make progress.