On 5/28/13 3:12 PM, Andrei Alexandrescu wrote:
> On 5/28/13 5:45 PM, Andrej Mitrovic wrote:
>> The timestamp for all files is dated as 2012.
>> - .chm file lacks the 2.063 changelog
>> - .chm file is extremely slow and flashes the screen all the time, I
>> guess it's probably trying to connect online and run some scripts.
>
> What is the process to build the .chm files? I think we should figure
> out a way to build them on Posix - relying on Windows to build is
> difficult because we don't have the machines.

I disagree.. particularly if you consider that there's pressure and desire to move to per-platform release zip/tarballs.  Only the windows platform should build and include that form of documentation.

>> - documentation for dead files is still being distributed
>> (http://d.puremagic.com/issues/show_bug.cgi?id=6101)).
>
> I'll look into that, thanks.

Is this another case of failing to start from a fresh directory for each doc build?  That should also include the doc push.  Sync to a clean directory and flip a symlink (or something close to that).  Anything less can leave garbage files around and/or race with not all files being present during a push to the website.




_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On 5/28/13 6:18 PM, Brad Roberts wrote:
> I disagree.. particularly if you consider that there's pressure and
> desire to move to per-platform release zip/tarballs. Only the windows
> platform should build and include that form of documentation.

Then we need at least one Windows machine with ssh access, or use wine.

>>> - documentation for dead files is still being distributed
>>> (http://d.puremagic.com/issues/show_bug.cgi?id=6101)).
>>
>> I'll look into that, thanks.
>
> Is this another case of failing to start from a fresh directory for each
> doc build? That should also include the doc push. Sync to a clean
> directory and flip a symlink (or something close to that). Anything less
> can leave garbage files around and/or race with not all files being
> present during a push to the website.

Not sure.

Andrei

_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On 5/28/2013 3:12 PM, Andrei Alexandrescu wrote:
>
> How do I get/build the changelog?

It's changelog.dd in the same directory as all the other website .dd files, and 'make' builds it.
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

Yup, it worked after tagging.

So the sequence is:

work work work
->
beta beta beta
->
TAG with new release
->
cd dlang.org && make -f posix.mak rsync
->
yay


Andrei

On 5/28/13 6:22 PM, Walter Bright wrote:
>
> On 5/28/2013 3:12 PM, Andrei Alexandrescu wrote:
>>
>> How do I get/build the changelog?
>
> It's changelog.dd in the same directory as all the other website .dd
> files, and 'make' builds it.
> _______________________________________________
> dmd-beta mailing list
> dmd-beta@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On 5/28/13, Walter Bright <walter@digitalmars.com> wrote:
> While I'm happy to get the error reports, I am unhappy that the beta has
> been
> out for 2 weeks and I get pasted for things not being "done" when nobody
> tries
> it out until the release.

I'm trying it out, but not through the .zip files, I use git instead. Maybe if you started versioning the zip files I'd be more inclined to use them (this is something that was mentioned in dconf but you seemed to have ignored the tip).

And I'm unhappy that I'm forced to mention about the broken documentation for every single release, this whole process should have been automated years ago.

But let's bury the hatchets. I think Nick mentioned it would be a good idea to have a D script of some sorts that would build the .zip release. If we had that, I suppose we could also have a test-case for the script itself to make sure we always have fresh documentation and the newest builds of all tools (e.g. the RDMD.exe in the zip file is time-stamped for 2 weeks ago).

If we had this whole release procedure open then we could start fixing
bugs such as distributing newer import libraries
(http://d.puremagic.com/issues/show_bug.cgi?id=6625), and separating
.zip files so Windows/Posix files are not mixed in the same archive.
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On Wed, 29 May 2013 00:44:08 +0200
Andrej Mitrovic <andrej.mitrovich@gmail.com> wrote:
> 
> And I'm unhappy that I'm forced to mention about the broken documentation for every single release, this whole process should have been automated years ago.
> 
> But let's bury the hatchets. I think Nick mentioned it would be a good idea to have a D script of some sorts that would build the .zip release. If we had that, I suppose we could also have a test-case for the script itself to make sure we always have fresh documentation and the newest builds of all tools (e.g. the RDMD.exe in the zip file is time-stamped for 2 weeks ago).
> 

FWIW, I am actually working on automating as much as I can. I'm starting with a minimal DMD bootstrapper (well, two really: one for Win and one for Posix) so that, hopefully, all of our other tools can safely rely on D being available.

Hopefully, I can have it all done in time for 2.064. We'll see.

Speaking of bootstrapping D (as this could impact what I'm doing as
well), there's been talk about parts of DMD being rewritten in D.
Where are we on that?
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On 5/28/13 3:44 PM, Andrej Mitrovic wrote:
> On 5/28/13, Walter Bright <walter@digitalmars.com> wrote:
>> While I'm happy to get the error reports, I am unhappy that the beta has
>> been
>> out for 2 weeks and I get pasted for things not being "done" when nobody
>> tries
>> it out until the release.
>
> I'm trying it out, but not through the .zip files, I use git instead.
> Maybe if you started versioning the zip files I'd be more inclined to
> use them (this is something that was mentioned in dconf but you seemed
> to have ignored the tip).
>
> And I'm unhappy that I'm forced to mention about the broken
> documentation for every single release, this whole process should have
> been automated years ago.
>
> But let's bury the hatchets. I think Nick mentioned it would be a good
> idea to have a D script of some sorts that would build the .zip
> release. If we had that, I suppose we could also have a test-case for
> the script itself to make sure we always have fresh documentation and
> the newest builds of all tools (e.g. the RDMD.exe in the zip file is
> time-stamped for 2 weeks ago).
>
> If we had this whole release procedure open then we could start fixing
> bugs such as distributing newer import libraries
> (http://d.puremagic.com/issues/show_bug.cgi?id=6625), and separating
> .zip files so Windows/Posix files are not mixed in the same archive.

Ignore what may or may not exist outside the current make files.  Just start with what exists in them.  Soon after there are workable targets to the existing makefiles, I'll get the auto-tester to execute them and upload the results to s3 and make them public.

I really don't think the zip/tarball creation steps should be a separate script.  A while back I started putting together a proof of concept / strawman version of what I was thinking.  They're likely somewhat bitrotten, but look at my account on github in the dmd, druntime, and phobos repos.  There's an 'install' branch for each of them with a commit or two to each.

I stopped when I git the documentation as the build systems for them are absurdly complex and convoluted.  Additionally, the tools stuff needs work, though its been ages since I last looked at them.

- Brad
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On Tue, 28 May 2013 18:19:57 -0700
Brad Roberts <braddr@puremagic.com> wrote:
> 
> Ignore what may or may not exist outside the current make files. Just start with what exists in them.  Soon after there are workable targets to the existing makefiles, I'll get the auto-tester to execute them and upload the results to s3 and make them public.
> 
> I really don't think the zip/tarball creation steps should be a separate script.  A while back I started putting together a proof of concept / strawman version of what I was thinking.  They're likely somewhat bitrotten, but look at my account on github in the dmd, druntime, and phobos repos.  There's an 'install' branch for each of them with a commit or two to each.
> 
> I stopped when I git the documentation as the build systems for them are absurdly complex and convoluted.  Additionally, the tools stuff needs work, though its been ages since I last looked at them.
> 

While that may be a feasible approach, IMO I think it's worth
minimizing the amount of work D's infrastructure needs to do in
shell, batch and makefile scripting. Compared to D itself, those tend
to be less portable (most notably the Win/Posix rift), more difficult to
write/maintain, and less graceful with unexpected failures. Plus
there's the increased dogfooding and the whole "self-hosted bragging
rights" thing that some people value.
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On 05/29/2013 12:12 AM, Andrei Alexandrescu wrote:
> How do I get/build the changelog? 
https://github.com/D-Programming-Language/tools/blob/master/changed.d
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta

On 05/28/2013 09:36 PM, Walter Bright wrote:
> The uploads are done, time to update the web site.
>
> http://digitalmars.com/d/download.html
> _______________________________________________
> dmd-beta mailing list
> dmd-beta@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta
>
>
I don't know how the installers are build but at least we failed to set RELEASE=1 for posix.mak.
So now dmd's version is shown as " DMD64 D Compiler v2.063-devel".

https://github.com/D-Programming-Language/dmd/pull/1737#issuecomment-15216216 

_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta