Re: [hibernate-dev] JIRA usage for OGM
Isn't marking those as "New feature" enough? Or, if necessary, tagging
them?
I obviously can't tell how others use JIRA, but personally I don't dive
into old tickets every day. Most of the time I only check the new
(incoming) tickets and those assigned to the next release. So, those extra
tickets are only a problem when setting the goals for the next release, and
we could easily tag them so as to exclude them from our searches.
The actual question may be: when those tickets are solved, will they be
released synchronously with OGM releases? I.e., will the contrib repository
be released at the same time as OGM? If not, then yes, I'd say we'd better
move these tickets to another JIRA project.
Yoann Rodière <yoann(a)hibernate.org>
Hibernate NoORM Team
On 16 March 2017 at 14:14, Sanne Grinovero <sanne(a)hibernate.org> wrote:
There are more than 300 open issues, which is fine but rather than
being these well-defined issues most sound like wishful thinking of
someone having a (possibly cool) idea but not really executing on it.
Since JIRA is an issue tracker and not really a planning tool / note
taking app I wish we could limit this practice of having issues like
"explore integration with.." ?
More specifically, could we move "out of the way" all issues related
to Databases which we're moving into the "contrib" repository?
I think it would be nice to have these in a different JIRA project.
Thanks,
Sanne
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev