Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Zope: Coders

July Bug Day Roundup

 

 

Zope coders RSS feed   Index | Next | Previous | View Threaded


chris at simplistix

Jul 31, 2004, 3:30 AM

Post #1 of 22 (3985 views)
Permalink
July Bug Day Roundup

Hi All,

A pretty frenetic bug day saw a LOT of cruft ejected from the collector.
It also saw a good few bugs resolved, and a lot more marked as resolved
that had been fixed along the way.

Also, there's now documentation of what the various collector states
mean at:

http://dev.zope.org/CVS/CollectorStatuses

Some points of it are still up for discussion, so please join in at
zope-coders [at] zope if you have a view!

All in all, a massive 64 issues were dealt with!
Many thanks to all who helped out, look forward to seeing as many of you
as possible for the next one at the end of August...

cheers,

Chris

Here's what got dealt with (there are "player stats" at the bottom ;-)

Resolved:

#13 - Undo with multiple ZEO´s mounted
#248 - refresh does not work for products initialized in the old style
#290 - Usage of trry: except: in Zope source
#515 - Collecor.__init__ stores new brains class in volatile attribute
#552 - Import obj w/ Proxy roles into Zope w/o role fails
#578 - ImplicitAcquisitionWrapper claim to be callable()
#691 - KeywordIndex and callable
#692 - DateTime fails to pass european dates
#740 - _tzoffset returns wrong offset
#891 - Enable locking of RESPONSE.setStatus and RESPONSE.setBody
#1156 - getObject fails to return objects which redefine __len__
#1233 - ZOPE_CONFIG environment var for app=Zope.app()
#1252 - VIRTUAL_URL
#1279 - --config-file support for test.py
#1295 - 2.7.0 tutorial Lesson 6
#1370 - customDefaultZPTReport.dtml Creates Invalid HTML
#1416 - DateTime class doesn't initialize off DateTime instance
#1421 - DateTime doesn't always raise a SyntaxError for bad dates
#1439 - Zope 2.7.2 for Windows uses Python 2.3.3
#1440 - Zope 2.7.2 lists as "unreleased version"
#1441 - Silly Borg Headers tempt MS Office
#1442 - Example cache sizes in zope.conf, using MB or kB
#1445 - test.py problems with -p and -v(v)

Rejected:

#18 - sequence-last inducts error when used in nested dtml-in
#37 - Z ODBC Database with DB2 TIMESTAMP#
#50 - DCO2 based ZOracle Adapter does not use bind variables
#154 - Zope crashes on external method loading dll
#229 - Paste object without view permission on management screen
#237 - Version editing via FTP/WebDAV
#247 - permission strings in ZMI aren't consistently capitalized
#418 - DTML anonymizes exceptions
#522 - "Owned" assumes access to the ObjectManagerItem Interface
#717 - support selection:{type} in manage_propertiesForm
#746 - dtml-sendmail expected string, unicode found
#775 - manage_changeProperties can't set boolean properties to false
#1223 - Problem with meta_type
#1308 - (duplicate) Need "actual URL" method
#1361 - (duplicate) etag header obliterated no matter what
#1378 - ExtensionClass Bug: unbound C method...
#1391 - tal: namspace attributes dropped before i18n processing
#1404 - envirnoment and cgi_environment don't appear to work
#1419 - Transience should return True|False, not 1|0
#1424 - Zope returns 400 to report an internal error
#1427 - Accept config file from stdin
#1444 - (duplicate) ZODB Error from Historical Compare
#1446 - TAL parse error on tags inside script
#1449 - DateTime wrong when 12:00:00AM
#1448 - "cache picture and css mixing"

Wontfix:

