Jump to page: 1 27  
Page
Thread overview
Coming Soon: Stable D Releases!
Jul 16, 2012
Adam Wilson
Jul 16, 2012
Jacob Carlborg
Jul 16, 2012
Adam Wilson
Jul 16, 2012
Roman D. Boiko
Jul 16, 2012
Adam Wilson
Jul 16, 2012
Leandro Lucarella
Jul 16, 2012
Adam Wilson
Jul 21, 2012
Leandro Lucarella
Jul 21, 2012
Adam Wilson
Jul 16, 2012
David Nadlinger
Jul 16, 2012
Adam Wilson
Jul 16, 2012
Marco Leise
Jul 16, 2012
Iain Buclaw
Jul 16, 2012
Marco Leise
Jul 16, 2012
Iain Buclaw
Jul 16, 2012
Adam Wilson
Jul 16, 2012
Iain Buclaw
Jul 16, 2012
Adam Wilson
Jul 21, 2012
Leandro Lucarella
Jul 21, 2012
Adam Wilson
Jul 22, 2012
Leandro Lucarella
Jul 22, 2012
Adam Wilson
Jul 23, 2012
Leandro Lucarella
Jul 23, 2012
Adam Wilson
Jul 24, 2012
Leandro Lucarella
Jul 24, 2012
Adam Wilson
Jul 16, 2012
Adam Wilson
Jul 16, 2012
Iain Buclaw
Jul 16, 2012
Adam Wilson
Jul 16, 2012
Iain Buclaw
Jul 16, 2012
Adam Wilson
Jul 16, 2012
Adam Wilson
Jul 17, 2012
Jacob Carlborg
Jul 17, 2012
Adam Wilson
Jul 17, 2012
Nick Sabalausky
Jul 17, 2012
Jacob Carlborg
Jul 17, 2012
Adam Wilson
Jul 17, 2012
Jacob Carlborg
Jul 21, 2012
Leandro Lucarella
Jul 16, 2012
Caligo
Jul 16, 2012
Adam Wilson
Jul 16, 2012
Caligo
Jul 16, 2012
Adam Wilson
Jul 16, 2012
Jonathan M Davis
Jul 19, 2012
Caligo
Jul 19, 2012
Adam Wilson
Jul 16, 2012
Brad Anderson
Jul 16, 2012
Adam Wilson
Jul 16, 2012
Brad Anderson
Jul 23, 2012
Adam Wilson
Jul 18, 2012
Jesse Phillips
Jul 24, 2012
xenon325
Jul 19, 2012
Jonathan M Davis
Jul 24, 2012
Don Clugston
Jul 24, 2012
Adam Wilson
Jul 25, 2012
Don Clugston
Jul 25, 2012
Jacob Carlborg
Jul 25, 2012
Don Clugston
Jul 25, 2012
Jacob Carlborg
Jul 25, 2012
Leandro Lucarella
Jul 26, 2012
Jacob Carlborg
Jul 25, 2012
Leandro Lucarella
Jul 26, 2012
Jacob Carlborg
Jul 25, 2012
Adam Wilson
Jul 26, 2012
Jacob Carlborg
Jul 26, 2012
Jonathan M Davis
Jul 26, 2012
Jacob Carlborg
July 16, 2012
As a result of the D Versioning thread, we have decided to create a new organization on Github called dlang-stable. This organization will be responsible for maintaining stable releases of DMD, DRuntime, and Phobos.

So what is a stable release?
A stable release is a complete build of DMD, DRuntime, and Phobos that ONLY includes the latest bug-fixes and non-breaking enhancements to existing features. It will not include, new features, breaking enhancements, and any other code that the core development team may be working on.

How often will you release?
The goal of this project is that D is stable at all times. Therefore, our primary method of release will simply be Git-HEAD. However, we will also make available frequent packaged distributions for those who may be unable to use Git-HEAD. While the exact release cadence is to be determined, we expect it to be more frequent then the current release schedule.

What if a bug fix breaks my code?
We will still issue the fix. Fixing the broken behavior is more important than allowing broken code to continue.

How much will the core team be involved?
The idea behind this project is that the core team needs to focus on developing D as fast as possible. However, we will coordinate with them as necessary when it is time to pull in the latest work from the development repositories and as any conflicts arise to between the two codebases.

Is this a fork of D?
No. Our goal is to follow the development of D perfectly. All the code for the stable releases will be received from the primary repositories. We will simply be cherry-picking the commits we want in the release.

Will new features ever be merged from the primary repositories?
Yes. As new features mature, they will be pulled into the stable repos. Precisely when this happens will be a mutual decision by all the developers involved and the community at large.

