[postgis-devel] Google's issue's tracker

[Obe, Regina]

Can we add status codes?

Ready for Test 

sounds much more clear

and I like 'Fixed' being reserved for done done ready to ship. I mean
when you list release notes you don't write

Verified
-----------
BUG 123: PostgreSQL Crashes when PostGIS is loaded in 8.4

You put

Fixed
-------
Bug 123: PostgreSQL Crashes when PostGIS is loaded in 8.4


-----Original Message-----
From: postgis-devel-bounces at postgis.refractions.net
[mailto:postgis-devel-bounces at postgis.refractions.net] On Behalf Of strk
Sent: Tuesday, December 02, 2008 4:55 PM
To: PostGIS Development Discussion
Subject: Re: [postgis-devel] Google's issue's tracker

On Tue, Dec 02, 2008 at 04:50:29PM -0500, Obe, Regina wrote:
> Ah yes you are right?  I guess I should have read the verbiage since
the
> term verified I found confusing.
> 
> Honestly though Fixed seems more final to me than Verified.  I always
> get confused between
> 
> Verified -  does that mean the bug is reproducible or the fix is
> verified to work.  I always use Verified in context of issue is
> reproducible, but we haven't decided if we care to fix it.

My 2c: we have a 'Ready for test' status in savannah for Gnash which
we use when a fix was committed and waiting for QA.
We use 'Fixed' as final step.

--strk;
_______________________________________________
postgis-devel mailing list
postgis-devel at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-devel
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.