On 10 November 2013 19:22, Andy Doan <[email protected]> wrote: > I've never played the role of a grumpy old guy before, but I'm going to try: > > How about we *not* use a code name and just call this what it is or will be? > Codenames just cause confusion over the long run and nobody will have a clue > what I'm talking about when I tell them I've spent 6 months working on > <insert your obscure reference here>. Let's just call it the CI-engine or > something along those lines, start a BZR repo and use monthly milestones.
Hi Andy, That's an entirely valid point, and apologies for creating confusion. To be clear, I wasn't suggesting we use this in public-facing materials. The Ubuntu Error Tracker components have had the codenames whoopsie and daisy(.ubuntu.com) since the outset, but we publically refer to it as the Error Tracker. I suggested this as an exercise to hopefully get everyone a bit more excited about the project. If you're just itching to get started though, we can most certainly go ahead and create an official project in Launchpad with a bzr repository. Do note that we should have the month-by-month milestoning done by this Thursday so we can start creating the core services, their juju charms, and tests. I've put Siva, Vincent, and Ursula on that this morning and my hope is that when the rest of you return from holiday you'll have a good set of plans to build on. I'm itching to dive into code and see this start to take shape, but I want to get a clear indication from you guys that we've planned this out as best we can and everyone has a clear understanding of what needs to be done. Sound good? -- Mailing list: https://launchpad.net/~canonical-ci-engineering Post to : [email protected] Unsubscribe : https://launchpad.net/~canonical-ci-engineering More help : https://help.launchpad.net/ListHelp