I have a bug fix ready to go. Who do I send the pull request to?
Please send all pull requests to the primary development repositories (D-Programming-Language). From there we will incorporate your fixes as they are merged into the primary repositories.

I still want to hack on DMD/DRuntme/Phobos. Where do I point my local repositories?
Then nothing will change for you. You can keep all your existing remotes.

Who is developing this project?
For the moment, just myself, with support from Andrei. Although, it would be much appreciated if a few others would step forward as release maintainers to help with the bug fix merges and quality control. If you are interested, I would love to hear from you. You can reply here, send me an email, or contact me on GitHub (handle: LightBender).

OK, I'm sold! When will the first Stable release be ready?
Not until after the official release of 2.060. We feel that it is best to this project from a released build of DMD and from then on maintain the stable versions. While it is technically feasible to go back and start from 2.059, the number of bug fixes since then it would make it a gargantuan task. In addition, this period allows us to build-up the release team, synchronize with the core team, and polish our release procedures. After 2.060 we will begin releasing stable versions of D

Where can I find these stable releases?
The stable releases are located on GitHub at https://github.com/dlang-stable
Once the packaged release become available you can expect to see them on http://www.dlang.org/

If you have any more questions or comments, please reply below and will attempt to answer them to the best of my ability.

Thank you for reading and I hope you enjoy D's new Stable releases!

-- 
Adam Wilson
IRC: LightBender
Project Coordinator
The Horizon Project
http://www.thehorizonproject.org/
July 16, 2012
On 2012-07-16 09:51, Adam Wilson wrote:
> As a result of the D Versioning thread, we have decided to create a new
> organization on Github called dlang-stable. This organization will be
> responsible for maintaining stable releases of DMD, DRuntime, and Phobos.
>
> So what is a stable release?
> A stable release is a complete build of DMD, DRuntime, and Phobos that
> ONLY includes the latest bug-fixes and non-breaking enhancements to
> existing features. It will not include, new features, breaking
> enhancements, and any other code that the core development team may be
> working on.
>
> How often will you release?
> The goal of this project is that D is stable at all times. Therefore,
> our primary method of release will simply be Git-HEAD. However, we will
> also make available frequent packaged distributions for those who may be
> unable to use Git-HEAD. While the exact release cadence is to be
> determined, we expect it to be more frequent then the current release
> schedule.
>
> What if a bug fix breaks my code?
> We will still issue the fix. Fixing the broken behavior is more
> important than allowing broken code to continue.
>
> How much will the core team be involved?
> The idea behind this project is that the core team needs to focus on
> developing D as fast as possible. However, we will coordinate with them
> as necessary when it is time to pull in the latest work from the
> development repositories and as any conflicts arise to between the two
> codebases.
>
> Is this a fork of D?
> No. Our goal is to follow the development of D perfectly. All the code
> for the stable releases will be received from the primary repositories.
> We will simply be cherry-picking the commits we want in the release.
>
> Will new features ever be merged from the primary repositories?
> Yes. As new features mature, they will be pulled into the stable repos.
> Precisely when this happens will be a mutual decision by all the
> developers involved and the community at large.
>
> I have a bug fix ready to go. Who do I send the pull request to?
> Please send all pull requests to the primary development repositories
> (D-Programming-Language). From there we will incorporate your fixes as
> they are merged into the primary repositories.
>
> I still want to hack on DMD/DRuntme/Phobos. Where do I point my local
> repositories?
> Then nothing will change for you. You can keep all your existing remotes.
>
> Who is developing this project?
> For the moment, just myself, with support from Andrei. Although, it
> would be much appreciated if a few others would step forward as release
> maintainers to help with the bug fix merges and quality control. If you
> are interested, I would love to hear from you. You can reply here, send
> me an email, or contact me on GitHub (handle: LightBender).
>
> OK, I'm sold! When will the first Stable release be ready?
> Not until after the official release of 2.060. We feel that it is best
> to this project from a released build of DMD and from then on maintain
> the stable versions. While it is technically feasible to go back and
> start from 2.059, the number of bug fixes since then it would make it a
> gargantuan task. In addition, this period allows us to build-up the
> release team, synchronize with the core team, and polish our release
> procedures. After 2.060 we will begin releasing stable versions of D
>
> Where can I find these stable releases?
> The stable releases are located on GitHub at
> https://github.com/dlang-stable
> Once the packaged release become available you can expect to see them on
> http://www.dlang.org/
>
> If you have any more questions or comments, please reply below and will
> attempt to answer them to the best of my ability.
>
> Thank you for reading and I hope you enjoy D's new Stable releases!
>

