A release volunteer for the July update is welcomed - do you have time to
help? The release schedule is here
https://github.com/geoserver/geoserver/wiki/Release-Schedule
I also note that foss4g is occurring right around when we make the RC; I am
considering making a milestone release for a foss4g
Some good news:
1. https://trac.osgeo.org/osgeo/ticket/2416 transfer of domains
Planet has transferred the geoserver.org domain to osgeo.
2. osgeo sys admins have made a new dns record for geoserver.org and
friends:
geoserver.org/www.geoserver.org 185.199.110.153
build.geoserver.org (144.76.16
Hi Andrea,
thank you for the feedback, find my replies below:
On Mon, Jul 4, 2022 at 5:25 PM Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:
> Hi all,
> I can understand the desire to use a more structured format rather than
> fiddling with escape codes when dealing with
> complex view pa
As you said, the main branch for sure.
About the other branches, it's really up to you.
Personally I try to stay on main for as long as I can, less overhead with
backports and the like, but
it also means less users interested in trying out the module since that's
the development series
Cheers
Andr
Hi Andrea,
Yes, sure !
I must admit I was a bit surprised you would give direct commit access ;o)
Which branch(es) should I target ? main, of course, but should I also
submit a PR on latest release for instance ? Or 2.21.x branch ?
Cheers,
Jean
*Jean Pommier -- pi-Geosolutions*
Ingénieur,
Marco Volpini (
https://osgeo-org.atlassian.net/secure/ViewProfile.jspa?accountId=5a129c3cb35ed9014cf6b480
) *created* an issue
GeoServer (
https://osgeo-org.atlassian.net/browse/GEOS?atlOrigin=eyJpIjoiNzIyMmNmZDA1NjJkNDQ4MTgwOGNlZDIxYzM3MzVlYzQiLCJwIjoiaiJ9
) / Improvement (
https://osgeo-or