#15 - sqlgroup.py enhancements - set, noparens, and comma tags
#127 - css files defines absolut sizes
#136 - FTP Upload raises Unauthorized after file upload
#371 - DTML and Python security function APIs are different
#553 - ZMI "find" doesnt find in File with text
#564 - Content-length of HEAD responses should be based on *parsed*
#729 - Edit page title tag should show the object title or id
#872 - Numbers in STX Tables
#1277 - manage_FTPget of Image is sad.
#1428 - Serve xml as application/xml instead of text/xml

Deferred: (meaning act on these or they get rejected next month)

#428 - FTP and large file uploads
#526 - anonymous users can sometimes view historical revisions
#804 - "make clean" doesn't run
#1398 - BTree raise SystemError on FreeBSD
#1401 - SystemError in SessionDataManager

And here's the "player stats" ;-)

Resolved Rejected Wontfixed Deferred Assists
chrisw 16 19 7 2
ajung 6 6 2 2
ctheune 1 1 2
arnarl 5
shh 2
casey 2
jim 1
evan 1
mcdonc 1
stevea 1
brian 1

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


klm at zope

Jul 31, 2004, 10:17 AM

Post #2 of 22 (3952 views)
Permalink
Re: July Bug Day Roundup [In reply to]

On Sat, 31 Jul 2004, Chris Withers wrote:

> Also, there's now documentation of what the various collector states
> mean at:
>
> http://dev.zope.org/CVS/CollectorStatuses
>
> Some points of it are still up for discussion, so please join in at
> zope-coders [at] zope if you have a view!

I have a pretty different conception of the states. I've created another
page, linked into chris', with my alternate framing, at:

http://dev.zope.org/CVS/CollectorStatusesAlt

Obviously, we need to resolve the differences so all the supporters use
the states the same way. I hardly participate in the zope collector
(though i do use collectors all the time for a lot of projects), so i'll
defer to the people who actually use it - but want to suggest this framing
because i think it'll help reduce the chaos.

> All in all, a massive 64 issues were dealt with!
> Many thanks to all who helped out, look forward to seeing as many of you
> as possible for the next one at the end of August...

Thanks to all for making zope better, and particularly to chris for
shepherding the effort!

Ken
klm [at] zope
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


chris at simplistix

Aug 9, 2004, 5:22 PM

Post #3 of 22 (3943 views)
Permalink
Re: July Bug Day Roundup [In reply to]

(bringing this back to zope-coders where it belongs..)

Ken Manheimer wrote:
> Then why were you asking for feedback in the first place?

Well, naturally, I expected everyone to agree with me ;-)

> A few supporters (chris, andreas, and dieter, at least) have indicated

I didn't read Andreas's comments as disagreeing, Chris seems to be on
the samish wavelength, Dieter's comment is worthless without elaboration...

> that they had different interpretations than you did, more similar to what
> i am suggesting. So at the least, the waters were already at least this
> muddy. The question, then, is how to settle on one set of states.

Yeah, agreed :-)

> - Lennert has proposed a "Submitted" state (which i interpret as being
> for issues that are pending disposition), instead of pending
> (i think "Submitted" is an improvement on "Pending")

I think Sidnei's reminder of Roundup's "Unread" state is better yet.

> - and "Pending" would be for items awaiting more info (i think that
> should instead be either "Accepted", if someone is taking
> responsibility, if only to "Reject" the thing if no more info is
> forthcoming, else "Deferred" if nobody is taking responsibility - it
> can go back to "Submitted" if more info comes...

I actually like Pending here. For me, it's Pending something,
acceptance, rejection, who knows? we need more info ;-)
I notice to attach a lot of importance to having someone assigned and
accountable. Is this a reality in an open source development environment?

> - sidnei mentioned that roundup calls the initial state "unread" (but i
> don't think that really applies to our initial state, because things
> may be read but not assigned any handling - and i don't think we need
> a state for truly "unread")

Hmm... I see you point, can't say why, but Unread still feels "right"er
for me :-S

> I guess i think we could make progress talking each state through.

Sure, lets start from the top. What state does stuff go into when it's
first plonked into the collector?

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


klm at zope

