On 2/19/2013 8:29 PM, Andrej Mitrovic wrote:
> On 2/19/13, Andrej Mitrovic <andrej.mitrovich@gmail.com> wrote:
>> I can see now there's a d.chm file in \bin.
>
> Walter that .chm file you're distributing in Windows\bin is v2.058
> (judging by the changelog), or some other version, but it definitely
> isn't the latest because documentation is missing (e.g. getProtection
> trait).
>
> Why can't we open up the release process so we know exactly which
> scripts and procedure is used to make a release .zip? That way we can
> catch these bugs in time.
>

It was in the beta.

On Monday, 18 February 2013 at 01:31:47 UTC, Mike Parker wrote:
> But I just want to throw in my 2 cents about the new changelog format. It's impossible now to tell at a glance what the major changes/fixes are. Clicking through four links to find them is bad enough, but the layout and color scheme of the Bugzilla search results makes it even more time consuming. I know it's easier from a maintenance perspective, but I've lost the motivation to even look at the changelog now. And it's something I really used to look forward to with each release.

I guess I have two cents as well. Might as well throw them in!

Each developer who works on bugs and enhancements for a given release can keep a private journal, some small text file somewhere. It only needs to note what that developer considers a highlight, something worth mentioning in a release notes format. When release time approaches, the manager solicits their notes from them, gives the whole thing a quick edit to avoid repeats, and you have your release notes. Now the release manager isn't responsible for remembering everything, just assembling it.

The things which are the most interesting will probably be on their developers' minds anyway, so it's probably not too much punishment to ask them for their notes.

On 02/19/2013 09:57 PM, Zach the Mystic wrote:

> Each developer who works on bugs and enhancements for a given release
> can keep a private journal, some small text file somewhere.

+1

Although, I have seen this done in Bugzilla itself: Every bug has a field that contains what goes into the release notes. Any bug that is a part of a release must have that field filled in and reviewed. Pretty simple and works well.

Ali

On 2/19/13 6:01 PM, Walter Bright wrote:
> On 2/18/2013 11:17 PM, Jacob Carlborg wrote:
>> On 2013-02-18 21:58, Walter Bright wrote:
>>
>>> I forgot to include VERSION in the zip file. Its contents are:
>>>
>>> 2.062
>>>
>>> all on one line. I'll fix the packages.
>>
>> Do you have an automated script for packing up the zip file? If not,
>> this is the
>> time to create one. We have seen this problem before, IIRC.
>>
>
> Yes, I do use a script. The script has to copy all the correct files
> over to the right place. VERSION is a new file in a new place, and the
> script needed updating to copy that one.
>
> Automation is great, and I use it. But files appear, disappear, and
> change directory from release to release, and so the scripts must change
> as well.

Maybe you can make the script uncompress the zip and build dmd... if it can build it, everything's fine :-)

On Wednesday, 20 February 2013 at 06:39:12 UTC, Ali Çehreli wrote:
> On 02/19/2013 09:57 PM, Zach the Mystic wrote:
>
> > Each developer who works on bugs and enhancements for a given
> release
> > can keep a private journal, some small text file somewhere.
>
> +1
>
> Although, I have seen this done in Bugzilla itself: Every bug has a field that contains what goes into the release notes. Any bug that is a part of a release must have that field filled in and reviewed. Pretty simple and works well.
>
> Ali

That's my first '+1' ever!

+1 to you, sir!

> I forgot to include VERSION in the zip file. Its contents are:
>
> 2.062
>
> all on one line. I'll fix the packages.

has this been done? it still seems the zip file doesn't contain it.

And what about druntime.lib. Is it there?
Or is it not needed?
Dňa 27. 2. 2013 9:08 timotheecour  wrote / napísal(a):
>> I forgot to include VERSION in the zip file. Its contents are:
>>
>> 2.062
>>
>> all on one line. I'll fix the packages.
>
> has this been done? it still seems the zip file doesn't contain it.

On Wednesday, February 27, 2013 09:30:24 Lubos Pintes wrote:
> And what about druntime.lib. Is it there?
> Or is it not needed?

druntime is linked in as part of Phobos, so all you need is phobos.lib. It hasn't been packaged as a separate library for quite a while now.

- Jonathan M Davis