Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
New orgs, new repos!
3 views
Skip to first unread message
Dustin J. Mitchell
Apr 17, 2014, 6:04:19 PM4/17/14
to Announcements and development of PuppetAgain, phrawzty
The "qa" PuppetAgain organization is coming up to speed in the next few days, so it's time to get a little more serious about isolating organizations from one another.
Nobody wants to break anyone else's infrastructure, so we're going to limit the scope of change to each single organization. Each organization will have its own repository, each with a 'default' and 'production' branch. Members of each organization will check in to their own repo's default branch, and merge to production. So releng/relops will commit to https://hg.mozilla.org/build/puppet, qa folks to https://hg.mozilla.org/qa/puppet, and so on.
So far, so not surprising.
More surprising: there won't be any "canonical" repository. We'll all merge *from* the other repos as frequently as our change management allows. That allows each organization to decide when to take a particular update or change, and to resolve any conflicts. I plan to check for updates at least weekly, and try to merge whenever I learn about a substantial change in another tree.
There will still be changes that need to be coordinated across organizations, particularly when package repository changes take place. We'll use this mailing list to coordinate such changes, and try to minimize those situations.
Dustin
Nobody wants to break anyone else's infrastructure, so we're going to limit the scope of change to each single organization. Each organization will have its own repository, each with a 'default' and 'production' branch. Members of each organization will check in to their own repo's default branch, and merge to production. So releng/relops will commit to https://hg.mozilla.org/build/puppet, qa folks to https://hg.mozilla.org/qa/puppet, and so on.
So far, so not surprising.
More surprising: there won't be any "canonical" repository. We'll all merge *from* the other repos as frequently as our change management allows. That allows each organization to decide when to take a particular update or change, and to resolve any conflicts. I plan to check for updates at least weekly, and try to merge whenever I learn about a substantial change in another tree.
There will still be changes that need to be coordinated across organizations, particularly when package repository changes take place. We'll use this mailing list to coordinate such changes, and try to minimize those situations.
Dustin
0 new messages