My Understanding of how maintenance works

| Home | Libraries | People | FAQ | More

### My Understanding of how maintenance works

There has been some discussion on the mailing list of how best to get patches available to users of libraries. This is the understanding I have been using. I posted this and have had no comments on it.

- Maintainers can have write access to the particular library for which they have responsibility. This includes all the branches and in particular both develop and master.
- It is up to the maintainer to put patches and tests onto develop and see whether there are any remaining problems.
- It is then up to the maintainer to move the patches and tests from develop to master.
  - This does not have to wait for a release of Boost.
  - It can be done any time and at some point master will then become the next release.
- I do not think that develop is moved to master in any other way. It is the maintainer who will know when that is the correct action.

If there is more than one maintainer then any of them can do this. Each will be able to see what has happened from the git log.