On Wed, Jun 03, 2015 at 09:43:31PM +0200, Matthias Kuhn wrote:
The ticket system sounds like a good place to manage this information.
In comparison to the commit in master the ticket can be altered later
on. And is referenced from the commit in master if that's the starting
point of the
On 06/03/2015 09:26 PM, Sandro Santilli wrote:
On Wed, Jun 03, 2015 at 06:29:36PM +0200, Paolo Cavallini wrote:
Il 03/06/2015 10:17, Sandro Santilli ha scritto:
The problem I see is by requiring [BACKPORTED] tag in the commit
to master you're basically preventing to test fixes in master
On 06/03/2015 10:11 PM, Sandro Santilli wrote:
On Wed, Jun 03, 2015 at 09:43:31PM +0200, Matthias Kuhn wrote:
The ticket system sounds like a good place to manage this information.
In comparison to the commit in master the ticket can be altered later
on. And is referenced from the commit in
On Wed, Jun 03, 2015 at 06:29:36PM +0200, Paolo Cavallini wrote:
Il 03/06/2015 10:17, Sandro Santilli ha scritto:
The problem I see is by requiring [BACKPORTED] tag in the commit
to master you're basically preventing to test fixes in master branch
before deciding if it's safe or not to
Hi Nyall
Thanks for your input. I'll back in the office tomorrow and can give you
more detailed answers to the technical questions.
To the technical issues:
Yes, I plan to fix them in the next time, but definitely before release
( fixed #12857 and started to look at #12836 already). I think
On Wed, Jun 03, 2015 at 07:56:53AM +0200, Paolo Cavallini wrote:
Il 03/06/2015 07:53, Nyall Dawson ha scritto:
I've been thinking about this... Do you think it's worthwhile to hold
off on back porting 2.10 freeze fixes until after release? That way we
get extra testing of these before
Il 03/06/2015 10:17, Sandro Santilli ha scritto:
The problem I see is by requiring [BACKPORTED] tag in the commit
to master you're basically preventing to test fixes in master branch
before deciding if it's safe or not to backport.
I saw Jurgen referencing the commit identifier of the
Il 03/06/2015 23:09, Matthias Kuhn ha scritto:
`git branch --contains {sha}` should return release-2_8 for a backported
commit.
But I have no idea how this plugin works and who maintains it :)
Agreed, better on tickets than on git.
Antway, this is an important info, if we want to be serious