Thanks for properly announcing this.

Question: are the going to be release only from "dlang-stable" or from the current repositories as well.

-- 
/Jacob Carlborg


July 16, 2012
On Monday, 16 July 2012 at 07:51:16 UTC, Adam Wilson wrote:
> As a result of the D Versioning thread, we have decided to create a new organization on Github called dlang-stable. This organization will be responsible for maintaining stable releases of DMD, DRuntime, and Phobos.

Congratulations!

I also proposed this idea:

> Also, nobody is preventing any person that considers this to be very important from creating a fork of stable branch and applying bug-fixes there. If this happens to be a very useful option, then it could be accepted as a policy.
>
> So my point of view is that it might be too early to have such policy yet.

http://forum.dlang.org/post/ovtazudocniqfcwzxpky@forum.dlang.org

Also I propose to have a download page with tracking statistics. This would be a nice feedback tool for multiple purposes.
July 16, 2012
Adam Wilson, el 16 de July a las 00:51 me escribiste:
> As a result of the D Versioning thread, we have decided to create a new organization on Github called dlang-stable. This organization will be responsible for maintaining stable releases of DMD, DRuntime, and Phobos.

What will be the version scheme of this dlang-stable compiler? If the git master branch will be the "release", will you increase that version number on each and every commit?

I think it would be a good idea to make real releases, with rc and everything to minimize the chances of introducing (untested) regressions (bare in mind that a lot of patches will not merge cleanly so knowing that the original patch introduced no regressions in the devel compiler doesn't mean it will be the same when merged in the stable one).

That said, I think it was about time D separate devel from stable, so thanks for stepping forward :)

--
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Soy como una mosca, parada en el agua.
Y vos sos un transatlántico, querés nadar a mi lado.
Y me estás ahogando.
July 16, 2012
On Monday, 16 July 2012 at 07:51:16 UTC, Adam Wilson wrote:
> As a result of the D Versioning thread, we have decided to create a new organization on Github called dlang-stable. This organization will be responsible for maintaining stable releases of DMD, DRuntime, and Phobos.

For the time being, I'd rather be explicit about who we is, and that this is not an »official« (whatever this really means) endeavor yet. Don't get me wrong, the idea is indeed nice, and probably it will work out just well. I only doubt that it is a good idea to raise expectations too high at this point…

David
July 16, 2012
Am Mon, 16 Jul 2012 00:51:16 -0700
schrieb "Adam Wilson" <flyboynw@gmail.com>:

For the 2.059 release I waited a while until apparent regressions and oddities in Phobos (deprecation warnings) were fixed in the main repository before updating the dmd package for Gentoo. This was quite a bit of manual work collecting, applying and testing patches from GitHub and the bug tracker.
Will this project be an option for me as a package maintainer? What I need is basically the official dmd zip file (sources, html docs, man pages, bash completion, rdmd binary & co.), but with hotfixes applied at about a week or two after release.
It seems like your work could make this possible and also allow me to issue a new revision of the package in case of, say a security fix that comes a month after release.
Last not least, will we get notified about critical/important fixes in the "stable" branch? 'Cause polling is so old-school ;). RSS, news group, email, phone call, anything will do. It looks like GitHub has a commit-RSS-feed, but it would be very noisy on most repositories with messages like "forgot this in last check-in" or "deleted unused file/code", and not every commit warrants a new package.

As it shows, the beta phase doesn't always catch all regressions in people's code, so I encourage you to do this project and eventually it will be used by GDC and other major from-source projects. By the way: Should this also later become the base for the official zip file download? IIRC Walter wanted to keep track of the DMD downloads from the main web site (no redistribution) and hotfixed versions of D could become increasingly popular.

-- 
Marco

July 16, 2012
On 16 July 2012 14:00, Marco Leise <Marco.Leise@gmx.de> wrote:
> Am Mon, 16 Jul 2012 00:51:16 -0700
> schrieb "Adam Wilson" <flyboynw@gmail.com>:
>
> As it shows, the beta phase doesn't always catch all regressions in people's code, so I encourage you to do this project and eventually it will be used by GDC and other major from-source projects. By the way: Should this also later become the base for the official zip file download? IIRC Walter wanted to keep track of the DMD downloads from the main web site (no redistribution) and hotfixed versions of D could become increasingly popular.
>
> --
> Marco
>

And what benefits would GDC get from opting to use this rather than the normal releases?


-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';
July 16, 2012
Am Mon, 16 Jul 2012 17:21:39 +0100
schrieb Iain Buclaw <ibuclaw@ubuntu.com>:

