Hi Kevin,
I've found this page of documentation, believe is what you were referring
to:
https://sourceforge.net/p/forge/documentation/GitHub%20Importer/#releases
Automatic imports would be cool indeed. We just need to figure out how they
match with our current release
file system structure
Cheers
On the subject of migrating away from Source Forge for hosting
installation artifacts, I just noticed that SourceForge has the option
to automatically pull in the artifacts from GitHub releases. This might
simplify transitioning to GitHub while still using SourceForge as a backup.
On 2018-03-06
I like that idea, we would need to coordinate with OSGeo slack with respect
to migrating mailing lists.
--
Jody Garnett
On 6 March 2018 at 13:32, Torben Barsballe
wrote:
>
>
>
>
>
>
>
> *SourceForge had outages / reduced service during the week of the GeoTools
> 19-beta / GeoServer 2.13-beta re
*SourceForge had outages / reduced service during the week of the GeoTools
19-beta / GeoServer 2.13-beta release.This caused: - Delays on mailing list
discussions and announcements (including the release announcement), - Loss
of all download statistics for the release, so we don't know how many
peo
