-
-
Notifications
You must be signed in to change notification settings - Fork 380
bugzilla changelog for 2.067.0 #920
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
Conversation
I generated the list of fixed bugzilla entries using changed with grep -h BUGZILLA ../dlang.org/changelog.dd changelog.txt | sed 's|^[ \t]*||' | sort | uniq -cd | sed -n 's|.*\(BUGZILLA [0-9]*\).*|\1|p' > duplicates I removed the duplicates from changelog.txt using this. for line in (cat duplicates)
sed -i "/$line/d" changelog.txt
end Finally inserted the changelog.txt manually into dlang.org's changelog.dd, rebuild dlang.org and looked at the changelog.html page. |
We should hide those lists behind some sort of unfold button. |
Then they wouldn't be searchable. |
Ah right. I still find this page fairly noisy, there should be clear bullet points or so. |
This looks great https://golang.org/doc/go1.3. |
I don't have a good recommendation on how to do it, but I think the changelog should omit bugs that were introduced and fixed during the release cycle. Those bugs are of almost zero value to list for anyone other than a branch follower, and those people are already aware. |
+1. Is there some way in future that we can mark this kind of bug report as a 'temporary' bug when it gets closed? Maybe with a new keyword, then the search query can be restricted to those that don't have that keyword. I also wonder if we could use another keyword for marking an issue as needing an explanation in the changelog. |
More manual annotations don't solve the problem because nobody is keen to add them. I think we could start to manually curate a list of prominent fixed bugs, with a link to the full list in Bugzilla. The current list is too long anyhow and people personally affected by a particular bug should add themselves to it's CC list to get notified. |
b97f481
to
ede37da
Compare
Updated, can we please merge this? |
I don't see why not, but maybe you also want to update the release date? |
see #933 |
bugzilla changelog for 2.067.0
thx |
No description provided.