All,

The following lists my progress and few points for which I need clarification.

I created a git hub account (AndrewEdwards) and obtained necessary access to all repos at github.com/D-Programming-Language. Access to the ftp is pending but should be granted shortly.

I've forked the following repos in order to comply with the Development_and_Release_Process documentation at wiki.dlang.org and Nick Sabalausky packaging tool:

	dmd, druntime, phobos, tools, dlang.org, installer

Following instructions at [1], I created a local repository prepared branch 2.065 in accordance with [2] for the forked repositories.

I've prepared a build environment on Mac OS X 10.9 with five VirtualBox images as follows:

	1) Mac OS X 10.9
	2) FreeBSD 9.2
	3) Windows 7
	4) Fedora 19
	5) Ubuntu 12.04

SSH was configured on all systems and keys were generated and uploaded to GitHub. I am experiencing a slight problem on Fedora though. After initial config, I was able to login remotely but now receive the error "Connection refused". Can't remember changing anything to cause this but anything is possible so I won't discount it. Worst case scenario, I'll wipe and reinstall it (for the novice the road to professional can seem very long).

Cygwin is installed on Windows 7 and SSHD properly configured.

Martin Norwak and Nick Sabalausky are working on polishing up the build script. Once this is complete, I will generate the binaries for the betas and upload.

Questions requiring clarification:

	1) Do I need to create a local repository on each system on which I build or does the one local repository on the base system suffice?

	2) What is the process to update a branch with all changes master? I will need to do this because a lot of changes have occurred since the 2.065 branches were created but the actual betas are not yet prepared. Going forward, this is the only time this will occur.

	3) Walter: Need your input/decision on what which tools are strictly required for the dmd release.

Note:
	Release 2.065 will be treated in the same fashion as previous releases in order to afford devs additional time to become familiar with documented release process. Meaning, after the betas are prepared and made available, bug fixes will merged to master and regressions cherry-picked into the branch.

I'm aiming to make betas public by 17 December.

Regards,
Andrew

-------------------------
[1] http://wiki.dlang.org/Development_and_Release_Process#Local_repository_setup

[2] http://wiki.dlang.org/Development_and_Release_Process#Preparing_a_new_major_release

On Monday, 9 December 2013 at 14:49:05 UTC, Andrew Edwards wrote:
> I am experiencing a slight problem on Fedora though. After initial config, I was able to login remotely but now receive the error "Connection refused". Can't remember changing anything to cause this but anything is possible so I won't discount it.

Maybe you have forgotten to add ssh daemon to autostart list?

On 2013-12-09 15:48, Andrew Edwards wrote:

> I've prepared a build environment on Mac OS X 10.9 with five VirtualBox
> images as follows:
>
>      1) Mac OS X 10.9

Make sure I got GCC, I don't think the test suite passes if DMD built with Clang.

-- 
/Jacob Carlborg

Also I don't think you need to bother with maintaining own forks unless you are planning to actually push something upstream. Just cloning core repos on build systems should be enough.

On Monday, 9 December 2013 at 14:49:05 UTC, Andrew Edwards wrote:
> 	2) What is the process to update a branch with all changes master? I will need to do this because a lot of changes have occurred since the 2.065 branches were created but the actual betas are not yet prepared. Going forward, this is the only time this will occur.

If branch does not have own commits to be preserved and needs to just be synced with master state (assuming D-Programming-Language remote is named `upstream`):

   git fetch upstream # download current remote state
   git checkout 2.065 # go to release branch
   git reset --hard upstream/master # make it identical to current master
   git push -f origin 2.065 # update own fork
   git push -f upstream 2.065 # update branch in core repos, careful here!

I can't imagine any other case when one may want to update release branch from master so it must the what you need.

On 12/9/13, 10:28 AM, Dicebot wrote:
> On Monday, 9 December 2013 at 14:49:05 UTC, Andrew Edwards wrote:
>> I am experiencing a slight problem on Fedora though. After initial
>> config, I was able to login remotely but now receive the error
>> "Connection refused". Can't remember changing anything to cause this
>> but anything is possible so I won't discount it.
>
> Maybe you have forgotten to add ssh daemon to autostart list?


Thanks... that's exactly it.

On 12/9/13, 10:36 AM, Dicebot wrote:
> Also I don't think you need to bother with maintaining own forks unless
> you are planning to actually push something upstream. Just cloning core
> repos on build systems should be enough.
>

At least for the time being, the only things I need to push are tags/branches when I create them. Hopefully that will change in the future.

On Monday, 9 December 2013 at 15:51:47 UTC, Dicebot wrote:
> On Monday, 9 December 2013 at 14:49:05 UTC, Andrew Edwards wrote:
>> 	2) What is the process to update a branch with all changes master? I will need to do this because a lot of changes have occurred since the 2.065 branches were created but the actual betas are not yet prepared. Going forward, this is the only time this will occur.
>
> If branch does not have own commits to be preserved and needs to just be synced with master state (assuming D-Programming-Language remote is named `upstream`):
>
>    git fetch upstream # download current remote state
>    git checkout 2.065 # go to release branch
>    git reset --hard upstream/master # make it identical to current master
>    git push -f origin 2.065 # update own fork
>    git push -f upstream 2.065 # update branch in core repos, careful here!
>
> I can't imagine any other case when one may want to update release branch from master so it must the what you need.

Note that, at least phobos repository already has some own commits in 2.065 branch.

Kenji Hara

On 2013-12-09 16:30, Jacob Carlborg wrote:

> Make sure I got GCC, I don't think the test suite passes if DMD built
> with Clang.

* you got.

-- 
/Jacob Carlborg

On 12/10/13, 2:16 AM, Jacob Carlborg wrote:
> On 2013-12-09 16:30, Jacob Carlborg wrote:
>
>> Make sure I got GCC, I don't think the test suite passes if DMD built
>> with Clang.
>
> * you got.
>

Ok... will do.