Update shipping_year when milestones are edited. #4397
Merged
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.
Once a feature owner fills in some shipping milestones, the feature's shipping_year should be calculated based on those milestones. This PR adds that calculation to the features_api.
In this PR:
fetch_chrome_release_info()
into fetchchannels.py to avoid a circular import._patch_update_stages()
now returns the list of stages that were updated so that we can check their milestones later.changed_fields
are now passed into_patch_update_special_fields()
so that we can check milestones and add a changed field item ifshipping_year
is set.