Aug 10, 2004, 7:21 AM

Post #4 of 22 (3934 views)
Permalink
Re: July Bug Day Roundup [In reply to]

On Tue, 10 Aug 2004, Chris Withers wrote:

> Ken Manheimer wrote:
> > I guess i think we could make progress talking each state through.
>
> Sure, lets start from the top. What state does stuff go into when it's first
> plonked into the collector?

"Submitted"

This is the state for things that are awaiting handling, as opposed to
being handled or closed/settled.

Issues _can_ return here if they got into a being-handled or closed
state but then lost that progress. Eg, something that was assigned to a
supporter, but then the supporter had to bail out and no other
supporters could take it on. Or something that was mistakenly closed -
and no supporters can take responsibility for it.

That's my candidate for the first state.

Ken
klm [at] zope
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


klm at zope

Aug 10, 2004, 8:38 AM

Post #5 of 22 (3946 views)
Permalink
Re: July Bug Day Roundup [In reply to]

On Tue, 10 Aug 2004, Ken Manheimer wrote:

> On Tue, 10 Aug 2004, Chris Withers wrote:
>
> > Ken Manheimer wrote:
> > > I guess i think we could make progress talking each state through.
> >
> > Sure, lets start from the top. What state does stuff go into when it's first
> > plonked into the collector?
>
> "Submitted"
>
> This is the state for things that are awaiting handling, as opposed to
> being handled or closed/settled.
>
> Issues _can_ return here if they got into a being-handled or closed
> state but then lost that progress. Eg, something that was assigned to a
> supporter, but then the supporter had to bail out and no other
> supporters could take it on. Or something that was mistakenly closed -
> and no supporters can take responsibility for it.
>
> That's my candidate for the first state.

A conversation with some folks here swayed me to a slightly different
proposal for "Submitted". Instead of replacing "Pending", it would be
only for issues that have not been touched. Comments would move issues to
"Pending", and "Pending" would be where issues return if they are
"unaccepted" moved out of a settled state without having an assigned
supporter.

So i'm up to two states:

"Submitted"

This is the state for things that are completely unhandled. Comments
move "Submitted" issues to "Pending", and once out of "Submitted" issues
generally do not return there. (Until we discover a compelling reason
to recirculate issues back, they don't return here.)

"Pending"

Issues that have been handled (have comments and/or other actions) but
are still awaiting substantial disposition (assignment or settlement).

Issues _can_ return here if they got into a being-handled or closed
state but then lost that progress. Eg, something that was assigned to a
supporter, but then the supporter had to bail out and no other
supporters could take it on. Or something that was mistakenly settled,
but has no supporter to take its responsibility and so has to be
returned to an awaiting-disposition state - "Pending" is it.

Ken
klm [at] zope
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


chris at simplistix

Aug 12, 2004, 4:55 AM

Post #6 of 22 (3928 views)
Permalink
Re: July Bug Day Roundup [In reply to]

Ken Manheimer wrote:

> "Submitted"
>
> This is the state for things that are awaiting handling, as opposed to
> being handled or closed/settled.
>
> Issues _can_ return here if they got into a being-handled or closed
> state but then lost that progress.

Surely a closed state is a closed state? The only way I can see
something going from a closed state back to "Submitted" is if a mistake
was made, correct?

> Eg, something that was assigned to a
> supporter, but then the supporter had to bail out and no other
> supporters could take it on. Or something that was mistakenly closed -
> and no supporters can take responsibility for it.
>
> That's my candidate for the first state.

Sounds good to me :-)

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


chris at simplistix

Aug 12, 2004, 4:59 AM

Post #7 of 22 (3928 views)
Permalink
Re: July Bug Day Roundup [In reply to]

