Re: [openstack-dev] [all] Switching to longer development cycles

TL;DR: +1 for 1-year release, without reducing face-to-face meetings. On Wed, Dec 13, 2017 at 6:35 PM Matt Riedemann wrote: > > Same question as above about just doing CD then. Why not getting rid of stable branches and releases altogether then? Honestly, I'm a big fan

Re: [openstack-dev] [tripleo] Blueprints moved out to Rocky

On Sat, Dec 9, 2017 at 12:35 AM Alex Schultz wrote: > Please take some time to review the list of blueprints currently > associated with Rocky[0] to see if your efforts have been moved. If > you believe you're close to implementing the feature in the next week > or two, let

Re: [openstack-dev] [tripleo] [ci] recheck impact on CI infrastructure

Hi Emilien and all, On 16.12.2016 01:26, Emilien Macchi wrote: > On Thu, Dec 15, 2016 at 12:22 PM, Sven Anderson <s...@redhat.com> wrote: >> Hi all, >> >> while I was waiting again for the CI to be fixed and didn't want to >> torture it with additional recheck

[openstack-dev] [tripleo] [ci] recheck impact on CI infrastructure

Hi all, while I was waiting again for the CI to be fixed and didn't want to torture it with additional rechecks, I wanted to find out, how much of our CI infrastructure we waste with rechecks. My assumption was that every recheck is a waste of resources based on a false negative, because it

Re: [openstack-dev] [TripleO] Your draft logo & a sneak peek

On 27.10.2016 19:54, Ryan Brady wrote: > > How is the current draft logo expressive? What does it express to you? To me it appears like an stylized owl with a three-quarter circle as opened wings, and with lines of three nested O's. Cheers, Sven

Re: [openstack-dev] [TripleO] Your draft logo & a sneak peek

Hi all, On 25.10.2016 14:28, Ryan Brady wrote: > I feel the logo draft is missing a lot of the detail and fidelity of our > current logo. > The draft logo has lines that are much too thick especially in the face > area. It's > recognizable from a shorter distance than our current logo. > >

[openstack-dev] [TripleO] FFE request for ec2-api integration

Hi, I'm working on the integration of the puppet-ec2api module. It is a (probably) very straight forward task. The only thing that is a current impediment is that puppet CI is currently not deploying and running tempest on puppet-ec2api. I'm currently working on getting the ec2 credentials

Re: [openstack-dev] [TripleO] Austin summit - session recap/summary

Thanks a ton, Steve! I have to admit, although I was at the summit in person, I can get out of your write-up a lot more than from the sessions itself. (Probably because of a mixture of not being a native speaker and being new to tripleO.) Cheers, Sven