Skip to content
mpvader edited this page May 27, 2018 · 21 revisions

A new release is, on average, made every two months. Note that those two months are not strict: we take an opportunistic approach.

A new cycle starts with including various

develop, testing, candidate and release

Develop:

Once all is in master, we trigger an automatic build. When successful, all output is uploaded to the develop feed.

There is a small number of test systems configured to update from that feed. There after,

Release:

Lastly, when we give the green light, the version is shortened to the format for official releases, see for example here. A new build is triggered and then tested (from the develop feed); and thereafter pushed to testing, candidate and release.

merge cycle

An example to show the full process.

  1. The fix has been implemented
  2. It’s reviewed, and pushed to the master branch of the project. example
  3. A new version of gps-dbus is released (version no changes in codes, tagged and pushed). example
  4. The change is listed on the Todo page; in the section that holds the queue for the Venus maintainer. Including link to an issue, if there is one, and a description. When it’s a bugfix, then include the version number at which the bug was introduced.
  5. Venus maintainer changes the bitbake recipe to the new version. example
  6. And possibly also includes other changes.
  7. Venus maintainer increases the build number (v2.2012 to v2.2013 for example); and triggers a build. example
  8. The build is now in the Develop-feed. Maintainer tests it and pushes to testing.
  9. All contributors test the version in testing for their changes: are they properly included and all OL?
  10. When all Ok, maintainer pushes to candidate

Lastly, after several of such cycles, the version is made official (for example v2.20~18 is changed to v2.20) and pushed to the Release feed. Also a blog is made, the todo list wiki page is prepared for the next cycle, developer changelog copied into its own separate page. Also the public changelog, available for customers via https://professional.victronenergy.com, is updated.

Todo: add git log of example project and git log of meta-victronenergy.

Clone this wiki locally