Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change deprecation window from 3 to 6 months #5694

Closed
alyssawilk opened this issue Jan 23, 2019 · 0 comments · Fixed by #5737
Closed

Change deprecation window from 3 to 6 months #5694

alyssawilk opened this issue Jan 23, 2019 · 0 comments · Fixed by #5737
Assignees
@alyssawilk
Labels
area/community enhancement Feature requests. Not bugs or questions.

Comments

@alyssawilk
Copy link
Contributor

While I'm musing on Envoy deprecation process (#5693, #5559) it'd be really helpful if we could change the deprecation window from 3 months / 1 release to 6 months / 2 releases. For major features it'd give folks time to allocate time to properly qual and test new code paths, and for minor features it'd still allow better customer communication for behavioral changes.

Throwing this out to the community - if no one objects I will make the changes to the tooling, and then we can bike-shed over on #5559 what we want the default deprecation process to be (how long on each phase)
@alyssawilk alyssawilk added enhancement Feature requests. Not bugs or questions. area/community labels Jan 23, 2019
@alyssawilk alyssawilk self-assigned this Jan 23, 2019
@alyssawilk alyssawilk mentioned this issue Jan 28, 2019
Merged
alyssawilk added a commit that referenced this issue Jan 30, 2019
@alyssawilk
governance: changing deprecation policy from one release to two. (#5737)
851c986 
This brings deprecation window from between 0-3 months to 3-6 months. Updating tools / docs accordingly.

Note the deprecation script can be skipped when we cut the next release because of this.
Also fixing up the deprecation script to handle (date)s and (pending)

Docs Changes: n/a
Release Notes: inline
Fixes #5694

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
danzh2010 pushed a commit to danzh2010/envoy that referenced this issue Jan 31, 2019
@alyssawilk @danzh1989
governance: changing deprecation policy from one release to two. (env…
5378e95 
…oyproxy#5737)

This brings deprecation window from between 0-3 months to 3-6 months. Updating tools / docs accordingly.

Note the deprecation script can be skipped when we cut the next release because of this.
Also fixing up the deprecation script to handle (date)s and (pending)

Docs Changes: n/a
Release Notes: inline
Fixes envoyproxy#5694

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>

Signed-off-by: alyssawilk <alyssar@google.com>
fredlas pushed a commit to fredlas/envoy that referenced this issue Mar 5, 2019
@alyssawilk @fredlas
governance: changing deprecation policy from one release to two. (env…
be8a40a 
…oyproxy#5737)

This brings deprecation window from between 0-3 months to 3-6 months. Updating tools / docs accordingly.

Note the deprecation script can be skipped when we cut the next release because of this.
Also fixing up the deprecation script to handle (date)s and (pending)

Docs Changes: n/a
Release Notes: inline
Fixes envoyproxy#5694

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Signed-off-by: Fred Douglas <fredlas@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@alyssawilk alyssawilk

Labels
area/community enhancement Feature requests. Not bugs or questions.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

governance: changing deprecation policy from one release to two. alyssawilk/envoy
1 participant
@alyssawilk