[GRASS-dev] [OSGeo/grass] r.in.wms: write string not bytes to capabilities file (#195)

GRASS GRASS developer
1

Hi Stefan,

On Fri, Nov 15, 2019 at 7:56 PM Stefan Blumentrath <notifications@github.com> wrote:

Merged #195 into master.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

…was this not backported on purpose?

I would invite all devs to:

  • either backport themselves,
  • or clearly indicate: do not backport,
  • or state: pls someone backport it (seems to be mostly me but that’s ok), there is a PR label for that.

We missed in 7.8.1 an important backport exactly due to this unclear situation.

I am not keen on manually compare every PR to see if it was backported or not…

thanks,
Markus

2

Sorry. It had a backporting label and I thought there was an auto-backport running…

But I can backport this one tonight. Good to learn how to backport anyway (it is well documented on the wiki).

Cheers
Stefan

···

Fra: Markus Neteler neteler@osgeo.org
Sendt: lørdag 16. november 2019 11:51
Til: Stefan Blumentrath Stefan.Blumentrath@nina.no
Kopi: GRASS developers list grass-dev@lists.osgeo.org
Emne: Re: [OSGeo/grass] r.in.wms: write string not bytes to capabilities file (#195)

Hi Stefan,

On Fri, Nov 15, 2019 at 7:56 PM Stefan Blumentrath <notifications@github.com> wrote:

Merged #195 into master.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

…was this not backported on purpose?

I would invite all devs to:

  • either backport themselves,
  • or clearly indicate: do not backport,
  • or state: pls someone backport it (seems to be mostly me but that’s ok), there is a PR label for that.

We missed in 7.8.1 an important backport exactly due to this unclear situation.

I am not keen on manually compare every PR to see if it was backported or not…

thanks,
Markus

3

On Sat, Nov 16, 2019 at 12:03 PM Stefan Blumentrath
<Stefan.Blumentrath@nina.no> wrote:

Sorry. It had a backporting label and I thought there was an auto-backport running...

Glad you got this impression :smiley:

But I can backport this one tonight. Good to learn how to backport anyway (it is well documented on the wiki).

It is very easy with cherry-picking:
https://trac.osgeo.org/grass/wiki/HowToGit#Backportingtoreleasebranches

To enable auto-backporting is probably dangerous but others may know
more about it.

Best
Markus