Update website for 2.0.0 release

bitsgalore commented 5 years ago

Branch here:

bitsgalore commented 5 years ago

As part of this, harmonise contents of this page:

with jpylyzer's general README, because now this information can be found in 3 places in 3 slightly different formats (readme, usage page, manual).

UPDATE - fixed by https://github.com/openpreserve/jpylyzer/commit/9fb5274698d5728ea334f0d1247c22203702e7fe; info from README now identical to usage.md so sections can simply be copied over.

bitsgalore commented 4 years ago

Since there will be a release candidate before the release, things will get slightly more complex, but the following steps should do the trick:

By publishing time of release candidate

Publish 2.0.0 XSD Schema to gh-pages branch - done
Publish 2.0.0 docs to gh-pages branch (using -2-0-0rc1 file name suffix, since we don't want this to replace the docs of the current stable 1.18 release at this stage!) - done
Write announcement/blog on jpylyzer website with links to all packages and docs. DON'T change any of the main links (right-hand column) at this stage because this is not a stable release - done, see here (TODO: add links to downloads)
Agree on publishing date/time

In branch gh-pages-2-0-0, update links to published packages
Copy over rc announcement blog post from gh-pages (see above), but change links to rc-specific documentation files to the regular documentation.
Remove the documentation files that are specific to the release candidate
Write release announcement blog.
Merge content of branch gh-pages-2-0-0 into gh-pages (might need some manual merge conflict resolving)

bitsgalore commented 4 years ago

Also, remove separate AMD64/i386 icons for the Debian packages, as we now only have 1 package as per https://github.com/openpreserve/jpylyzer/issues/117.