On 08/12/2015 09:13, Julian Sedding wrote: > +1 - Setting the next release as fixVersion for blockers makes sense.
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. Davide
