On 08/12/2015 16:06, Julian Reschke wrote:
>
> 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"?
If the backport is part of the issue no you can't. If the
On 2015-12-09 10:33, Davide Giannella wrote:
On 08/12/2015 16:06, Julian Reschke wrote:
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"?
If the backport
+1 - Setting the next release as fixVersion for blockers makes sense.
For all other issues setting the fixVersion once it is fixed seems
more sensible.
Regards
Julian
On Tue, Dec 8, 2015 at 8:27 AM, Marcel Reutegger wrote:
> On 07/12/15 14:55, "Davide Giannella" wrote:
>>The
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
On 07/12/15 14:55, "Davide Giannella" wrote:
>The process I'm proposing is:
>
>- fixVersion = 1.4
>- fix it
>- fixVersion = 1.3.x
+1
Regards
Marcel
+1 to the idea. Additionally, we can probably setup a query to find issues
marked resolved in 1.4 while releasing and set fixForVersion according to
release being prepared.
-Vikas
(sent from mobile)
On 07-Dec-2015 7:25 pm, "Davide Giannella" wrote:
> Hello team,
>
> would it
+1. That's how I've been handling the issues assigned to me for a while
now.
Michael
On 7.12.15 2:55 , Davide Giannella wrote:
Hello team,
would it be a problem for anyone if we start a new process of not
setting a fixVersion like 1.3.12 but setting such specific version only
when we