Jim Gallacher wrote .. > Jim Gallacher wrote: > > Now that 3.2.7 is out, should we be changing the status resolved issues > > to closed in JIRA.
If that is what closed implies. Is there somewhere which states what we should interprete the different status as meaning? I don't recollect seeing anything unless I am missing the obvious. BTW, as far as I know I still don't have full JIRA access otherwise I would help with closing them off. I noticed a few on the weekend that weren't even in resolved status yet, even though fixed in 3.2.7. Grisha, if you are reading this, what do I need to do to get admin JIRA access on mod_python stuff? I recollect asking you but can't remember what you said. I thought perhaps you were going to organise it, but also can't remember. > Other JIRA thoughts: > > Should we have a "unit test" component for bugs in the actual unit test > code? > > Since we plan on having 3.2.x bugfix releases, should create new JIRA > versions starting with 3.2.7? No harm in doing so. Probably would only be used if reported by someone else or change is not simple. For the simple stuff, like basic auth, easier to just fix it on the spot, although I am tending towards thinking having a JIRA issue for all changes is a good goal. Graham