Ken Manheimer wrote:
> So i'm up to two states:
>
> "Submitted"
>
> This is the state for things that are completely unhandled. Comments
> move "Submitted" issues to "Pending", and once out of "Submitted" issues
> generally do not return there. (Until we discover a compelling reason
> to recirculate issues back, they don't return here.)

Even better! I can't see any reason for issues to return to "Submitted"
given the definition here...

> "Pending"
>
> Issues that have been handled (have comments and/or other actions) but
> are still awaiting substantial disposition (assignment or settlement).
>
> Issues _can_ return here if they got into a being-handled or closed
> state but then lost that progress. Eg, something that was assigned to a
> supporter, but then the supporter had to bail out and no other
> supporters could take it on. Or something that was mistakenly settled,
> but has no supporter to take its responsibility and so has to be
> returned to an awaiting-disposition state - "Pending" is it.

Yep, even better too. Is there any way we could have issues that are in
non-terminal states other that "submitted" be authomatically returned to
Pending if they're been in their current state for longer than 1 month
with no action (ie: comments or state changes) added?

cheers,

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


klm at zope

Aug 12, 2004, 2:23 PM

Post #8 of 22 (3933 views)
Permalink
Re: July Bug Day Roundup [In reply to]

On Thu, 12 Aug 2004, Chris Withers wrote:

> Ken Manheimer wrote:
>
> > "Submitted"
> >
> > This is the state for things that are awaiting handling, as opposed to
> > being handled or closed/settled.
> >
> > Issues _can_ return here if they got into a being-handled or closed
> > state but then lost that progress.
>
> Surely a closed state is a closed state? The only way I can see
> something going from a closed state back to "Submitted" is if a mistake
> was made, correct?

Mistaken settlement of an issue is one reason. There are others. In the
real world situations can change in unexpectable ways, making eg
previously unfixable things fixable. (The goal of issue management is not
perfection, but improved collective intelligence in the process of dealing
with problem reports.)

Ken
klm [at] zope

Intelligence: Err
and err,
and err again,
but less
and less
and less. -- Piet Hien ("Grooks")


_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


klm at zope

Aug 12, 2004, 2:23 PM

Post #9 of 22 (3950 views)
Permalink
Re: July Bug Day Roundup [In reply to]

Sounds like nobody objects to "Suspend" and "Pending" as i framed them.
Cool.

Here's three more, leaving the two most controversial (and the idea of
providing for automatic expiration) for later. I'll be out of the office
and away until monday, so will continue my part in the discussion then.
Good weekend, all!

"Assigned" (instead of "Accepted")

Issues that have at least one supporter responsible for their
solution. This is the state for issues that are being worked on or are
awaiting complete assessment for their viability depending on further
input from the submitter.

The assigned supporters are responsible for either solving the issue or
collecting further information to determine what resolution it deserves.

Supporters are assigned to issues either by "accepting" them or via
"assignment" by another supporter or collector manager. Supporters can
resign from the issue, but the issue will automatically move back to
"Pending" if that leaves it with no supporters.

(People interested in helping with the resolution of an accepted issue -
or any issue, for that matter - but lacking official supporter privileges
can signal their intention by posting a comment to the issue.)

"Resolved"

The fix or feature has been implemented, along with any necessary tests.

Tests which would provoke the bug, if it were still present, and/or
demonstrate the correctness of the new functionality are always required,
unless they are impossible to write. (Leniency may be warranted for very
minor changes?)

When you resolve an issue, please include details about:

o the action taken

o the repository branches where code was committed

o the expected Zope version(s) where the changes will land.

"Rejected"

Issues assessed to be invalid for this collector, so that they will not
be addressed any further.

Common reasons for rejection:

o The issue is outside the scope of the collector. For the Zope
collector, this means the issue is not with a central Zope component,
but rather a third-party item such as a database adapter, Plone,
etc. The rejecter should indicate the appropriate venue for the
issue, when known.

o The issue cannot be reproduced. The rejector should establish that
there is a test, if feasible, demonstrating that the reported behaviour
does not occur, writing one if necessary.

