Yes labels and tags would help me to keep them "out of the way" but
like Yoann suggests, I expect the "contrib repository" to not be
released and tagged in strict synch with the Hibernate OGM main
project?
I guess we didn't discuss this in depth, but if we don't allow the
"contrib repository" to
I would prefer to release both at the same time even if there are no
big changes.
As for creating a new project, wouldn't have a new label or component be enough?
On Fri, Mar 17, 2017 at 8:21 AM, Yoann Rodiere wrote:
> Isn't marking those as "New feature" enough? Or, if
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
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