On Tue, Jul 09, 2013 at 05:56:24PM +0000, Edison Su wrote: > > > > -----Original Message----- > > From: John Burwell [mailto:jburw...@basho.com] > > Sent: Tuesday, July 09, 2013 7:53 AM > > To: dev@cloudstack.apache.org > > Cc: 'Chip Childers' > > Subject: Re: Swift in 4.2 is broken, anybody wants it to be supported in > > 4.2? > > > > Edison, > > > > As I read through this thread, we seem to be conflating the following > > topics: > > > > 1. Feature regression testing per release cycle > > 2. Identifying and back porting defect fixes to previous releases > > 3. Feature removal process > > > > To my mind, these topics are completely unrelated. We have regression test > > and defect triage processes to address items 1 and 2. If you feel that they > > can be improved, then we should discuss those improvements in a separate > > thread. No community or system will be perfect. I believe the best we can > > do is seek to do it better today than yesterday. To that end, observing > > that > > we did something poorly in the past does not justify continuing to do it > > poorly or removing a feature on which users are relying. > > > > > > I am concerned about item 3 -- the merge of a feature removal without > > community consensus. If you *think* a feature is broken in a previous > > This feature is not been tested since about one and half year ago, nobody > knows the status of swift integration. > If we can't claim to support Swift in 4.0, 4.1, then why you think I am > removing a feature?
But we *do* claim that support. See [1]. Not having tested it is *not* the same as saying that it isn't supported. [1] http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.1.0/html/Installation_Guide/about-secondary-storage.html
