Re: [GRASS-dev] [release planning] GRASS GIS 8.2.1
Hi devs, On Thu, Oct 20, 2022 at 1:30 PM Markus Neteler wrote: > > Hi devs, > > It is time to release 8.2.1 as a number of fixes and improvements have > accumulated. For a list, see > > https://github.com/OSGeo/grass/compare/8.2.0...releasebranch_8_2 > > We still have open issues remaining related to the 8.2.1 milestone: > https://github.com/OSGeo/grass/milestone/17 > > Here the open PRs related to the 8.2.1 milestone: > https://github.com/OSGeo/grass/pulls?q=is%3Aopen+is%3Apr+milestone%3A8.2.1 > > Please check issues and PRs and bump those not being addressed for > 8.2.1 to the 8.3.0 milestone. > > I would like to prepare 8.2.1RC1 next week. Meanwhile 70 commits made it into the upcoming 8.2.1RC1. I try to prepare RC1 in the next days. Markus -- Markus Neteler, PhD https://www.mundialis.de - free data with free software https://grass.osgeo.org https://courses.neteler.org/blog ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] [release planning] GRASS GIS 7.8.8
Hi devs, all, On Sun, Jul 3, 2022 at 11:01 PM Markus Neteler wrote: > On Thu, Jun 16, 2022 at 2:13 PM Martin Landa wrote: > > Dear all, > > > > 7.8.8RC1 was released on May 14. There is one open issue [1]. Do we plan to > > release 7.8.8 anyway? > > Yes, we do asap. Well, some months have passed... > > > > [1] https://github.com/OSGeo/grass/milestone/14 Since RC2 more fixes came in: https://github.com/OSGeo/grass/compare/7.8.8RC2...releasebranch_7_8 Shall we prepare RC3 next? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] GitHub backport label proposal
Markus, Please go ahead with new labels for backport, let’s start with “backport [branch name]”. If it becomes too noisy, it is easy to change (ie. the label names). Best, Nicklas > On 22 Nov 2022, at 21:40, Even Rouault wrote: > > > Le 22/11/2022 à 19:51, Nicklas Larsson a écrit : >> Looks like a clever little bot. In case that is the way the community choose >> to go then the label will have to be “backport releasebranch_8_2”, which is >> very long… >> I also wonder how useful it would be at the moment for GRASS, e.g. wide >> ranging indentation changes often causes conflicts between main and latest >> release branches. > > Sure the bot just tries to git cherry-pick commits, and if they don't apply > cleanly, it obviously fails, with reports like > https://github.com/qgis/QGIS/pull/50943#issuecomment-1322647971 > > > -- > http://www.spatialys.com > My software is free, but my time generally not. > ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
