Skip to content

Conversation

MartinNowak
Copy link
Member

No description provided.

@MartinNowak
Copy link
Member Author

I generated the list of fixed bugzilla entries using changed with --start=2014-08-18, then found all the duplicate bugzilla entries using this.

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.

@MartinNowak
Copy link
Member Author

We should hide those lists behind some sort of unfold button.

@CyberShadow
Copy link
Member

We should hide those lists behind some sort of unfold button.

Then they wouldn't be searchable.

@MartinNowak
Copy link
Member Author

Then they wouldn't be searchable.

Ah right. I still find this page fairly noisy, there should be clear bullet points or so.

@MartinNowak
Copy link
Member Author

This looks great https://golang.org/doc/go1.3.

@braddr
Copy link
Member

braddr commented Mar 4, 2015

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.

@ntrel
Copy link
Contributor

ntrel commented Mar 5, 2015

the changelog should omit bugs that were introduced and fixed during the release cycle

+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.

@MartinNowak
Copy link
Member Author

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.

@MartinNowak
Copy link
Member Author

Updated, can we please merge this?

@CyberShadow
Copy link
Member

I don't see why not, but maybe you also want to update the release date?

@MartinNowak
Copy link
Member Author

see #933

CyberShadow added a commit that referenced this pull request Mar 24, 2015
@CyberShadow CyberShadow merged commit f763124 into dlang:master Mar 24, 2015
@MartinNowak MartinNowak deleted the bugzillaChangelog branch March 24, 2015 18:14
@MartinNowak
Copy link
Member Author

thx

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.

4 participants