Release B@D v1.0

Issue Background

Before ELCE, release a new version of B@D box

Issue description

Ticket #37 (closed) describe the process in less detail than this task.

Gold Master declaration

• Check the licenses of the box
• Gold Master declaration

Check the task from the previous release #85 (closed)

Deployment

• Create a new folder at S3 service for the new release.
• Upload to S3 the box, metadata and artefacts
• Test integrity of the box artefacts and metadata. Execute the box.
• Add link and hashes to ticket #143
• Communicate the deployment has finished.

Check the task from the previous release #86 (closed) #96 (closed)

Documentation

• Modify the feature page to adapt it to the new release.
• Modify the download page to adapt it to the new release.
• Adapt the instructions page to the new release.
• Modify the landing page to adapt it to the new release.
• Modify the Management diagrams to reflect the 1.0 release.
• Modify the FAQ page to adapt it to the new release.

Check the tasks from previous releases: #38 (closed) #39 (closed) #40 (closed) #45 (closed) #74 (closed) #95 (closed) #105 (closed)

Marketing

• Release announcement
  • Create and review the release announcement.
  • Review and approval.
• Create the marketing material.
  • Create the social media messages in the CIP wiki.
  • Create a blog post about the release.
  • Create two slides about the release to be included in the CIP presentation.

Check the tasks from previous releases: #41 (closed) #90 (closed) #14 (closed)

Publishing

• Publish on the blog the release announcement (private) the same day so the date of the main url is right.
• Include links to the release announcement on the landing and feature pages, blog post and download page.
• Add links to the download page of the box, metadata, hashes and instructions.
• Publish the social media messages.
• Publish the release announcement as blog.
• Publish the post-release blog post.

Other tasks to review: #10 (closed) #90 (closed)

Acceptance criteria

• Link to Gold Master communication.
• Link to the communication that the deployment is done
• Link to pages when documentation is done
  • Link to the finished feature page
  • Link to the finished landing page
  • Link to the finished FAQ page
  • Link to the finished instructions page
• Link to the finished download page
• Link to the published release announcement