releases

[Iain Buclaw via D.gnu]

On 6 October 2015 at 17:23, Johannes Pfau via D.gnu <d.gnu at puremagic.com>
wrote:

> Am Tue, 06 Oct 2015 12:52:23 +0000
> schrieb John Colvin <john.loughran.colvin at gmail.com>:
>
> > http://gdcproject.org/downloads are all with gcc 5.2
> >
> > https://github.com/D-Programming-GDC/GDC/releases/tag/v2.066.1_gcc5
> > is with gcc 5.1, as is the gdc-5 branch
> >
>
> The gcc.version file is the version tested by the CI systems. This is
> important for the master branch which uses gcc snapshots and
> older or newer snapshots often do not work.
>
> For the release branches the version indicated in gcc.version is less
> important. It's used by the autotester, but GCC does not break
> compatibility in minor releases so you should always use the latest
> release. 5.2 in this case.
>
> OT: I just updated all gcc.version files. I'll push these updates once
> the autotester passes.
>
> > Is there a reason for this? If I want to package the latest
> > "stable" gdc (must be from source), what should I work from?
>
> => latest GCC 5 (5.2 right now) and gdc-5 branch.
>
> We should probably add tags whenever we release updated binaries. But I
> don't want to call these v2.066.1_gcc5.2 as you can use all gdc-5
> commits with all GCC 5 versions. Probably v2.066.1_gcc5_r2 instead or
> something like that.
>

I hope you are not backporting latest master to those branches too. ;-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/d.gnu/attachments/20151006/c784d3e4/attachment.html>