Release Process

We use GitHub’s milestones to releases’ planning and anyone is free to suggest an issue to a milestone, and discuss about any issue in the next tsuru version. We also have internal goals as listed bellow and our focus will be these goals. But it’s not immutable, we can change any goal at any time as community need.

At we have goals by quarter of a year (short term goals bellow), but it doesn’t mean that there’s only one release per quarter. Our releases have one or more main issues and minor issues which can be minor bugfixes, ground work issue and other “not so important but needed” issues.

You can suggest any issue to any milestones at any time, and we’ll discuss it in the issue or in Gitter.

Next Release 0.12.0

  • Lean containers (issue #1136)
  • Dockerize tsuru installation (issue #1091)

Long term Goals

These goals are our goals to 1.0 version.

  • review platform management.

    We are thinking to change our way to manage platform. Today tsuru has your own platform. But we have a lot of problem to mantain it. In other way, we have buildpacks and we can use it to provide any platform we want, but there’s no free lunch. Buildpack can be build by any one and are updated automagicly, so your application can stop work and you’ll can do anything to fix it.

  • docker images with envs.

  • get logs and metrics from outside of app container.

  • improve app-swap

  • improve plugins