Sorry this makes no sense, of course we need for improvements and such.
Actually it's now only a matter of monitoring and educating
Jacques
Le 13/04/2016 21:51, Jacques Le Roux a écrit :
BTW don't we need to remove Upcoming branch from unreleased versions? It's
confusing there, I mean. Is it
Done
Le 13/04/2016 21:39, Jacques Le Roux a écrit :
OK clear, if it works for releasing. I will update the wiki page
Thanks
Jacques
Le 13/04/2016 19:17, Jacopo Cappellato a écrit :
Hi Jacques,
the idea is that if we fix something in a release, for example 15.12.01
then it is implied that
BTW don't we need to remove Upcoming branch from unreleased versions? It's
confusing there, I mean. Is it necessary for the releasing process?
Jacques
Le 13/04/2016 21:39, Jacques Le Roux a écrit :
OK clear, if it works for releasing. I will update the wiki page
Thanks
Jacques
Le
OK clear, if it works for releasing. I will update the wiki page
Thanks
Jacques
Le 13/04/2016 19:17, Jacopo Cappellato a écrit :
Hi Jacques,
the idea is that if we fix something in a release, for example 15.12.01
then it is implied that all future releases will be also fixed: 15.12.03,
04
Hi Jacques,
the idea is that if we fix something in a release, for example 15.12.01
then it is implied that all future releases will be also fixed: 15.12.03,
04 but also 16.xx.xx etc...
In fact by policy we always fix in trunk and then backport if needed.
Cheers,
Jacopo
On Wed, Apr 13, 2016 at
Le 10/04/2016 10:35, Jacques Le Roux a écrit :
Hi Jacopo, inline...
Le 21/03/2016 15:10, Jacopo Cappellato a écrit :
Jacques, thanks for raising this point that I think is worth of some
clarifications and enhancements to get the best out of the Jira reports.
[...]
"Upcoming branch" should
Le 10/04/2016 10:35, Jacques Le Roux a écrit :
So, apart maybe some very specific cases, could we in others words say it
should not be used by bug fixes?
About the very specific cases, I wonder when a bug fixes cannot be backported,
notably to the last release branch.
I see only when a
Hi Jacopo, inline...
Le 21/03/2016 15:10, Jacopo Cappellato a écrit :
Jacques, thanks for raising this point that I think is worth of some
clarifications and enhancements to get the best out of the Jira reports.
[...]
"Upcoming branch" should be used to mark all the issues that are
20/03/2016 12:29, Jacopo Cappellato a écrit :
Hi Jacques,
I have added it because it is required as a "Fix for" version for patches
that are backported to the 15.12 release.
Jacopo
On Sat, Mar 19, 2016 at 10:23 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
Hi,
Who added the 15.12.01 unreleased version in Jira and why?
Thanks
Jacques
ded it because it is required as a "Fix for" version for patches
>>> that are backported to the 15.12 release.
>>>
>>> Jacopo
>>>
>>> On Sat, Mar 19, 2016 at 10:23 PM, Jacques Le Roux <
>>> jacques.le.r...@les7arts.com> wrote:
>>>
>>> Hi,
>>>>
>>>> Who added the 15.12.01 unreleased version in Jira and why?
>>>>
>>>> Thanks
>>>>
>>>> Jacques
>>>>
>>>>
>>
Sat, Mar 19, 2016 at 10:23 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
Hi,
Who added the 15.12.01 unreleased version in Jira and why?
Thanks
Jacques
t; version for patches
that are backported to the 15.12 release.
Jacopo
On Sat, Mar 19, 2016 at 10:23 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
Hi,
Who added the 15.12.01 unreleased version in Jira and why?
Thanks
Jacques
Hi Jacques,
I have added it because it is required as a "Fix for" version for patches
that are backported to the 15.12 release.
Jacopo
On Sat, Mar 19, 2016 at 10:23 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Hi,
>
> Who added the 15.12.01 unrelease
Hi,
Who added the 15.12.01 unreleased version in Jira and why?
Thanks
Jacques
14 matches
Mail list logo