What are the best practices for Kiln repositories?

Question

I noticed in this image from the Kiln site that the repositories are named stable, qa and devel. Is there any reasoning behind this? Or is there a better/different way that's more accepted?

Answer 1

Have a read of this post on the Kiln StackExchange site which explains why they use stable and devel. It also suggests other ways of structuring your repositories.

We keep a devel and stable repository. New features go into devel and eventually get merged forward to stable, while bug fixes go into stable and get merged back into devel.