[QGIS-Developer] 3.4 backports

[Nyall Dawson]

On Tue, 17 Sep 2019 at 09:28, Nathan Woodrow <madmanwoo at gmail.com> wrote:
>
> Is it easy to disable the auto backport and have it just create the pull request and tag someone?  That way it can still be semi-automatic but with some human checks

That's what it does -- it creates the PR, but the PR can't be merged
without someone (other than the original developer) approving it.

I'm seeing a lot of backports which the bot can't auto create over the
last week, where devs have manually backported... yet the validity of
the backport is questionable and I'd hate to see wasted effort going
into manual backports which won't be accepted.

Nyall


>
> On Tue, Sep 17, 2019 at 9:06 AM Nyall Dawson <nyall.dawson at gmail.com> wrote:
>>
>> Hi all,
>>
>> Just a quick plea that during this freeze period please think
>> carefully about the suitability of backporting fixes to 3.4. At this
>> stage in its lifecycle 3.4 should only receive absolutely mission
>> critical fixes (such as crash fixes or data corruption issues).
>>
>> The consequence of regressions in 3.4 caused by backporting minor bug
>> fixes much outweighs the benefits of fixing these bugs. While the
>> backport label makes 3.4 backports easy to do, it does not guarantee
>> their safety or suitability.
>>
>> Thanks!
>> Nyall
>> _______________________________________________
>> QGIS-Developer mailing list
>> QGIS-Developer at lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer