From the preceding discussion, it is clear that the community desires
both a swift release cycle and more stability. No one solution will
appease the entire community. Therefore, I will take the middle ground.
The way forward will be as follows:
Official releases will occur on an 8 week basis
On Tuesday, 3 December 2013 at 14:26:07 UTC, Andrew Edwards wrote:
From the preceding discussion, it is clear that the community
desires both a swift release cycle and more stability. No one
solution will appease the entire community. Therefore, I will
take the middle ground. The way forward wi
On Tuesday, 3 December 2013 at 15:36:46 UTC, eles wrote:
Should DUB be added, too?
Lets wait a bit until it stabilizes a bit before putting it into
official package. At future least SDL addition comes to my mind.
On Tuesday, 3 December 2013 at 14:26:07 UTC, Andrew Edwards wrote:
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 z
In general this sounds great. However:
On Tuesday, 3 December 2013 at 14:26:07 UTC, Andrew Edwards wrote:
Betas will be released four weeks after an official release.
Does this mean that a new release branch will be created at that
point? I think it makes sense.
Once a release candidate is
On Tuesday, 3 December 2013 at 16:04:32 UTC, Dicebot wrote:
On Tuesday, 3 December 2013 at 14:26:07 UTC, Andrew Edwards
wrote:
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 a
On Tuesday, 3 December 2013 at 14:26:07 UTC, Andrew Edwards wrote:
[snip]
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.
Please use win
On Tuesday, 3 December 2013 at 14:26:07 UTC, Andrew Edwards wrote:
Betas will be released four weeks after an official release.
The intent is to afford a thorough review of all features
introduced since the last official release and allot ample time
to remedy any resulting regressions.
Rele
On Tuesday, 3 December 2013 at 20:51:27 UTC, Martin Nowak wrote:
On Tuesday, 3 December 2013 at 16:04:32 UTC, Dicebot wrote:
Wasn't Nick working on automation of that part?
https://github.com/D-Programming-Language/installer/pull/24
On Tuesday, 3 December 2013 at 16:04:32 UTC, Dicebot wrote:
Wasn't Nick working on automation of that part?
It isn't automatable because the zip is assembled from different
platforms.
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 need
On Tuesday, 3 December 2013 at 21:23:49 UTC, Martin Nowak wrote:
The tools strictly related to D are, dman, ddmangle and rdmd.
And link on windows.
Thanks for doing this Andrew.
On 2013-12-03 21:51, Martin Nowak wrote:
It isn't automatable because the zip is assembled from different platforms.
Why can't that be automatable? We do have the servers running the tests.
The idea is that they should build them.
--
/Jacob Carlborg
On 12/3/13, 12:21 PM, tn wrote:> In general this sounds great. However:
>
> On Tuesday, 3 December 2013 at 14:26:07 UTC, Andrew Edwards wrote:
>> Betas will be released four weeks after an official release.
>
> Does this mean that a new release branch will be created at that point?
> I think it ma
On 12/3/13, 2:08 PM, Brad Anderson wrote:
On Tuesday, 3 December 2013 at 14:26:07 UTC, Andrew Edwards wrote:
[snip]
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 C
On 12/3/13, 3:32 PM, Nick wrote:
On Tuesday, 3 December 2013 at 14:26:07 UTC, Andrew Edwards wrote:
Betas will be released four weeks after an official release. The
intent is to afford a thorough review of all features introduced since
the last official release and allot ample time to remedy
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 t
On Wednesday, 4 December 2013 at 02:15:23 UTC, Andrew Edwards
wrote:
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 incrementall
On 12/3/13, 9:26 PM, Jesse Phillips wrote:
On Wednesday, 4 December 2013 at 02:15:23 UTC, Andrew Edwards wrote:
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 +
c
On 12/3/13, 9:15 PM, Andrew Edwards wrote:
On 12/3/13, 4:23 PM, Martin Nowak wrote:
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 rele
On Wednesday, 4 December 2013 at 04:29:19 UTC, Andrew Edwards
wrote:
On 12/3/13, 9:15 PM, Andrew Edwards wrote:
On 12/3/13, 4:23 PM, Martin Nowak wrote:
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/i
On 12/3/13, 11:29 PM, Andrew Edwards wrote:
I created the v2.065-b1 tag and verified that it actually exists. If I
use 2.065 as indicated in the instructions for making betas, it results
in the exact same error.
Any thoughts?
OK the problem was that I didn't finish branching all the componen
On 12/3/13, 11:38 PM, Craig Dillabaugh wrote:
On Wednesday, 4 December 2013 at 04:29:19 UTC, Andrew Edwards wrote:
On 12/3/13, 9:15 PM, Andrew Edwards wrote:
On 12/3/13, 4:23 PM, Martin Nowak wrote:
Only Walter knows how to build the zip.
Nick wrote a build script the produces a similar zip fi
On 2013-12-03 15:25, Andrew Edwards wrote:
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 rel
On 2013-12-04 03:26, Jesse Phillips wrote:
Also, at some point Walter said in a random forum post that he wanted
this next release to be bug fixes only and rather quick... You're plan
and Walter's don't seem to match exactly.
Walter has also said it's up to the release manager (build master) t
On 2013-12-03 20:08, Brad Anderson wrote:
Historically, Walter has created the release zips (just using the
makefile, I believe). As far as I know, work hasn't begun on getting the
autotester to roll releases.
I doubt he has a completely automated process of doing it. It has failed
too many t
On 2013-12-04 02:30, Andrew Edwards wrote:
Ok, got you. One question, does dinstaller.nsi work on linux/osx? If not
I will need your assistance to prepare the package until such time as I
can obtain an image for VirtualBox.
Everything should be built using the autotester.
Which is basically
On 2013-12-04 05:29, Andrew Edwards wrote:
Tried it but came across the following errors:
andrews-mini:osx-release ace$ ~/create_dmd_release v2.065-b1
--extras=$HOME/localextras-osx --archive-zip --archive-7z
Cloning: g...@github.com:D-Programming-Language/dmd.git
The authenticity of host 'g
On 2013-12-04 06:25, Andrew Edwards wrote:
My next question is whether or not this can be used on my platform (OSX)
to build binaries for the other platforms (Linux, Windows, FreeBSD) or
do I have to be on those platforms to do so? If that is the case, then I
will need assistance getting for Win
On 12/4/13, 3:09 AM, Jacob Carlborg wrote:
On 2013-12-03 15:25, Andrew Edwards wrote:
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
On 12/4/13, 3:21 AM, Jacob Carlborg wrote:
On 2013-12-04 05:29, Andrew Edwards wrote:
Couldn't do git protocol, falling back to 'https://'...
You need to have your SSH key uploaded to github. See:
https://help.github.com/articles/generating-ssh-keys
I did this but it is not working for m
On 2013-12-04 09:23, Andrew Edwards wrote:
Working on that.
* Instruct the autotester to build the compiler, libraries, installers
and all tools for each platform based on the newly created tag
Will need access from Brad Roberts. Have yet to receive any kind of
response to date.
* Assemble
04-Dec-2013 12:23, Andrew Edwards пишет:
On 12/4/13, 3:09 AM, Jacob Carlborg wrote:
On 2013-12-03 15:25, Andrew Edwards wrote:
[snip]
* Generate the changelog from bugzilla. The overview/general information
should already be present in the changelog at this time
Will need help on this one.
On 12/4/13 12:18 AM, Jacob Carlborg wrote:
On 2013-12-03 20:08, Brad Anderson wrote:
Historically, Walter has created the release zips (just using the
makefile, I believe). As far as I know, work hasn't begun on getting the
autotester to roll releases.
I doubt he has a completely automated pr
On 2013-12-04 20:28, Dmitry Olshansky wrote:
There is a tool for that. Nothing stellar but it does the job:
https://github.com/D-Programming-Language/tools/blob/master/changed.d
Great.
Also be sure to contact Andrej Mitrovic he is a mastermind behind nice
changelogs we had for the last coupl
On 2013-12-04 20:52, Brad Roberts wrote:
I'm not sure this is really a good goal any more. The overlap between
testing and releasing isn't as big as I originally thought. Add to that
that the very definition of what a release is is in question. The only
overlap that really exists is that ther
On Tuesday, 3 December 2013 at 22:24:45 UTC, Jacob Carlborg wrote:
Why can't that be automatable? We do have the servers running
the tests. The idea is that they should build them.
Conflating binaries for multiple platforms is the problem here.
On Thursday, 5 December 2013 at 07:58:10 UTC, Jacob Carlborg
wrote:
* Not a single person need to have all different platforms to
create a release
We'll need to move to building linux distribution specific build
to fix issues with shared library dependencies, so it's even more
platforms.
*
On 12/4/2013 12:18 AM, Jacob Carlborg wrote:
I doubt he has a completely automated process of doing it. It has failed too
many times.
The cause of those failures is that the product changes from release to release.
There are new files to be added, old ones to be removed, directories change,
t
On 2013-12-05 09:02, Martin Nowak wrote:
Conflating binaries for multiple platforms is the problem here.
Just send them to a single machine which assembles the cross-platform zip.
--
/Jacob Carlborg
On 2013-12-05 09:09, Martin Nowak wrote:
We'll need to move to building linux distribution specific build to fix
issues with shared library dependencies, so it's even more platforms.
Yes. Can we manage with Debian and Red Hat based system? Do we need
others as well?
I think a good solution
On 2013-12-05 09:32, Walter Bright wrote:
The cause of those failures is that the product changes from release to
release. There are new files to be added, old ones to be removed,
directories change, targets change, everything is in flux.
What about all the times when the git tag and the relea
On 12/5/13, 3:09 AM, Martin Nowak wrote:
On Thursday, 5 December 2013 at 07:58:10 UTC, Jacob Carlborg wrote:
* Not a single person need to have all different platforms to create a
release
We'll need to move to building linux distribution specific build to fix
issues with shared library depende
On 2013-12-06 17:45, Andrew Edwards wrote:
I crashed my system so I had to start over with a fresh
installation/configuration. The following images are installed within
VirtualBox:
OS X 10.9
Ubuntu 12.04
Fedora 19
FreeBSD 9.2
Windows 7 [1]
All images are 64 bits and al
On 2013-12-06 17:45, Andrew Edwards wrote:
I crashed my system so I had to start over with a fresh
installation/configuration. The following images are installed within
VirtualBox:
OS X 10.9
Ubuntu 12.04
Fedora 19
FreeBSD 9.2
Windows 7 [1]
All images are 64 bits and al
On 2013-12-06 18:15, Dicebot wrote:
Gentoo does not have binary packages.
Is Gentoo needed to create package, although it isn't binary packages?
--
/Jacob Carlborg
On Friday, 6 December 2013 at 17:10:58 UTC, Jacob Carlborg wrote:
Gentoo and Arch Linux perhaps? I don't remember if Arch uses
its own package manager or not. Dicebot can answer this.
Gentoo does not have binary packages. Arch Linux has own package
manager / package format but I'd prefer it to
On Friday, 6 December 2013 at 17:09:34 UTC, Jacob Carlborg wrote:
On 2013-12-06 17:45, Andrew Edwards wrote:
I crashed my system so I had to start over with a fresh
installation/configuration. The following images are installed
within
VirtualBox:
OS X 10.9
Ubuntu 12.04
Fedora 19
I see no reason in try to provide packages for a platforms that
are already maintained by people that actually use those
platforms. Such attempts are doomed to be inferior to native
ones. It makes sense to take over support if it was abandoned for
that specific platform but not before.
06-Dec-2013 20:45, Andrew Edwards пишет:
On 12/5/13, 3:09 AM, Martin Nowak wrote:
[snip]
[1] There is not yet a windows image installed as I do not have an
installation CD.
Well, there is a temporary option to get an 90-day evaluation version of
enterprise edition ISO.
Here is 8.1, building
On 2013-12-06 18:29, Dicebot wrote:
I see no reason in try to provide packages for a platforms that are
already maintained by people that actually use those platforms. Such
attempts are doomed to be inferior to native ones. It makes sense to
take over support if it was abandoned for that specific
51 matches
Mail list logo
