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.

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

Create README.md + labeling and milestone guidance #33

Merged
merged 1 commit into from
Apr 12, 2016
Merged

Create README.md + labeling and milestone guidance #33

merged 1 commit into from
Apr 12, 2016

Conversation

wolenetz
Copy link
Member

No description provided.

@wolenetz
Copy link
Member Author

Jerry and Mark, please take a look. I'll send to public-html-media shortly with a reference to this. Essentially, this guidance is my understanding of what Jerry and I did when triaging MSE github issues last week, with a few clarifications and a couple corrections (which I'll also highlight in the p-h-m email I'm about to send...) Thanks!

@wolenetz
Copy link
Member Author

As part of this summarization, two action items were discovered. I would like to make sure we're all on the same page for MSE and use this pull request to make sure Mark, Jerry and I agree with the guidance and the following:

  1. Generally, we should consider closing V.Next MSE issues (for now, at least).
  2. We should change the currently-labeled “needs author input” to “needs feedback” and assign to appropriate reporter to obtain that feedback. During triage, we misunderstood “author” to mean bug author, not web author. We’ll also need to add a separate, new, “needs author input” label for future usage for when we might need input from web authors.

@wolenetz
Copy link
Member Author

@jdsmith3000 and @mwatson2, it would be good to get this reviewed, updated if necessary, and landed as soon as possible. Friendly ping :)

A bug in version # of the spec.
Currently, V1 is the first version of MSE (in CR in Q4 2015).

### “V.Next”:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VNext probably makes more sense since that will make it alphabetically after V# (i.e. in the Milestones dropdown).

Alternatively, use a little 'v' in all cases: v1, vNext

@wolenetz
Copy link
Member Author

I like the alternative (little 'v' in all cases). I'll make that change soon to this PR.

@wolenetz
Copy link
Member Author

We also just added a "breaking change" label to track issues that might possibly cause re-entry to CR, for example. Needs to be added to this PR, too.

@jdsmith3000
Copy link
Contributor

This draft looks good, Matt. I agree with using VNext and adding a breaking change description. I suggest also adding our recent V1Nonbreaking milestone. With those changes, we should accept this PR.

@jdsmith3000
Copy link
Contributor

To confirm, I think we should match the EME milestones, using capital "V" and no decimals. They are currently "V1", "V1NonBlocking" and "VNext". I plan to edit these in a triage pass today.

@wolenetz
Copy link
Member Author

I've updated the PR with a rebase and to add "V#NonBlocking" milestone, "breaking change" label, and rename "V.Next" to "VNext". I believe this satisfies all comments on the original PR and I'll merge this PR soon.

@wolenetz wolenetz merged commit 9f4bfb0 into w3c:gh-pages Apr 12, 2016
@wolenetz wolenetz deleted the wolenetz-patch-1 branch April 12, 2016 00:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants