I'm game.

On 8/31/2011 9:37 PM, Brad Roberts wrote:
>
> Well, there seemed to be some limited consensus 2 weeks ago that it might be time for a beta, then the period of extended brokenness.  Now that we're back in a happy state, shall we?
>
> Anyone have a 'really must be fixed before the next release' list?
>
> As always, mine consists of the open regression bugs, but since I'm not personally investing in fixing any of them, it's poor form to gripe too much about them.
>

> Anyone have a 'really must be fixed before the next release' list?

Is rdmd working correctly?
There's still this:
https://github.com/D-Programming-Language/tools/pull/10

And I guess adding ddemangle also can't hurt: https://github.com/D-Programming-Language/tools/pull/2

Last time we got a bunch of regressions reported after the beta was out, so probably the sooner the better.

On Thu, Sep 1, 2011 at 2:37 PM, Brad Roberts <braddr at puremagic.com> wrote:
> On 8/13/2011 12:40 PM, Walter Bright wrote:
>>
>> _______________________________________________
>> dmd-beta mailing list
>> dmd-beta at puremagic.com
>> http://lists.puremagic.com/mailman/listinfo/dmd-beta
>
> Well, there seemed to be some limited consensus 2 weeks ago that it might be time for a beta, then the period of extended brokenness. ?Now that we're back in a happy state, shall we?
>
> Anyone have a 'really must be fixed before the next release' list?
>
> As always, mine consists of the open regression bugs, but since I'm not personally investing in fixing any of them, it's poor form to gripe too much about them.
>
> _______________________________________________
> dmd-beta mailing list
> dmd-beta at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta
>

Has anyone seen this one?

http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=143686 http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=143687

Might be nothing, but if it's legit, it should be fixed before releasing a beta.

-Steve



----- Original Message -----
> From: Daniel Murphy <yebblies at gmail.com>
> To: Discuss the dmd beta releases for D <dmd-beta at puremagic.com>
> Cc:
> Sent: Thursday, September 1, 2011 8:39 AM
> Subject: Re: [dmd-beta] Time for a new beta?
> 
> Last time we got a bunch of regressions reported after the beta was out, so probably the sooner the better.

Sigh, the news groups suck as a bug reporting mechanism.

On Sep 1, 2011, at 11:20 AM, Steve Schveighoffer <schveiguy at yahoo.com> wrote:

> Has anyone seen this one?
> 
> http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=143686 http://www.digitalmars.com/webnews/newsgroups.php?art_group=digitalmars.D&article_id=143687
> 
> Might be nothing, but if it's legit, it should be fixed before releasing a beta.
> 
> -Steve
> 
> 
> 
> ----- Original Message -----
>> From: Daniel Murphy <yebblies at gmail.com>
>> To: Discuss the dmd beta releases for D <dmd-beta at puremagic.com>
>> Cc:
>> Sent: Thursday, September 1, 2011 8:39 AM
>> Subject: Re: [dmd-beta] Time for a new beta?
>> 
>> Last time we got a bunch of regressions reported after the beta was out, so probably the sooner the better.
> _______________________________________________
> dmd-beta mailing list
> dmd-beta at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta

Right, but then Walter says don't use bugzilla for code that hasn't been released yet.

> Right, but then Walter says don't use bugzilla for code that hasn't been released yet.

Oh, I didn't know that. I'd been occasionally doing that. What's the proper place then? (Not the phobos list I hope, I *hate* mailing lists.)

On Thursday, September 01, 2011 13:33 Nick Sabalausky wrote:
> > Right, but then Walter says don't use bugzilla for code that hasn't been released yet.
> 
> Oh, I didn't know that. I'd been occasionally doing that. What's the proper place then? (Not the phobos list I hope, I *hate* mailing lists.)

I don't think that there _is_ a proper place. Generally, it just gets brought up on one of the lists or someone files it in bugzilla anyway.

- Jonathan M Davis

Quote:

On 8/30/11, Walter Bright <newshound2 at digitalmars.com> wrote:
> On 8/29/2011 5:11 PM, Walter Bright wrote:
>> On 8/29/2011 4:52 PM, bearophile wrote:
>>> alias NotNull!(Foo*) NFooP;
>>>
>>> void bar(NFooP foop) { // Error: variable test2.bar.foop initializer
>>> required
>>> for type NotNull!(Foo*)
>>
>> Looks like you found a bug. I'll take care of it.
>
> Fixed. Keep 'em coming!

So I just replied there after trying out the notnull stuff.

On Thu, 1 Sep 2011, Jonathan M Davis wrote:

> On Thursday, September 01, 2011 13:33 Nick Sabalausky wrote:
> > > Right, but then Walter says don't use bugzilla for code that hasn't been released yet.
> > 
> > Oh, I didn't know that. I'd been occasionally doing that. What's the proper place then? (Not the phobos list I hope, I *hate* mailing lists.)
> 
> I don't think that there _is_ a proper place. Generally, it just gets brought up on one of the lists or someone files it in bugzilla anyway.
> 
> - Jonathan M Davis

Walter is wrong.  They should go in bugzilla.  The only time it might not be worth it is if the fix is done immediately.  But that's not the norm, so, better to have the issue in a trackable location, aka bugzilla.

My 2 cents,
Brad