Today's meeting brought up sourceforge support for download stats as being
useful. GitHub provides a download count, but not the region and operating
system specific breakdown.
--
Jody Garnett
On 2 October 2017 at 11:09, Torben Barsballe <[email protected]>
wrote:
> Hello All,
>
> This latest release has been fraught with peril (as is usual for RC1
> releases). Now that it is complete, there are a few things I wanted to
> bring up:
>
> *Migration to build.geoserver.org <http://build.geoserver.org>*
>
> Over the past few months, we have been gradually migrating to
> build.geoserver.org as our new build server. As of now, I believe the
> only remaining builds not fully migrated are the cite tests.
>
> - When constructing the 2.12 jobs for the new stable branch, I have
> only added them to build.geoserver.org. Unlike most of the other jobs
> on there, I have set them up to notify the mailing lists if they fail. Now
> that build.geoserver.org is more stable, we should consider swapping
> other notifications from ares to build.geoserver.org.
> - When updating the GeoServer download page (geoserver.github.io), I
> have updated all nightly builds to point to build.geoserver.org
> instead of ares. Both new and historical builds seem to work.
> - When updating the doc links on docs.geoserver.org, I attempted to
> change the nightly builds to link to build.geoserver.org instead of
> ares. I was unsuccessful, as build.geoserver.org only supports https,
> and docs.geoserver.org only supports http. I have added a 2.12 nightly
> doc build to ares for now. A long-term solution may involve migrating
> docs.geoserver.org, perhaps to a github pages site.
>
> *SourceForge outage*
>
> The SourceForge outage midweek caused a delay in the release, along with
> other chaos, like temporarily knocking out the mailing lists.
>
> - We should revisit using SourceForge to host artifacts. GitHub
> supports attaching artifacts to releases; besides the time required to set
> this up, does anyone know of any compelling reasons not to use this feature
> for GeoTools, GeoWebCache and GeoServer releases? It seems fairly easy to
> use.
>
>
> *Doc updates*
>
> When going through the release procedures, I found a few issues, and have
> updated them accordingly. PRs available for review:
>
> - https://github.com/geotools/geotools/pull/1708
> - https://github.com/geoserver/geoserver/pull/2553
>
> *Windows and Mac build*
>
> - The windows build on build.geoserver.org is now fully automatic, and
> integrated with the regular release procedure.
> - The mac build still requires some manual steps from someone with
> access to the Boundless desktop-ci jenkins build box.
>
>
> Torben
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
