[Qgis-developer] Backport necessary fixes to release-2_2 branch?

Tim Sutton lists at linfiniti.com
Mon Mar 10 12:42:16 PDT 2014


On Mon, Mar 10, 2014 at 7:50 PM, Larry Shaffer <larrys at dakotacarto.com>wrote:

> Hi,
> After recent discussions, it was my understanding that...
> * we could backport necessary fixes to the release-2_2 branch
> * there would be no point release, or even additional tagging, only an
> available source branch
> Am I correct?

We discussed it on IRC [1] at this month's PSC meeting and basically it is
still unconcluded - but we are working on figuring out a good strategy for
bug fixes - Juergen's domain obviously so he can comment more once there is
a concrete plan of action.

> If not, are we really expected to maintain a set of external patch files
> for packagers willing to roll out these fixes?
> No I don't think so.

> What about automatic installers that can pull directly off of that branch,
> e.g. Homebrew on Mac? Surely those maintainers aren't expected to track and
> maintain a set of externally hosted patch files for those as well.
Nope we want to avoid that. AFAIK there is nothing stopping your pushing
fixes to the release branch already, the issues are more about quality and
cadence of bugfix releases.



> Regards,
> Larry
> _______________________________________________
> Qgis-developer mailing list
> Qgis-developer at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/qgis-developer

Tim Sutton - QGIS Project Steering Committee Member
Please do not email me off-list with technical
support questions. Using the lists will gain
more exposure for your issues and the knowledge
surrounding your issue will be shared with all.

Irc: timlinux on #qgis at freenode.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20140310/154821ef/attachment.html>

More information about the Qgis-developer mailing list