January 03, 2010
On Sun, 03 Jan 2010 17:47:44 -0300, Leandro Lucarella wrote:

> Moritz Warning, el  3 de enero a las 15:25 me escribiste:
>> On Sun, 03 Jan 2010 10:22:02 -0500, Eldar Insafutdinov wrote:
>> 
>> > Eldar Insafutdinov Wrote:
>> > 
>> >> Walter Bright Wrote:
>> >> 
>> >> > Fixes the Tango build breaks.
>> >> > 
>> >> > 
>> >> > http://www.digitalmars.com/d/1.0/changelog.html http://ftp.digitalmars.com/dmd.1.055.zip
>> >> > 
>> >> > 
>> >> > http://www.digitalmars.com/d/2.0/changelog.html http://ftp.digitalmars.com/dmd.2.039.zip
>> >> 
>> >> And thank's a lot for this release. I was finally able to compile QtD almost without patching dmd (only patch from#3600). Getting rid of the forward reference bugs is a big milestone. We just have to make sure that there won't be regressions. Somebody mentioned a while ago about a service, that would build big D projects with the newest compiler version to avoid regressions. This idea I believe is worth discussing.
>> > 
>> > I was wrong, there is still a forward reference bug in dmd, which I cannot reduce to a testcase, considering the size of the library.
>> 
>> Have you tried http://d.puremagic.com/issues/show_bug.cgi?id=102 ?
> 
> WoW! I wonder why that patch is not already in DMD, since Don said that it passes the DMD test suite, and not only fixes 102, it also fixes 461, 2386, 2654 and 2666, not counting a couple of already fixed bugs. I think Rainer Schuetze deserves a lot of credit, I think his practically at the same scale as Don fixing important bugs, I hope Walter realizes that and had him the DMD test suite as well (or even better, releases the test suite ;).
> 
> Thanks for the quick release fixing the regressions!

Yes, big kudos to Rainer as well!
January 03, 2010
Eldar Insafutdinov wrote:
> This patch is no longer relevant. Here is the patch
> http://pastebin.com/m1bed188d that fixes compiling QtD with the
> current dmd (I also have to apply a patch from #3600). However I
> cannot really file a bug as I cannot reduce it to a testcase of a
> reasonable size. Any chance that this patch can be applied? Shall I
> submit it to the bugzilla then?

You should still submit it to bugzilla, because often someone else is able to cut them down to size.
January 03, 2010
digited wrote:
> Walter Bright Wrote:
> 
>> Fixes the Tango build breaks.
> 
> With RC's, you'll never need this.

I put out a beta to the people who have asked to be on the beta announcement list, and nobody (other than Don) gave any feedback on it. If you want to be on the beta list, please email me.

Or on second thought, perhaps I'll ask Brad to set up a beta mailing list.
January 03, 2010
Walter Bright wrote:
> digited wrote:
>> Walter Bright Wrote:
>>
>>> Fixes the Tango build breaks.
>>
>> With RC's, you'll never need this.
> 
> I put out a beta to the people who have asked to be on the beta announcement list, and nobody (other than Don) gave any feedback on it. If you want to be on the beta list, please email me.
> 
> Or on second thought, perhaps I'll ask Brad to set up a beta mailing list.

Why not just post them publicly on the announce newsgroup?

January 03, 2010
Hello Walter,

> digited wrote:
> 
>> Walter Bright Wrote:
>> 
>>> Fixes the Tango build breaks.
>>> 
>> With RC's, you'll never need this.
>> 
> I put out a beta to the people who have asked to be on the beta
> announcement list, and nobody (other than Don) gave any feedback on
> it. If you want to be on the beta list, please email me.
> 
> Or on second thought, perhaps I'll ask Brad to set up a beta mailing
> list.
> 

If you do, please add a link to it to the D front page. (I might be interested later but not now)


January 03, 2010
Brad Roberts Wrote:

> Walter Bright wrote:
> > digited wrote:
> >> Walter Bright Wrote:
> >>
> >>> Fixes the Tango build breaks.
> >>
> >> With RC's, you'll never need this.
> > 
> > I put out a beta to the people who have asked to be on the beta announcement list, and nobody (other than Don) gave any feedback on it. If you want to be on the beta list, please email me.
> > 
> > Or on second thought, perhaps I'll ask Brad to set up a beta mailing list.
> 
> Why not just post them publicly on the announce newsgroup?
> 

Agree.

Please, Walter, post betas in Announce newsgroup (here). I'll test Tango trunk, miniD, xf and my code at least on Windows and Mac 10.5 at work (i'm using 64-bit linux distro, so - ldc there)

Giving beta testers a couple of days before releasing final version will be perfect.
January 04, 2010
Brad Roberts wrote:
> Why not just post them publicly on the announce newsgroup?

I'd rather it be a self-selected list of people who decide they need to be notified, rather than expecting them to constantly check the announce n.g. I'd also rather not confuse releases with betas, I doubt many would be interested in betas other than library maintainers.
January 04, 2010
On Sun, 03 Jan 2010 16:52:20 -0800, Walter Bright wrote:

> Brad Roberts wrote:
>> Why not just post them publicly on the announce newsgroup?
> 
> I'd rather it be a self-selected list of people who decide they need to be notified, rather than expecting them to constantly check the announce n.g. I'd also rather not confuse releases with betas, I doubt many would be interested in betas other than library maintainers.

Please put me on the list.
January 04, 2010
Moritz Warning wrote:
> On Sun, 03 Jan 2010 16:52:20 -0800, Walter Bright wrote:
> 
>> Brad Roberts wrote:
>>> Why not just post them publicly on the announce newsgroup?
>> I'd rather it be a self-selected list of people who decide they need to
>> be notified, rather than expecting them to constantly check the announce
>> n.g. I'd also rather not confuse releases with betas, I doubt many would
>> be interested in betas other than library maintainers.
> 
> Please put me on the list.

When Brad creates it, I (or Brad) will post an announcement here, and you'll be able to sign up for it.
January 04, 2010
Walter Bright, el  3 de enero a las 16:52 me escribiste:
> Brad Roberts wrote:
> >Why not just post them publicly on the announce newsgroup?
> 
> I'd rather it be a self-selected list of people who decide they need to be notified, rather than expecting them to constantly check the announce n.g. I'd also rather not confuse releases with betas, I doubt many would be interested in betas other than library maintainers.

Why don't you do both? I would like to know when DMD is about to be released and I don't maintain any libraries (I'm trying to merge latest DMD FE to LDC though). I don't want to receive any personal e-mails, the announcement NG is perfect for me.

Please, please, do both if you think is very important for some other people to be explicitly notified via personal e-mails.

Thanks.

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Lo último que hay que pensar es que se desalinea la memoria
Hay que priorizar como causa la idiotez propia
Ya lo tengo asumido
	-- Pablete, filósofo contemporáneo desconocido