[hibernate-dev] JIRA issue status - Closed v. Resolved

Steve Ebersole steve at hibernate.org
Wed Dec 21 09:51:43 EST 2011

On 12/20/2011 02:55 PM, Sanne Grinovero wrote:
> I agree as well on interpreting "Closed" as "forever"; AFAIR new
> issues can be linked to the older closed ones so that while a comment
> might not be allowed, it's still possible to point to "follow ups" in
> case of need.
> I'm not sure however about enforcing this, but I'm not against it. I'd
> prefer if committers had the option to reopen, it's never nice when
> tools prevent you to fix eventual mistakes.

Yeah I think this is the conclusion I am coming (back) to as well. 
Which luckily is exactly how we have jira set up currently :)

I think the big change here (for core at least as it sounds like the 
other projects do this already) is to consider released issues closed, 
to the point of moving issues from a Resolved status to a Closed status 
as part of the release.

By convention I still think an issue I report and then solve is Closed 
rather than Resolved, but eh, its an opinion.

So overall:
* Close all issues on release
* Closed issues are, by *convention*, not reopened
* Allow dev team to reopen issues that are closed, but with the 
understanding that this is there just to edit the issue details to fix 

> On the release steps: I'm not sure re Maven plugins, but JIRA has a
> REST API as well for automating transitions. I agree with Hardy that
> I'm not concerned about such a manual step, but in case we want in
> future this could be automated as I think releases should be more and
> more automated, but we can proceed by small steps; I'd expect this to
> be easier with gradle, and maybe Maven plugins exists.
> There definitely is automation in Jenkins which we could use for
> release automation anyway:
> https://wiki.jenkins-ci.org/display/JENKINS/Jira+Issue+Updater+Plugin

Like I said in Hardy's response, my concern is not the time it takes to 
do this, but more me actually remembering to do it :)

I will look at automating this via gradle at some point.  Though, TBH, 
setting up a jenkins job to do the release sounds fantastic.  My concern 
is the infinispan tests though.  For each release lately I have had to 
run the build multiple times until those happen to pass.

steve at hibernate.org

More information about the hibernate-dev mailing list