[Pyblosxom-devel] call for help -- help me triage!

[will kahn-g. <wi...@bl...>]

Between the bugs we migrated over from SourceForge and new bugs that are
being created, there's a fair amount of work for PyBlosxom.  I've marked
some of it as needing to be done in the 1.5 cycle.  Half of those bugs,
though, probably just need to be triaged.

Anyhow, I need some help.  At work, I'm in the middle of a very
aggressive/ambitious development cycle that ends March 1st.  I really
want to make sure PyBlosxom continues to move forward rather than
languishing in the eves of my free time.

If anyone has an hour they can spare this week, I encourage you to pick
a bug from the issue list and triage it.  Triaging involves finding a
bug marked "unread" or "chatting", reading through it, and answering the
following questions:

1. is the bug reproducible with what's in git master?

2. if the bug is reproducible, is there a theory for what's going on and
what might need to be fixed?

Add a comment to the issue with your answers.  And that's it!  You don't
have to fiddle with flags or issue metadata--just add a comment.

Answering those two questions turns a bug from an unknown into something
that we can do something with.

The issue tracker is at:

http://pyblosxom.bluesock.org/bugs/

The 1.5 milestone is at:

http://pyblosxom.bluesock.org/bugs/issue?status=-1,1,2,3,4,5,6,7&@sort=-activity&@search_text=&@columns=id,activity,title,creator,assignedto,status&@dispname=Milestone%201.5&@group=priority&milestone=1&@filter=status,milestone&@pagesize=50&@startwith=0

There's a "Milestone 1.5" link in the sidebar of the issues page if that
link is too ornery.

Thank you!  Your help will make it more likely we get an rc3 with a lot
of bug fixes out in the near term rather than in June.

/will