On Monday, 18 February 2013 at 01:02:43 UTC, Walter Bright wrote:
> http://digitalmars.com/d/download.html
>
> The dlang.org site isn't updated yet, but the downloads are there.

Has anyone even tested the release package? I get

    make: *** No rule to make target `../VERSION', needed by `verstr.h'.  Stop.

during building of dmd. People in #d report the same. It can't work, the file isn't even in the package.

Am Sun, 17 Feb 2013 17:02:20 -0800
schrieb Walter Bright <newshound2@digitalmars.com>:

> http://digitalmars.com/d/download.html
> 
> The dlang.org site isn't updated yet, but the downloads are there.

I didn't read the whole thread now. Just reporting that
the .zip package cannot be compiled due to missing VERSION
file and that all the Phobos documentation now has empty
"Examples:" sections (which I thought was already fixed).

-- 
Marco

On Monday, February 18, 2013 18:43:37 Dmitry Olshansky wrote:
> 18-Feb-2013 17:22, Leandro Lucarella пишет:
> >> I also would love to see an automatically generated changelog similar to the original based on the bugzilla data. Can we add a "changelog description" field to bug reports so if the bug description (which arguably shouldn't be changed) isn't a very good changelog entry, that is used instead?
> > 
> > All we need to do is force people to update the changelog when making a pull request. That's it. You are making everything more complex than it should be...
> 
> Or instead somebody just has to take time and write down 10 most important things in new release. Add this task to release manager role.
> 
> *That's* what interesting not pushing more grunt work on contributors that basically doesn't work at all.
> 
> Other then this a small script to expand the bugzilla entries into a webpage (just like before title + link to bugzilla).

Exactly. It would be nice to have the list of bug fixes and whatnot listed on the page directly rather than linked to, but having that managed automatically is great. The real problem is that we need a set of "release notes" at the top which lists the important changes. That just means that someone needs to take the time to write that up for each release. Updating the changelog manually is not only broken because stuff gets missed, but it's broken because it causes merge problems if you merge in the changelog changes at the same time as the commit. We don't need all of that extra grunt work. We just need the release notes section to be written by someone (or someones) in preparation for the release.

- Jonathan M Davis

On 2/18/2013 8:47 AM, Bill Baxter wrote:
> Must be a problem with mobile Chrome then. Probably not specific to the new
> change log handling. In chrome that entire content pane has a tendency to
> disappear.

I'm still not sure if you're referring to the changelog.html page or the bugzilla page.

On 2/18/2013 9:02 AM, Sven-Hendrik Haase wrote:
> On Monday, 18 February 2013 at 01:02:43 UTC, Walter Bright wrote:
>> http://digitalmars.com/d/download.html
>>
>> The dlang.org site isn't updated yet, but the downloads are there.
>
> Has anyone even tested the release package? I get
>
>      make: *** No rule to make target `../VERSION', needed by `verstr.h'.  Stop.
>
> during building of dmd. People in #d report the same. It can't work, the file
> isn't even in the package.

I forgot to include VERSION in the zip file. Its contents are:

2.062

all on one line. I'll fix the packages.

On Monday, 18 February 2013 at 01:31:47 UTC, Mike Parker wrote:
> On Monday, 18 February 2013 at 01:02:43 UTC, Walter Bright wrote:
> I've lost the motivation to even look at the changelog now.

+1

On 2/18/13, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> wrote:
> I agree we need to improve on this. One way to achieve that, seeing as marketing is not Walter's focus, is to denote a release czar who has that particular task around releases. Andrej, would you want to try that role?

How about I write how a release would look like for 2.062 (a mockup), and if we're all fond of it we can base this on the upcoming release? That way we don't have to argue days before a release on what the release should look like.

On Tue, 19 Feb 2013, Andrej Mitrovic wrote:

> On 2/18/13, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> wrote:
> > I agree we need to improve on this. One way to achieve that, seeing as marketing is not Walter's focus, is to denote a release czar who has that particular task around releases. Andrej, would you want to try that role?
> 
> How about I write how a release would look like for 2.062 (a mockup), and if we're all fond of it we can base this on the upcoming release? That way we don't have to argue days before a release on what the release should look like.

How about writing one for 2.062 that can be inserted into the change log instead of the current links rather than a mockup that might represent what a change log might look like?

On 2/18/13, Walter Bright <newshound2@digitalmars.com> wrote:
> http://digitalmars.com/d/download.html

Argh the chm generation is awful now. I have to wait 5 seconds every time I open a page in CHM (only the pages not in Phobos like language reference, how-to's, etc). Sometimes hh.exe (CHM viewer) freezes and uses 100% of a CPU core for several seconds before unfreezing.

And the Phobos pages have no styling.

On 2/19/13, Brad Roberts <braddr@puremagic.com> wrote:
> How about writing one for 2.062 that can be inserted into the change log instead of the current links rather than a mockup that might represent what a change log might look like?

Yes. I'll get to it and make a pull request once it's ready.