[Qgis-developer] backported fixes

[Paolo Cavallini]

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 master branch
> in the backporting commit, and I followed that habit as in that way
> you can tell if a commit was backported by 'git log --grep'ing for
> the commit of interest. For example (try these in 2.8 branch):

Hi Sandro,
I see your point. My aim was to give "normal" users an easy way of
discovering whether they can expect a fix in the next LTR release, or if
they have to head for next release.
All the best.

-- 
Paolo Cavallini - www.faunalia.eu
QGIS & PostGIS courses: http://www.faunalia.eu/training.html