Now that 3.2.7 is out, should we be changing the status resolved issues
to closed in JIRA.

Jim

[ Post a follow-up to this message ]

Jim Gallacher wrote:
> Now that 3.2.7 is out, should we be changing the status resolved issues
> to closed in JIRA.


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?

Jim

[ Post a follow-up to this message ]

Jim Gallacher wrote ..
> Jim Gallacher wrote: 

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.
[vbcol=seagreen]
> 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

[ Post a follow-up to this message ]

Graham Dumpleton wrote:
> Jim Gallacher wrote ..
> 
>
>
> If that is what closed implies. Is there somewhere which states what we
> should interprete the different status as meaning? I don't recollect seein
g
> anything unless I am missing the obvious.

http://www.atlassian.com/software/j...2/statuses.html

The status of an issue cannot be changed once it has been marked as closed.
 
>
>
> 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, easie
r to
> just fix it on the spot, although I am tending towards thinking having a
> JIRA issue for all changes is a good goal.

I guess I'm just looking for a bit of clarity. Let's say we make a
3.2.10 bugfix release. A JIRA issue which is fixed in 3.2.10 gets marked
as fixed in 3.2. A user looks at the issue and says "Great, I'm using
3.2.7, and it says it's fixed in 3.2, so I must be ok".

Jim

[ Post a follow-up to this message ]

Jim Gallacher wrote .. 
> easier to 
> a 
>
> I guess I'm just looking for a bit of clarity. Let's say we make a
> 3.2.10 bugfix release. A JIRA issue which is fixed in 3.2.10 gets marked
> as fixed in 3.2. A user looks at the issue and says "Great, I'm using
> 3.2.7, and it says it's fixed in 3.2, so I must be ok".

Hmmm, I can see why you might be confused by my response. I was only
referring to the "unit test" question. Totally missed the 3.2.7 question.

On the latter I'm not sure. This sort of confusion is why I like to add fina
l
comments to issues when I put stuff back in a repository. I was remiss this
time in not mentioning that the fixes would be expected to first be availabl
e
in 3.3.0.

BTW, are we going to put up your developer guidelines anywhere for viewing?

http://www.modpython.org/pipermail/...ber/019712.html

Just spent a while trying to find out how to subscribe to python-cvs. Couldn
't
find it in an obvious spot unless I missed the obvious.

Graham

[ Post a follow-up to this message ]

> BTW, are we going to put up your developer guidelines anywhere for viewing?
>
>   http://www.modpython.org/pipermail/...ber/019712.html

Until it finds a permanent home the best place to look is here:
http://people.apache.org/~jgallache...developers.html

And mailing list info:
[url]http://people.apache.org/~jgallacher/mod_python/website-test/lists.html#mp-svn[/ur
l]

Jim

[ Post a follow-up to this message ]

Now that JIRA is responding again I thought I'd update the status of
some issues.

I've created a new JIRA version for 3.2.8.

Version 3.2 is still shown as unreleased. I assume the proper action is
to rename it to 3.2.7 and mark it as released. Can someone confirm that
this is the correct action? Nicolas? Grihsa?

Jim

[ Post a follow-up to this message ]

On 2/19/06, Graham Dumpleton <grahamd@dscpl.com.au> wrote:
>
> 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.


I've added you to the mod_python-developers group, so you should be able to
close issues now.  Is there anyone else who should be added?

I'm not quite clear who can add folks to that group (i.e. if someone in that
group can add other members or only the project admin - Grisha - can do so),
but I'll be keeping an eye out here.

Thanks.  -- justin

[ Post a follow-up to this message ]

Yup, I think it's the thing to do.

Regards,
Nicolas

2006/2/25, Jim Gallacher <jpg@jgassociates.ca>:
> Now that JIRA is responding again I thought I'd update the status of
> some issues.
>
> I've created a new JIRA version for 3.2.8.
>
> Version 3.2 is still shown as unreleased. I assume the proper action is
> to rename it to 3.2.7 and mark it as released. Can someone confirm that
> this is the correct action? Nicolas? Grihsa?
>
> Jim
>

[ Post a follow-up to this message ]