> On 16 July 2012 14:00, Marco Leise <Marco.Leise@gmx.de> wrote:
> > Am Mon, 16 Jul 2012 00:51:16 -0700
> > schrieb "Adam Wilson" <flyboynw@gmail.com>:
> >
> > As it shows, the beta phase doesn't always catch all regressions in people's code, so I encourage you to do this project and eventually it will be used by GDC and other major from-source projects. By the way: Should this also later become the base for the official zip file download? IIRC Walter wanted to keep track of the DMD downloads from the main web site (no redistribution) and hotfixed versions of D could become increasingly popular.
> >
> > --
> > Marco
> >
> 
> And what benefits would GDC get from opting to use this rather than the normal releases?

What he said, [regression] fixes that didn't make it into the initial release. I don't know about GDC's 'patch level', but for 2.059 I applied patches for the following issues after release, to have it feel as solid as good old 2.058:
- issue-7907
- issue-7911
- issue-7922
- outOfMemoryError-undeprecation
- std-path-sep-deprecation

In case crypto algorithms become part of Phobos, some patches may improve security as well. Didn't you say you work only with the GitHub release tags for stability?

-- 
Marco

July 16, 2012
On 7/16/12 3:51 AM, Adam Wilson wrote:
> As a result of the D Versioning thread, we have decided to create a new
> organization on Github called dlang-stable. This organization will be
> responsible for maintaining stable releases of DMD, DRuntime, and Phobos.
[snip]
> Thank you for reading and I hope you enjoy D's new Stable releases!

This is a wonderful initiative that I hope will catch on.

Walter and I are fully behind this experiment. We will make/accept changes to the download pages to take into account this new branch.

The main threat I see is bugfixes that depend on code previously introduced with now features. I'm not sure how frequent that situation is.

Finally, one suggestion: I suggest you relentlessly work to automate the process to the point where you issue e.g. the command

./merge 534d44c979 70dcb958ea

and the script merges in the two specified commits, builds everything, runs the test suite, runs the Phobos unittests, and if all worked, builds packages and uploads them making them available right away.

That way the team members (busy professionals with many other responsibilities) know that once the collective decision to merge a commit has been taken, there's virtually no overhead to deploying the decision.

I'm a huge fan of automation and I believe we've made progress introducing it in dmd's process, but not as much as we could and should.


Good luck!

Andrei

July 16, 2012
On Mon, 16 Jul 2012 06:00:02 -0700, Marco Leise <Marco.Leise@gmx.de> wrote:

> Am Mon, 16 Jul 2012 00:51:16 -0700
> schrieb "Adam Wilson" <flyboynw@gmail.com>:
>
> For the 2.059 release I waited a while until apparent regressions and oddities in Phobos (deprecation warnings) were fixed in the main repository before updating the dmd package for Gentoo. This was quite a bit of manual work collecting, applying and testing patches from GitHub and the bug tracker.
> Will this project be an option for me as a package maintainer? What I need is basically the official dmd zip file (sources, html docs, man pages, bash completion, rdmd binary & co.), but with hotfixes applied at about a week or two after release.
> It seems like your work could make this possible and also allow me to issue a new revision of the package in case of, say a security fix that comes a month after release.
> Last not least, will we get notified about critical/important fixes in the "stable" branch? 'Cause polling is so old-school ;). RSS, news group, email, phone call, anything will do. It looks like GitHub has a commit-RSS-feed, but it would be very noisy on most repositories with messages like "forgot this in last check-in" or "deleted unused file/code", and not every commit warrants a new package.
>
> As it shows, the beta phase doesn't always catch all regressions in people's code, so I encourage you to do this project and eventually it will be used by GDC and other major from-source projects. By the way: Should this also later become the base for the official zip file download? IIRC Walter wanted to keep track of the DMD downloads from the main web site (no redistribution) and hotfixed versions of D could become increasingly popular.

For the first few packaged releases we aren't going to call this thing official. It's just an experiment for the moment. But if it is popular and the stability promises we are attempting to make actually hold up, (i.e. this experiment actually works) there are plans to revisit this question with an eye towards making it official.

However, since the commit list will be bug-fixes and non-breaking enhancements only, you may find it easier to work off this list than HEAD.

If you have any more questions on this subject please email Andrei. (You can find his email at http://erdani.com/index.php/contact/) He is the liaison between this project and the core team.

-- 
Adam Wilson
IRC: LightBender
Project Coordinator
The Horizon Project
http://www.thehorizonproject.org/
« First   ‹ Prev
1 2 3 4 5 6 7