o More information was necessary to assess the issue, and it was
requested, but was not provided within a reasonable period (typically
a month).

> "Submitted"
>
> This is the state for things that are completely unhandled. Comments
> move "Submitted" issues to "Pending", and once out of "Submitted" issues
> generally do not return there. (Until we discover a compelling reason
> to recirculate issues back, they don't return here.)
>
> "Pending"
>
> Issues that have been handled (have comments and/or other actions) but
> are still awaiting substantial disposition (assignment or settlement).
>
> Issues _can_ return here if they got into a being-handled or closed
> state but then lost that progress. Eg, something that was assigned to a
> supporter, but then the supporter had to bail out and no other
> supporters could take it on. Or something that was mistakenly settled,
> but has no supporter to take its responsibility and so has to be
> returned to an awaiting-disposition state - "Pending" is it.

Ken
klm [at] zope

_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


chris at simplistix

Aug 13, 2004, 1:33 AM

Post #10 of 22 (3952 views)
Permalink
Re: Re: July Bug Day Roundup [In reply to]

Ken Manheimer wrote:

> Sounds like nobody objects to "Suspend" and "Pending" as i framed them.
> Cool.

Who the what the? I didn't see them anywhere...
Pending -> fine, Suspend -> even the word makes me nervous ;-)

> "Assigned" (instead of "Accepted")
>
> Issues that have at least one supporter responsible for their
> solution. This is the state for issues that are being worked on or are
> awaiting complete assessment for their viability depending on further
> input from the submitter.
>
> The assigned supporters are responsible for either solving the issue or
> collecting further information to determine what resolution it deserves.
>
> Supporters are assigned to issues either by "accepting" them or via
> "assignment" by another supporter or collector manager. Supporters can
> resign from the issue, but the issue will automatically move back to
> "Pending" if that leaves it with no supporters.
>
> (People interested in helping with the resolution of an accepted issue -
> or any issue, for that matter - but lacking official supporter privileges
> can signal their intention by posting a comment to the issue.)

OK. I still like the idea of assigned stuff going back to pending if no
action happens for a month. Is that a possibility?

> "Resolved"
>
> The fix or feature has been implemented, along with any necessary tests.
>
> Tests which would provoke the bug, if it were still present, and/or
> demonstrate the correctness of the new functionality are always required,
> unless they are impossible to write. (Leniency may be warranted for very
> minor changes?)

...or in situations where ther eare no tests for the whole area the
change is to be made in?

> When you resolve an issue, please include details about:
>
> o the action taken
>
> o the repository branches where code was committed
>
> o the expected Zope version(s) where the changes will land.

Sounds good.

> "Rejected"
>
> Issues assessed to be invalid for this collector, so that they will not
> be addressed any further.
>
> Common reasons for rejection:
>
> o The issue is outside the scope of the collector. For the Zope
> collector, this means the issue is not with a central Zope component,
> but rather a third-party item such as a database adapter, Plone,
> etc. The rejecter should indicate the appropriate venue for the
> issue, when known.
>
> o The issue cannot be reproduced. The rejector should establish that
> there is a test, if feasible, demonstrating that the reported behaviour
> does not occur, writing one if necessary.
>
> o More information was necessary to assess the issue, and it was
> requested, but was not provided within a reasonable period (typically
> a month).

Yep.

