[gdal-dev] process for adding commits to minor release

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[gdal-dev] process for adding commits to minor release

Norman Barker-2
Hi,

I was looking at the recent 3.0.2 release and it was missing a few of my commits for the TileDB driver dating back to June. How do I get these added to the 3.0.x series, I understood the backport function to be for bug fixes?

Norman

_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: process for adding commits to minor release

Even Rouault-2
On mardi 5 novembre 2019 14:48:19 CET Norman Barker wrote:
> Hi,
>
> I was looking at the recent 3.0.2 release and it was missing a few of my
> commits for the TileDB driver dating back to June. How do I get these added
> to the 3.0.x series, I understood the backport function to be for bug fixes?

When you create a pull request, you can add the "backport 3.0" label if you
want a backport pull request to be created after the initial pull request has
been merged to master.

If the changes are already in master, git cherry-pick them manually in
release/3.0 (possibly creating in a branch to create a pull request against
release/3.0 so that it gets CI tested)

Even

--
Spatialys - Geospatial professional services
http://www.spatialys.com
_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Reply | Threaded
Open this post in threaded view
|

Re: process for adding commits to minor release

Matthias Kuhn 🌍
Hi

On 11/5/19 9:54 PM, Even Rouault wrote:

> On mardi 5 novembre 2019 14:48:19 CET Norman Barker wrote:
>> Hi,
>>
>> I was looking at the recent 3.0.2 release and it was missing a few of my
>> commits for the TileDB driver dating back to June. How do I get these added
>> to the 3.0.x series, I understood the backport function to be for bug fixes?
> When you create a pull request, you can add the "backport 3.0" label if you
> want a backport pull request to be created after the initial pull request has
> been merged to master.
>
> If the changes are already in master, git cherry-pick them manually in
> release/3.0 (possibly creating in a branch to create a pull request against
> release/3.0 so that it gets CI tested)

You can also add the label if it has been merged already, this will
trigger the backport as well.

Matthias

>
> Even
>
_______________________________________________
gdal-dev mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/gdal-dev