We can still use scheduled release as we do now and yet have some agility. An idea was passed around before if we can modularize ACS in future releases VS being it monolithic.
We can still have a core as is, but additional components/plugins can be loaded adhoc pm the need base. As an example, there is no need to bake in vmware support into release if a customer has not need for it. You cant just upgrade vmware code unless you upgrade from version X.y.1 to X.y.2. Same applies to all other "plugins", that are not truly pluggable. Splitting components as separate "plugins" (or whatever the proper term is) would ease the release cycle and give us flexibility in my opinion. > -----Original Message----- > From: Daan Hoogland [mailto:daan.hoogl...@gmail.com] > Sent: Tuesday, September 24, 2013 12:22 PM > To: dev > Subject: Re: [PROPOSAL] move away from time-based releases and/or > revamp release process > > is this work a workshop to get at least a core group of us in line. We all > have > ideas and a lot of good ones are buried under an ton weighing archive of > mails. > > Daan > > On Tue, Sep 24, 2013 at 6:06 PM, Chip Childers <chip.child...@sungard.com> > wrote: > > On Tue, Sep 24, 2013 at 10:00:32AM -0600, Marcus Sorensen wrote: > >> I guess I'm in the minority though, since we're the only ones > >> discussing it. > > > > No you are not. Personally, I'm thinking about this problem a bit > > before adding my 2 cents. Don't take that silence as thinking we are > > "ok". > > > > Short version of my thoughts: > > > > 1 - a schedule is really important to a project like this > > 2 - not releasing crap quality is really really important to a project > > like this > > > > Note the "really" vs. "really really". > > > > -chip