>>"Submitted"
>>
>> This is the state for things that are completely unhandled. Comments
>> move "Submitted" issues to "Pending", and once out of "Submitted" issues
>> generally do not return there. (Until we discover a compelling reason
>> to recirculate issues back, they don't return here.)

Can we clear this up? How about:

"Submitted"
This is the state for items that have not been assessed. Comments
move "Submitted" issues to "Pending", and once out of "Submitted"
issues do not return there.

>>"Pending"
>>
>> Issues that have been handled (have comments and/or other actions) but
>> are still awaiting substantial disposition (assignment or settlement).
>>
>> Issues _can_ return here if they got into a being-handled or closed
>> state but then lost that progress. Eg, something that was assigned to a
>> supporter, but then the supporter had to bail out and no other
>> supporters could take it on. Or something that was mistakenly settled,
>> but has no supporter to take its responsibility and so has to be
>> returned to an awaiting-disposition state - "Pending" is it.

Sounds good.

Still waiting to see what this scarey "Suspend" state is, I'm hoping it
was a typo :-S

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


chris at simplistix

Aug 13, 2004, 1:46 AM

Post #11 of 22 (3951 views)
Permalink
Re: Re: July Bug Day Roundup [In reply to]

Ken Manheimer wrote:
> "Rejected"
>
> Issues assessed to be invalid for this collector, so that they will not
> be addressed any further.
>
> Common reasons for rejection:

I'd like to add one here:

o Duplicate issues.

...unless we can add Duplicate functionality like the original collector
had ;-)

cheers,

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


klm at zope

Aug 13, 2004, 6:30 AM

Post #12 of 22 (3932 views)
Permalink
Re: Re: July Bug Day Roundup [In reply to]

On Fri, 13 Aug 2004, Chris Withers wrote:

> Ken Manheimer wrote:
>
> > Sounds like nobody objects to "Suspend" and "Pending" as i framed them.
> > Cool.
>
> Who the what the? I didn't see them anywhere...
> Pending -> fine, Suspend -> even the word makes me nervous ;-)

Whoops - "Submitted" (as lennart proposed, and i included in my first
batch in this thread), not "Suspend".

> [...]
> >>"Submitted"
> >>
> >> This is the state for things that are completely unhandled. Comments
> >> move "Submitted" issues to "Pending", and once out of "Submitted" issues
> >> generally do not return there. (Until we discover a compelling reason
> >> to recirculate issues back, they don't return here.)
>
> Can we clear this up? How about:
>
> "Submitted"
> This is the state for items that have not been assessed. Comments
> move "Submitted" issues to "Pending", and once out of "Submitted"
> issues do not return there.

Fine. I might even add a bit more clarification:

"Submitted"
This is the state for items that have not been touched by a
supporter. Any action moves issues out of the Submitted state, and
once out issues do not return there. Comments move "Submitted" issues
to "Pending".

> [...]
> Still waiting to see what this scarey "Suspend" state is, I'm hoping it
> was a typo :-S

Or, as i like to say, a typoo.

Ken
klm [at] zope
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


tseaver at zope

Aug 13, 2004, 7:42 AM

Post #13 of 22 (3924 views)
Permalink
Re: July Bug Day Roundup [In reply to]

Chris Withers wrote:

> OK. I still like the idea of assigned stuff going back to pending if no
> action happens for a month. Is that a possibility?

I would rather address the issue with "nagmail": each supporter would
get a periodic (weekly, likely, for the main Zope collector) e-mail
summarizing the issues to which they are assigned.

>> "Resolved"
>>
>> The fix or feature has been implemented, along with any necessary
>> tests.
>>
>> Tests which would provoke the bug, if it were still present, and/or
>> demonstrate the correctness of the new functionality are always
>> required,
>> unless they are impossible to write. (Leniency may be warranted for
>> very
>> minor changes?)
>
>
> ...or in situations where ther eare no tests for the whole area the
> change is to be made in?

Nope. *Any* change could be expected to have one or more tests which
demonstrate either that:

- the bug existed before before the fix (e.g., the test fails without
the fix), but no longer exists after (the test passes).

- the new feature works.

Writing more tests for the unit being changed qualifies as a "work of
supererogation." There are occoasionally areas (medusa's guts, for one)
which are so gnarly that nobody can figure out how to write tests for
that. If you plan to resolve an issue without adding test, and want to
plead "gnarliness" as an excuse, expect to defend the choice. ;)

Tres.
--
===============================================================
Tres Seaver tseaver [at] zope
Zope Corporation "Zope Dealers" http://www.zope.com
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


