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.
{{ message }}
Activity
WeatherGod commentedon Mar 7, 2017
#8219QuLogic commentedon Mar 7, 2017
#8212dstansby commentedon Mar 7, 2017
#8215anntzer commentedon Mar 8, 2017
#8233NelleV commentedon 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 commentedon Mar 8, 2017
(That's without considering the risk of backporting documentation that uses new features).
dstansby commentedon Mar 8, 2017
#8211dstansby commentedon Mar 8, 2017
Would backporting to
2.0.xinstead be fine?anntzer commentedon Mar 8, 2017
#8228-- renames don't get backported -- @QuLogic.dstansby commentedon 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 commentedon 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 commentedon May 1, 2017
Thanks @dstansby.