Not sure how, or when to push for this, but I've some changes for std.csv

https://github.com/D-Programming-Language/phobos/pull/389

which would be good to have merged. Johnathon's given it a once over already and has been passing the auto tester for some time... Whoh, good to see such a green list in there that aren't all old!

I'd like to add that last night I finally finished resolving all the compiler seg faults. While they weren't marked critical, I regard them as particularly important because they give a bad impression. If there are any remaining that I missed, please upgrade their importance and let me know about them.

Who sets the priority levels in bugzilla? If compiler segfaults get top priority, shouldn't they have the highest priority in bugzilla?

Can't priority levels get renamed/added in bugzilla? Would doing that help add clarity into when bugs will get fixed?

Sent from my iPhone

On Jan 29, 2012, at 1:52 PM, Walter Bright <walter at digitalmars.com> wrote:

> I'd like to add that last night I finally finished resolving all the compiler seg faults. While they weren't marked critical, I regard them as particularly important because they give a bad impression. If there are any remaining that I missed, please upgrade their importance and let me know about them.
> _______________________________________________
> dmd-beta mailing list
> dmd-beta at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta

On 1/29/2012 11:22 AM, Jason House wrote:
> Who sets the priority levels in bugzilla?

Anyone can set or change the priority level. Setting too much of a store by these, however, leads to raging bikeshed wars and pointless hard feelings, which I've been in and wish to avoid.

On 1/29/2012 8:10 AM, Andrei Alexandrescu wrote:
> We started at 25 regressions, 18 blockers, 45 critical, and 158 major bugs out of 2751 open issues.
> 
> Now we have 2541 issues, of which 29 regressions, 15 blockers, and 49 criticals, and 147 majors.
> 
> Great job on the bug scrubbing and picking the low-hanging fruit (210!) but unfortunately we haven't significantly reduced the age of the oldest bug, and we have a net increase of regressions and criticals. I'd say we should make significant progress on these three items before considering a beta.
> 
> 
> Andrei

I'm fine with a beta at any point in time.  That said, I strongly agree with Andrei in terms of considering a release. I'd be happy enough if just the regressions were addressed.  There's 7 that have been filed since 1/1/2012, most if not all of which are very recent regressions, not just newly discovered old regressions.

On Sunday, January 29, 2012 10:24:41 Jesse Phillips wrote:
> Not sure how, or when to push for this, but I've some changes for std.csv
> 
> https://github.com/D-Programming-Language/phobos/pull/389
> 
> which would be good to have merged. Johnathon's given it a once over already and has been passing the auto tester for some time... Whoh, good to see such a green list in there that aren't all old!

I'll look at it again. I hadn't noticed that you'd updated it. Unfortunately, github doesn't send e-mails when you submit code changes to a pull request, just when comments are added. So, in the future, you should post a comment when you've updated a pull request.

- jonathan M Davis

Walter Bright, el 29 de enero a las 11:38 me escribiste:
> On 1/29/2012 11:22 AM, Jason House wrote:
> >Who sets the priority levels in bugzilla?
> 
> Anyone can set or change the priority level. Setting too much of a store by these, however, leads to raging bikeshed wars and pointless hard feelings, which I've been in and wish to avoid.

"Importance" has 3 fields: Priority, Severity and Votes. Severity is inherent to the issue. Votes is the "priority" defined by the user, and Priority should be defined by the developers[1].

It's true that everybody can change the Priority, but if it's possible
to put some message there (without having to click on the help), I think
people might leave it alone (Wikis do work, right?). Also, as
I suggested in the devel list[2], it might help to rename the priorities
to something more readable, like:
P1 -> Immediate (*)
P2 -> Next release
P3 -> Eventually
P4 -> Future
P5 -> Informational

[1] http://d.puremagic.com/issues/page.cgi?id=fields.html#importance [2] http://permalink.gmane.org/gmane.comp.lang.d.dmd.devel/3211

-- 
Leandro Lucarella (AKA luca)                     http://llucax.com.ar/
----------------------------------------------------------------------
GPG Key: 5F5A8D05 (F8CD F9A7 BF00 5431 4145  104C 949E BFB6 5F5A 8D05)
----------------------------------------------------------------------
Parece McGuevara's o CheDonald's

Sorry I haven't been active lately, My family and I have had the stomach bug for the last week :(

But if you could include those snn.lib changes that you pulled for pipes to work on Windows in the next release, I'd really appreciate it!

-Steve



----- Original Message -----
> From: Walter Bright <walter at digitalmars.com>
> To: Discuss the dmd beta releases for D <dmd-beta at puremagic.com>
> Cc:
> Sent: Sunday, January 29, 2012 4:42 AM
> Subject: [dmd-beta] Time for a beta?
> 
> 
> _______________________________________________
> dmd-beta mailing list
> dmd-beta at puremagic.com
> http://lists.puremagic.com/mailman/listinfo/dmd-beta
> 

Will do.

On 2/3/2012 7:10 AM, Steve Schveighoffer wrote:
> Sorry I haven't been active lately, My family and I have had the stomach bug for the last week :(
>
> But if you could include those snn.lib changes that you pulled for pipes to work on Windows in the next release, I'd really appreciate it!

If the current library-based AA implementation stays in for this release, there is another regressions that breaks Thrift (very similar to the one that you added the druntime workaround for, Walter:

http://d.puremagic.com/issues/show_bug.cgi?id=7451

David