tseaver at zope

Aug 13, 2004, 7:42 AM

Post #14 of 22 (3960 views)
Permalink
Re: July Bug Day Roundup [In reply to]

Chris Withers wrote:

> OK. I still like the idea of assigned stuff going back to pending if no
> action happens for a month. Is that a possibility?

I would rather address the issue with "nagmail": each supporter would
get a periodic (weekly, likely, for the main Zope collector) e-mail
summarizing the issues to which they are assigned.

>> "Resolved"
>>
>> The fix or feature has been implemented, along with any necessary
>> tests.
>>
>> Tests which would provoke the bug, if it were still present, and/or
>> demonstrate the correctness of the new functionality are always
>> required,
>> unless they are impossible to write. (Leniency may be warranted for
>> very
>> minor changes?)
>
>
> ...or in situations where ther eare no tests for the whole area the
> change is to be made in?

Nope. *Any* change could be expected to have one or more tests which
demonstrate either that:

- the bug existed before before the fix (e.g., the test fails without
the fix), but no longer exists after (the test passes).

- the new feature works.

Writing more tests for the unit being changed qualifies as a "work of
supererogation." There are occoasionally areas (medusa's guts, for one)
which are so gnarly that nobody can figure out how to write tests for
that. If you plan to resolve an issue without adding test, and want to
plead "gnarliness" as an excuse, expect to defend the choice. ;)

Tres.
--
===============================================================
Tres Seaver tseaver [at] zope
Zope Corporation "Zope Dealers" http://www.zope.com

_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


pw_lists at slinkp

Aug 13, 2004, 11:53 AM

Post #15 of 22 (3936 views)
Permalink
Re: Re: July Bug Day Roundup [In reply to]

On Fri, Aug 13, 2004 at 10:42:09AM -0400, Tres Seaver wrote:
> Writing more tests for the unit being changed qualifies as a "work of
> supererogation." There are occoasionally areas (medusa's guts, for one)
> which are so gnarly that nobody can figure out how to write tests for
> that. If you plan to resolve an issue without adding test, and want to
> plead "gnarliness" as an excuse, expect to defend the choice. ;)

Supererogation, great word.

Some day I must learn the fine art of picking bugs for bug day that
don't lead me down the path of struggling to get the first no-op testcase
to *run* in some previously-untested area, before i can get any
real work done...
"This little bug looks pretty easy to fix... DOH!"
:-\

--

Paul Winkler
http://www.slinkp.com
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


chris at simplistix

Aug 16, 2004, 4:05 AM

Post #16 of 22 (3950 views)
Permalink
Re: Re: July Bug Day Roundup [In reply to]

Ken Manheimer wrote:
> "Submitted"
> This is the state for items that have not been touched by a
> supporter. Any action moves issues out of the Submitted state, and
> once out issues do not return there. Comments move "Submitted" issues
> to "Pending".

Sounds good to me :-)

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


chris at simplistix

Aug 16, 2004, 4:10 AM

Post #17 of 22 (3969 views)
Permalink
Re: July Bug Day Roundup [In reply to]

Tres Seaver wrote:

> I would rather address the issue with "nagmail": each supporter would
> get a periodic (weekly, likely, for the main Zope collector) e-mail
> summarizing the issues to which they are assigned.

I'm all for both. nagmail is great for annoying^wreminding the
supporter, but it doesn't bring issues back into the
pool-that-need-to-be-dealt-with (I believe "Pending" is the agreed term
for this now) so other people can deal with them once the supporter has
changed their email address or learned how to filter out the nagmail ;-)
(FWIW, I think every single issue that had been dumped in "Deferred" was
assigned to someone who had since changed their email address...)

> Nope. *Any* change could be expected to have one or more tests which
> demonstrate either that:
>
> - the bug existed before before the fix (e.g., the test fails without
> the fix), but no longer exists after (the test passes).
>
> - the new feature works.

