Build Master: Scheduling II

[Andrew Edwards]

On 12/3/13, 4:23 PM, Martin Nowak wrote:
> On Tuesday, 3 December 2013 at 14:26:07 UTC, Andrew Edwards wrote:
>> Tools currently included in the packages are as follows:
>
> We need to discuss the list of included tools.
> Some of them are only available as binaries, i.e. only Walter knows how
> to build them. Also DUMPOBJ and OBJ2ASM aren't needed on linux or OSX.
> The tools strictly related to D are, dman, ddmangle and rdmd.
>
>> This list, at the very least, should include DustMite but there are
>> some other tools included in the tools repo on github that might
>> belong here. (This will be considered for inclusion in future releases
>> and will have no effect on release 2.065)
>>
>> As I am not skilled at GitHub, I will be following the
>> instructions/guidelines exactly as outlined here:
>>
>>     http://wiki.dlang.org/Development_and_Release_Process.
>
> This does not reflect how we handle things currently.
> It would be good to start from the current process (version branch +
> cherry-picking from master) and incrementally improve it towards what we
> want to achieve. The wiki depicts an idealistic process that requires a
> lot of awareness by every dev and doesn't map good onto the GitHub
> workflow.

Understood. I would however, suggest that it is a habit that we should 
get into. One of the first things that we should have devs review when 
they want to know how to contribute is to lead them to this page. As I 
matter of fact, I think it might even be a good idea to include it in 
the CONTRIBUTING.md file on GitHub or, at the very least, insert a link 
to it.

>>
>> I am working on a MacMini running OS X v10.9. I have Ubuntu 13.10
>> Server loaded in VirtualBox and will be using Jordi Sayol's script to
>> build packages for linux/Windows and Jacob Carlborg script for OSX.
>>
>> Both of these scripts require an preexisting release zip and as of
>> this moment, I am unaware of the steps to create that file. I will
>> need some instructions on how to access and run the auto tester if
>> that's what generates the zip or, if it's already automatically
>> created, instructions on how to retrieve and stage it for the build.
>
> Only Walter knows how to build the zip.
> Nick wrote a build script the produces a similar zip file,
> https://github.com/D-Programming-Language/installer/pull/24.
> Maybe we can get that in shape for the next few releases.

I'll check it out. Hopefully it does what I need.

> In the mid-term we should replace all installer scripts that depend on
> the dmd2.zip with scripts that build a platform specific release from
> source.
> Work is being done to add install targets to the Makefiles of each project.
>
> I'm currently working on a spec file to build RPMs for Fedora.
>
>>
>> I will be setting up a tag on github today for the first beta release
>> of 2.065 (2.065-b1).
>>
> It would be helpful to post a short notice in advance on the dmd-beta
> mailing list so that the devs can coordinate their work accordingly.

Will do.