The release process

Work in progress. Please contribute

This page is build as a reminder/to-do list on what should be done to dreate a new "Sloeber".

The steps to make a new release as follows:

• Update the version numbers in the manifest, xml and pom files
• run the unit tests
• run the upload tests
• try a upgrade from a previous stable release
• Update the sloeber.io web site
• Make a release in github
• update the stable update site on sloeber.it
• Share with the world.

---

Lets go into detail for each of these steps:

Update the version numbers in the manifest, xml and pom files

In eclipse update for all project the pom.xml file
For the pojo projects update the manifest.MF file
For the feature projects update the feature.xml file
For the product projects update arduino.product

If all of this has been done correctly mvn verify should run ok and the build product should reference the new version numbers.
If so check-in the changes and push to github.

##There are plenty of unit tests to be run. By cheking in before running the unit tests the test can be run on several systems and os'es at the same time.
Most of the long running tests do not have 100% success rate.

Update the web site

Sloeber.io points to eclipse.baeyens.it and eclipse.baeyens.it is updated via the github repository and the nightly build on Jantjes Build server. In general this is a good time to check if everything is still "acceptable" on the website.
But for sure:
Update the globals.txt file to reflect the new version number. Update the index.shtml page to share the good news. Add the newly released files to fragments/files.php Update the fragments/navbar.html to contain a extra archived version Check nightly.php and stable.php to work correctly.

push your changes to github.

Make a release in guthub

Make a new release X_Y on github. (do this after you updated the web site and after a successfully nightly build on jantjes server, so the updated site is tagged correctly)
On Jantjes Build server: Rename the nightly build product files (5 in total) by adding VX.Y_ in front of the nightly build. X stands for the major version Y stands for the minor version.
It needs to be jantjes build server as Jantjes build server adds jre folders for the windows releases.
Upload the 5 files mentioned earlier to the release On github rename the label "status: fixed in nightly" to "status:fixed in release X.Y" and create a new label "status: fixed in nightly"
Of course you need the right credentials to do so.

update the update site on baeyens.it

Prerequisites

• Jantjes build server workspace is accessible as file system
• You have read and write permissions to the workspace
  Step 1
  Download the VX folder from ftp.baeyens.it/eclipse/update/VX/stable
  Start your sloeber development environment (pde not cdt)
  open the workspace on the build server
  right click on the io.sloeber.updatesite and select export
  select plug-in development->deployable features->next in available features select io.sloeber.feature
  in destination select the downloaded Vx folder
  in options make sure the source is not selected and "use class files compiled in the workspace" is selected
  select finish
  wait until done On baeyens.it rename the VX update site for backup reasons upload the VX folder to ftp.baeyens.it/eclipse/update/VX/stable

The eclipse market place.

Updating the eclipse market place is also a good idea. As we are at it. Do both the product and the plugin version. It is also a good idea to tweet about the new releas.