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.
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
use milestones to indicate backport #5498
Conversation
👍 |
I am fine deferring this decision to @minrk, but just to play devil's Originally the logic for change is that it wasn't easy to use labels for On Wed, Apr 2, 2014 at 11:02 AM, Thomas Kluyver notifications@github.comwrote:
Brian E. Granger |
Adding labels to PRs is easy, but there is still no way to view only PRs with a specific label (you can view all Issues with a label, but not just PRs). Further, I think this better communicates when each change is actually available in a release - as we were doing it previously, we had a clear indication of what's different between 2.0 and 1.0, but that's not actually what anybody cares about. What people want to know is the difference between 2.0 and 1.2.1, but that's not easy to see with our current labeling scheme (Issues with milestone 2.0, but without any backport label). I don't feel super strongly, but I think it's worth a try. |
All true, let's give it a shot. On Wed, Apr 2, 2014 at 11:48 AM, Min RK notifications@github.com wrote:
Brian E. Granger |
I've updated the wiki |
use milestones to indicate backport
instead of labels. I think this will more clearly indicate what's new in what releases, plus it's way easier to show pull requests with a specific milestone than it is with a specific label.
use milestones to indicate backport
instead of labels.
I think this will more clearly indicate what's new in what releases, plus it's way easier to show pull requests with a specific milestone than it is with a specific label.