-
Notifications
You must be signed in to change notification settings - Fork 131
The release process
Work in progress. Please contribute
This page is build as a reminder/to-do list on what should be done when a new "Arduino eclipse plugin V2" release is created. The basic idea of the new release creation process is that the new release is created after the release is published. This makes that the nightly is ready to be released. This makes the steps to make a new release as follows:
- Publish and tag the nightly build packages as a new release
- Create a Marker in github so we know what code has been used for the release.
- Update the plugin so it reflects it is a new release.
Lets go into detail for each of these steps:
From a delivery point of view there are 3 locations that must be updated.
- The stable product version on eclipse.baeyens.it
- The V2 update site on eclipse.baeyens.it
- The eclipse.baeyens.it web site
- The eclipse market place.
To release a stable version on eclipse.baeyens.it renaming 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. The files location on the server is eclipse/download/product. Of course you need the right credentials to do so.
Making a update site in eclipse is easy but I do not know how to expand an existing update site. The V2 update site is located at eclipse/V2/
The web site is updated via the github repository and the nightly build. The change involves the remind pages. rename V to V+1 rename V-1 to V copy V-2 to V-1 Note that the above description is a mental description and does not necessarily is the physical action that needs to take place. It is also a good idea to tweet about this so the home page reflects the new release.
Updating the eclipse market place is also a good idea. As we are at it. Do both the product and the plugin version.
Input please
Change the link to the remind page