January 07, 2014



Andrej Mitrovic <andrej.mitrovich@gmail.com> schrieb:
>Well I'm still here tomorrow, I'll write up as much as I can and then others can contribute more pulls if needed (just like the last time).

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


January 09, 2014
Now there is a v2.065-b1 tag for dmd.
<https://github.com/D-Programming-Language/dmd/releases>https://github.com/D-Programming-Language/dmd/releases/tag/v2.065-b1
This opens a can of questions.
Who created it, why didn't anybody told me (and others) about it, how
was it decided that dmd is beta ready, what's the intent/plan for the
other repos?
Please communicate before doing non-obvious steps so that others can
learn the process too.

Should we now tag all other repos? Who is feeling responsible for each repo, e.g. tracks that regressions are fixed and tags the branch?

I'm making progress for automatic release building.
https://github.com/MartinNowak/installer/tree/vagrant
I still have to waste a lot of time (rebasing, workarounding...),
because nobody merges my mostly trivial installer pulls.
https://github.com/D-Programming-Language/installer/pulls

Still here is a snapshot release of the 2.065 branches with a few
remaining issues.
- FreeBSD has no dmd.conf
- contains a few spurious .gitignore files

Things to recheck.
- link.exe is updated to optlink 8.00.15
- OSX dmd binaries are all 64 bit
- Is the increased size only due to the added FreeBSD binaries?
- ??? help appreciated

I'm working on these but would appreciate help in the form of monitoring the installer repo. http://dlang.dawg.eu/download/dmd.2.065.snapshot.1.zip

I remember that we found the name "beta" inappropriate during the last
release because
there are still open regressions.
Releasing a beta to helpful testers before obvious bugs are fixed is
rude because they will waste
their time to reproduce know issues.
To provide a single fix I can easily build more snapshots (takes about
20 unattended minutes).

-Martin



January 09, 2014
On 01/09/2014 08:33 PM, Martin Nowak wrote:
> I'm working on these but would appreciate help in the form of monitoring the installer repo.
> http://dlang.dawg.eu/download/dmd.2.065.snapshot.1.zip
http://dlang.dawg.eu/download/checksum.md5

f52d32c74fd6045e15cf59783e9d6c3d  dmd.2.065.snapshot.1.zip

http://dlang.dawg.eu/download/checksum.sha1

1deb415408dc64f6871e3d55c8b0dee91fbbf1eb  dmd.2.065.snapshot.1.zip




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


January 09, 2014
Please be aware that Andrew Edwards is the buildmaster and is coordinating all this.

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


January 09, 2014
On 9 jan 2014, at 20:33, Martin Nowak <code@dawg.eu> wrote:

> - OSX dmd binaries are all 64 bit


I don't think this is a problem. It will be hard to find a Mac that cannot run 64bit binaries. Otherwise just run an additional compilation and merge the binaries with "lipo":

$ lipo -create -output dmd dmd32 dmd64

You can do the same with libraries.

-- 
/Jacob Carlborg


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


January 09, 2014
On 1/9/2014 12:57 PM, Jacob Carlborg wrote:
> On 9 jan 2014, at 20:33, Martin Nowak <code@dawg.eu> wrote:
>
>> - OSX dmd binaries are all 64 bit
>
> I don't think this is a problem. It will be hard to find a Mac that cannot run 64bit binaries. Otherwise just run an additional compilation and merge the binaries with "lipo":
>
> $ lipo -create -output dmd dmd32 dmd64
>
> You can do the same with libraries.
>

We haven't shipped 32 bit binaries on OSX for a while now, and nobody has noticed. 32 bits on OSX is dead.
_______________________________________________
dmd-beta mailing list
dmd-beta@puremagic.com
http://lists.puremagic.com/mailman/listinfo/dmd-beta


January 09, 2014
On 1/9/14, 2:33 PM, Martin Nowak wrote:
> Now there is a v2.065-b1 tag for dmd.
> <https://github.com/D-Programming-Language/dmd/releases>https://github.com/D-Programming-Language/dmd/releases/tag/v2.065-b1
> This opens a can of questions.
> Who created it, why didn't anybody told me (and others) about it, how
> was it decided that dmd is beta ready, what's the intent/plan for the
> other repos?
> Please communicate before doing non-obvious steps so that others can
> learn the process too.
>
Martin, I created this tag back when I just started. It was discussed in my initial announcement after creating the 2.065 branch. Either way, the tag will need to be deleted and recreated after all pushing the required files to build this release to the 2.065 branch. With your progress on vagrant/virtualbox I am hoping I will be able to build the 2.065 branch very soon. I have been able to use it to build head but not the 2.065 branch. This is largely because patches are being merged to head but not pushed to the branch.
> Should we now tag all other repos? Who is feeling responsible for each repo, e.g. tracks that regressions are fixed and tags the branch?
>
I am responsible for this. Request however, that this particular tag be deleted (v2.065-b1) because we're not ready. I am reading Pro Git right now because I made a number of mistakes a few weeks back and decided not to play in the live repo until I get a better grasp of how to use it. That being said, I will not delay the process because of my shortcomings so as soon as regressions are addressed and I can build the 2.065 branch without errors, I will release the beta.
> I'm making progress for automatic release building. https://github.com/MartinNowak/installer/tree/vagrant
I will check this out tonight. Thanks for the hard work.
> I still have to waste a lot of time (rebasing, workarounding...),
> because nobody merges my mostly trivial installer pulls.
> https://github.com/D-Programming-Language/installer/pulls
> Still here is a snapshot release of the 2.065 branches with a few
> remaining issues.
> - FreeBSD has no dmd.conf
> - contains a few spurious .gitignore files
>
> Things to recheck.
> - link.exe is updated to optlink 8.00.15
> - OSX dmd binaries are all 64 bit
> - Is the increased size only due to the added FreeBSD binaries?
> - ??? help appreciated
>
> I'm working on these but would appreciate help in the form of monitoring the installer repo. http://dlang.dawg.eu/download/dmd.2.065.snapshot.1.zip
>
> I remember that we found the name "beta" inappropriate during the last
> release because
> there are still open regressions.
> Releasing a beta to helpful testers before obvious bugs are fixed is
> rude because they will waste
> their time to reproduce know issues.
> To provide a single fix I can easily build more snapshots (takes about
> 20 unattended minutes).
>
> -Martin
>
>
>
> _______________________________________________
> dmd-beta mailing list
> dmd-beta@puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta



January 09, 2014
Rather than trying to fix the 2.065 branch, perhaps we should simply abandon it and go with 2.066?

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


January 10, 2014
On Jan 10, 2014, at 01:24 AM, Walter Bright <walter@digitalmars.com> wrote:

> Rather than trying to fix the 2.065 branch, perhaps we should simply abandon it and go with 2.066?

Absolutely not. We already have a very confusing release process, don't making more confusing by skipping version numbers.

--
/Jacob Carlborg

January 10, 2014
On Jan 09, 2014, at 11:51 PM, Andrew Edwards <edwards.ac@gmail.com> wrote:

> I am responsible for this. Request however, that this particular tag be deleted (v2.065-b1) because we're not ready. I am reading Pro Git right now because I made a number of mistakes a few weeks back and decided not to play in the live repo until I get a better grasp of how to use it.

It's very easy to create a local git repository to experiment with. Don't use the public repositories for this.

$ git init .

The above will create a git repository in the current working directory.

--
/Jacob Carlborg