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

docs: Add Known issues to v1.7.0/1.7.1 CHANGELOG #1473

Closed
wants to merge 1 commit into from

Conversation

yosuke-furukawa
Copy link
Member

On evangelism WG, we are writing weekly updates.
We have not found the Known issues area. So I just added Known issues area.

On evangelism WG, we are writing weekly updates. 
We have not found the Known issues area. So I just added Known issues area.
@brendanashworth
Copy link
Contributor

Question: do we have a process / system for figuring out what counts as a "known issue"? Are they usually just copied from previous changelogs? Maybe we should make a label for them?

@brendanashworth brendanashworth added the doc Issues and PRs related to the documentations. label Apr 20, 2015
@yosuke-furukawa
Copy link
Member Author

do we have a process / system for figuring out what counts as a "known issue"?

I don't know. But I think release manager picks up known issues from issue list.

Are they usually just copied from previous changelogs?

No. release manager added new issues to v1.8.0 CHANGELOG.

Maybe we should make a label for them?

+1

@rvagg
Copy link
Member

rvagg commented Apr 20, 2015

@yosuke-furukawa || @brendanashworth please go ahead and make a label for them and include the existing ones and any others that you find. Perhaps I'll build something in to changelog-maker to help automate.

@brendanashworth
Copy link
Contributor

I added a "confirmed-bug" tag for now.

@rvagg
Copy link
Member

rvagg commented Apr 20, 2015

lgtm btw @yosuke-furukawa, land at will

@domenic
Copy link
Contributor

domenic commented Apr 20, 2015

I don't understand personally what differentiates known issues from this entire list?

@Fishrock123
Copy link
Contributor

@domenic "our bugs" (not deps, usually.)

@domenic
Copy link
Contributor

domenic commented Apr 20, 2015

@Fishrock123 so you really think that there are only 6 bugs that are "ours" and the other 160 are in the deps?

@Fishrock123
Copy link
Contributor

The issue tracker is not strictly for bugs you know. :)

One could argue, we could just link it, but that would not be correct in the future.

i.e. #1415 is definitely not a bug nor an "issue" per-say.

@domenic
Copy link
Contributor

domenic commented Apr 20, 2015

Sure, but just doing a quick scan, there are a lot of bugs there beyond just the six. I could start listing them but I'm not sure it would be helpful.

@domenic
Copy link
Contributor

domenic commented Apr 20, 2015

Also my more general point is that it seems strange to list "known issues" in the changelog every release given that the place people should go to find known issues is, well, the issue tracker.

@Fishrock123
Copy link
Contributor

Also my more general point is that it seems strange to list "known issues" in the changelog every release given that the place people should go to find known issues is, well, the issue tracker.

Sure, but we can't get a snapshot for when that release went out.

@brendanashworth
Copy link
Contributor

@yosuke-furukawa will you be merging this?

@yosuke-furukawa
Copy link
Member Author

@brendanashworth OK. I will do it.

yosuke-furukawa added a commit that referenced this pull request Apr 28, 2015
PR-URL: #1473
Reviewed-By: Brendan Ashworth <brendan.ashworth@me.com>
@yosuke-furukawa
Copy link
Member Author

landed 391cae3
Thank you for review.

@yosuke-furukawa yosuke-furukawa deleted the yosuke-furukawa-patch-1 branch April 28, 2015 16:16
@rvagg rvagg mentioned this pull request Apr 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc Issues and PRs related to the documentations.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants