Repository navigation
need to backport docathon PRs #8223
Description
Rather than backporting each individual docathon PR, we will do one large docathon merge at the end of the week. Let's keep a list here of the docathon PRs that were accepted.
| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Rather than backporting each individual docathon PR, we will do one large docathon merge at the end of the week. Let's keep a list here of the docathon PRs that were accepted.
| Back | FazBrowse Home | New Git URL |
Activity
WeatherGod commented on Mar 7, 2017
#8219
QuLogic commented on Mar 7, 2017
#8212
dstansby commented on Mar 7, 2017
#8215
anntzer commented on Mar 8, 2017
#8233
NelleV commented on Mar 8, 2017
As mentionned on gitter, I feel uncomfortable backporting documentation pull request. We've identified a bug in the 2.0.0 documentation reference in a ticket (#8235), and if we backport the pull request that fixes this bug, we loose the information allowing to identify when the bug was discovered.
NelleV commented on Mar 8, 2017
(That's without considering the risk of backporting documentation that uses new features).
dstansby commented on Mar 8, 2017
#8211
dstansby commented on Mar 8, 2017
Would backporting to 2.0.x instead be fine?
anntzer commented on Mar 8, 2017
#8228 -- renames don't get backported -- @QuLogic.
dstansby commented on Apr 10, 2017
The docathon has long gone, so I'm happy to port these all back to 2.0.x - if anyone has any objections then shout, otherwise I will do them in a couple of days!
dstansby commented on May 1, 2017
Great, these are all backported, thanks to everyone who did the original PRs, and sorry for the delay on my end...
QuLogic commented on May 1, 2017
Thanks @dstansby.