Re: [DISCUSS] More Versioning Discussion

2014-04-18 Thread Josh Elser
A passing thought, but when we get to "real" bug fix releases, I'd like to see the testing burden reduced. If there's only bug fixes, we need only test that those are fixed and don't need to hold ourselves to the week of testing IMO. Hopefully unit and integration tests would be sufficient, but I

Re: [DISCUSS] More Versioning Discussion

2014-04-18 Thread Mike Drob
On Fri, Apr 18, 2014 at 11:42 AM, Christopher wrote: > On Fri, Apr 18, 2014 at 10:43 AM, Sean Busbey wrote: > > I know this got very long, especially for a Friday. Please bear with me. > > > > > > On Thu, Apr 17, 2014 at 5:56 PM, Christopher > wrote: > > > > > >> You seem to keep insisting that

Re: [DISCUSS] More Versioning Discussion

2014-04-18 Thread Christopher
On Fri, Apr 18, 2014 at 10:43 AM, Sean Busbey wrote: > I know this got very long, especially for a Friday. Please bear with me. > > > On Thu, Apr 17, 2014 at 5:56 PM, Christopher wrote: > > >> You seem to keep insisting that we don't have consensus on basic API >> >> guarantees. I don't think tha

Re: [DISCUSS] More Versioning Discussion

2014-04-18 Thread Sean Busbey
I know this got very long, especially for a Friday. Please bear with me. On Thu, Apr 17, 2014 at 5:56 PM, Christopher wrote: > You seem to keep insisting that we don't have consensus on basic API > > guarantees. I don't think that's true. We may not have a complete > policy, but I think we hav

Re: [DISCUSS] More Versioning Discussion

2014-04-18 Thread David Medinets
As long as v1.4.2 client code is compatible with all subsequent releases, I foresee no problems. Or write a 1.4.2 to 1.X.X proxy layer. *this is a poe* On Thu, Apr 17, 2014 at 11:05 PM, Christopher wrote: > That's a fair point, but the main point I was trying to make using > that example was

Re: [DISCUSS] More Versioning Discussion

2014-04-18 Thread Christopher
That's a fair point, but the main point I was trying to make using that example was that there are concrete efforts which have been made to inch closer to better compatibility guarantees, and compatibility... specifically within a supported release line... is something that we routinely consider an

Re: [DISCUSS] More Versioning Discussion

2014-04-17 Thread Mike Drob
For a little bit of historical context - when filing ACCUMULO-751 to ask for wire compatibility, I had no intention of providing both forward and backwards compatibility. I really wanted the ability to do rolling upgrades where I could upgrade tablet servers one-by-one and not have suffer any clust

[DISCUSS] More Versioning Discussion

2014-04-17 Thread Christopher
Sean comment on ACCUMULO-2343: https://issues.apache.org/jira/browse/ACCUMULO-2343?focusedCommentId=13973504&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13973504 I was going to comment in IRC or in response in JIRA, but I think this would better serve the group to