Page History

...

The artifacts to be uploaded to Sourceforge, as well as PGP signatures, SHA1 checksums, file sizes, etc., can be found at the central Maven repository search site: http://search.maven.org/#search%7Cga%7C1%7Corg.fcrepo.

The Fedora Messaging client can be found at http://search.maven.org/#search%7Cga%7C1%7Cfedora-client-messaging.

Files sent to sourceforge and linked directly from the documentation's Download page should include:

For each file, also add a *.asc file, containing the PGP signature for the file, as created by Maven and stored in the central repository.

...

If this is a maintenance point release, create separate child release note pages for each release covered by the documentation (see https://wiki.duraspace.org/display/FEDORA36FEDORA38/Release+Notes for an example).
Otherwise, post the release notes in the Release Notes page (see https://wiki.duraspace.org/display/FEDORA35/Release+Notes for an example).

...

Make sure the license and copyright information is up-to-date with this release.

Update the Fedora Commons wiki

Fedora Commons Wiki (Plone): http://www.fedora-commons.org/
Sitemap: http://www.fedora-commons.org/sitemap

...

• navigate to Previous Releases folder
• select green view tab
• select display drop-down menu
• select change content item as default view...

...

• select Manage Portlets
• select the Current Releases portlet.
• update the link to the installer: http://downloads.sourceforge.net/fedora-commons/fcrepo-installer-X.Y.jar
• update the link to the source: https://github.com/fcrepo/fcrepo/zipball/vX.Y

...

release

...

In the Software section:

• Make sure the default view for the Fedora Repository reflects the new release
• Update the previous version to point to the archived documentation
• Make sure the license information is up-to-date with the latest release

On the homepage:

...

.

Announce release

Let Carol Minton Morris (clt6 at cornell dot edu) know that the release is complete and can be announced.

...