That was not working well for 4.1 which peaked at 64 unresolved issues. I have
decided to unassign all issues for version 4.1 and readded the truly important
ones. We are back at 4 which is much more reasonable.
Let's make sure we don't have to hit the big reset button in the future which
should
In this light - http://community.jboss.org/wiki/PlansForHibernateSearch4x/
this is an attempt to create a page on what we should/want to focus on for the
next release.
Not sure what x stands for tbh. Once upon a time I thought we will be releasing
4.0 Final, tightly
followed by a 4.1 mainly wit
Sorry that's likely me moving out issues from 4.0, for what I can
certainly judge we won't be adding in 4.0 anymore, but at the same
time don't feel certain enough to remove them from schedule so I just
moved them to the next one:
for most of these 4.1 is a better guess than the current 4.0 so I ho
I am seeing a lot of issues being assigned to 4.1. I find it unrealistic. Below
is a gentle reminder on how I'd like us to assign versions.
On 4 nov. 2011, at 11:40, Emmanuel Bernard wrote:
> ## Managing JIRA
>
> JIRA is not exactly a list to Santa Claus. Let me rephrase, JIRA is not a
> list
