dandax
Reputation: 1267
What are the best practices for Kiln repositories?
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?
Upvotes: 5
Views: 1050
Answers (1)
Pauk
Reputation: 2631
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.
Upvotes: 5
Related Questions
- Best practice for maintaing K8S resources in github
- Why Kiln is based on Mercurial, and not other (D)VCS
- Best practice for organizing Kubernetes objects across multiple git repos?
- Best practices for git repositories on open source projects
- Shrinking Mercurial repo size (manifests in particular)
- How do I clone/pull from GitHub, but push to Kiln?
- Automated sync between Github and Kiln
- Mercurial/Kiln: Compare local with remote, separate repositories?
- Embedding a github repository inside a mercurial (kiln) repository - how integrated is it?
- "factorizing" a mercurial repository on kiln