Okay, but big areas where there are no tests may see less attention as a
result. I know this is a horrible chicken and egg situation :-S

> Writing more tests for the unit being changed qualifies as a "work of
> supererogation."

And in english? ;-)

> There are occoasionally areas (medusa's guts, for one)
> which are so gnarly that nobody can figure out how to write tests for
> that. If you plan to resolve an issue without adding test, and want to
> plead "gnarliness" as an excuse, expect to defend the choice. ;)

Hehe, okay, that sounds fair enough :-)

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


tseaver at zope

Aug 16, 2004, 1:06 PM

Post #18 of 22 (3941 views)
Permalink
Re: July Bug Day Roundup [In reply to]

Chris Withers wrote:

>> Writing more tests for the unit being changed qualifies as a "work of
>> supererogation."
>
>
> And in english? ;-)

Check the Articles of Religion in your Book of Common Prayer.

Tres.
--
===============================================================
Tres Seaver tseaver [at] zope
Zope Corporation "Zope Dealers" http://www.zope.com
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


chris at simplistix

Aug 16, 2004, 11:54 PM

Post #19 of 22 (3940 views)
Permalink
Re: July Bug Day Roundup [In reply to]

Tres Seaver wrote:
>> And in english? ;-)
>
> Check the Articles of Religion in your Book of Common Prayer.

I'm afraid I don't have access to such a tome :-/

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


tseaver at zope

Aug 17, 2004, 6:57 AM

Post #20 of 22 (3924 views)
Permalink
Re: July Bug Day Roundup [In reply to]

On Tue, 17 Aug 2004 08:54:18 +0200
Chris Withers <chris [at] simplistix> wrote:
> Tres Seaver wrote:
> >> And in english? ;-)
> >
> > Check the Articles of Religion in your Book of Common
> Prayer.
>
> I'm afraid I don't have access to such a tome :-/

Your Parliament still has to approve changes to it ;)

http://www.eskimo.com/~lhowell/bcp1662/index.html

and in particular:

http://www.eskimo.com/~lhowell/bcp1662/articles/articles.html

Tres.
--
============================================================
Tres Seaver tseaver [at] zope
Zope Corporation "Zope Dealers" http://www.zope.com
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


chris at simplistix

Aug 17, 2004, 10:18 PM

Post #21 of 22 (3934 views)
Permalink
Re: July Bug Day Roundup [In reply to]

Tres Seaver wrote:
> Your Parliament still has to approve changes to it ;)

You talking about the Irish or the English?

> and in particular:
>
> http://www.eskimo.com/~lhowell/bcp1662/articles/articles.html

http://www.eskimo.com/~lhowell/bcp1662/articles/articles.html#14

I think I understand this now having read everythign in context: don't
write more tests than you need to, right?

Hmmm...

Chris - http://www.eskimo.com/~lhowell/bcp1662/articles/articles.html#33

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders


tseaver at zope

Aug 19, 2004, 6:47 AM

Post #22 of 22 (3926 views)
Permalink
Re: July Bug Day Roundup [In reply to]

Chris Withers wrote:
> Tres Seaver wrote:
>
>> Your Parliament still has to approve changes to it ;)
>
>
> You talking about the Irish or the English?
>
>> and in particular:
>>
>> http://www.eskimo.com/~lhowell/bcp1662/articles/articles.html
>
>
> http://www.eskimo.com/~lhowell/bcp1662/articles/articles.html#14
>
> I think I understand this now having read everythign in context: don't
> write more tests than you need to, right?

Nope. The A of R says that claiming extra "stars in your crown" for
going above-and-beyond the law is bogus; it also says that the Church
may not teach / compel people to do such things.

Nailing-theses-to-the-door'ly,

Tres.
_______________________________________________
Zope-Coders mailing list
Zope-Coders [at] zope
http://mail.zope.org/mailman/listinfo/zope-coders

Zope coders RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.