Re: Eirini in 2019 CFAR certification requirements


Simon D Moser
 

+1. Our main intent certainly was to avoid certification FUD in case we accomplish a "mature" Eirini in the first half or 2019. To me ammeding the requirements with a mid-term update does address this, so I'm fine with that.

Mit freundlichen Grüßen / Kind regards

Simon Moser

Senior Technical Staff Member / IBM Master Inventor
Bluemix Application Platform Lead Architect
Dept. C727, IBM Research & Development Boeblingen

-------------------------------------------------------------------------------------------------------------------------------------------
IBM Deutschland
Schoenaicher Str. 220
71032 Boeblingen
Phone: +49-7031-16-4304
Fax: +49-7031-16-4890
E-Mail: smoser@...
-------------------------------------------------------------------------------------------------------------------------------------------
IBM Deutschland Research & Development GmbH / Vorsitzender des
Aufsichtsrats: Martina Koederitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht
Stuttgart, HRB 243294

*******

ITIL has led people to think in siloes ("go fix change management").
Project Management has led people to think in finite units of work instead of streams of product.
Both are fundamental dysfunctions of the framework model, not failures of execution.
       ⁃        Rob England




From:        "Troy Topnik" <troy.topnik@...>
To:        cf-dev@...
Date:        04/12/2018 21:12
Subject:        Re: [cf-dev] Eirini in 2019 CFAR certification requirements
Sent by:        cf-dev@...




That sounds reasonable. I was going to add some "pending feature parity and passing CATs" language in the proposed change, but ammeding the requirements with a mid-term update would probably satisfy our needs without introducing conditional clauses.

Thanks for the feedback.

TT



Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.