On 2015-12-08 16:50, Davide Giannella wrote:
On 08/12/2015 09:13, Julian Sedding wrote:
+1 - Setting the next release as fixVersion for blockers makes sense.
+1
This is VERY important. As main release manager this is the only way I
have to understand if a release should be blocked waiting on something
or not. Normally is not an issue for the unstable cuts but it is when
dealing with patch releases (stables. Not as in horses ;)).
I will proceed de-scheduling all 1.3.x that are not resolved and set 1.4
if missing.
So what's the correct JIRA state for something that has been fixed in
1.3.x, which is intended to be backported to 1.2, but hasn't been
backported yet? Can I still set that to "resolved"?
Best regards, Julian
