On Thu, May 7, 2015 at 12:10 PM, Dan Smith <[email protected]> wrote: >> > In which case, the question is whether to do this now/soon (before >> > proliferation of branches) or later (and try to coordinate rebases & >> > merges if there's branches in progress). >> > >> > I am in favour of doing it early. >> > > One point on this is that there is still lingering work on the > pivotal/GemFire side to get some features that are currently under > development into the open source - so there are actually several feature > branches already (albeit not yet in the open source codebase).
On that note, can you guys please at least file all the JIRAs to describe what's coming? I see you filed a few, but perhaps it would be helpful to create an umbrella JIRA so we can track those pending changes. Also, I expect that this is the last time a bulk update is coming, right? Now that we're fully enabled on ASF infrastructure there's no reason for us to not starting to follow the usual process which is: commit early commit often ;-) > When we do start renaming, we need to investigate how to do it in a way > that is backwards compatible, at least at a client/server messaging level > if not API, peer-to-peer, etc. Agreed. That's actually good timing -- since it'll give us time to explore the options while you guys will commit the missing bits that rely on old naming. Thanks, Roman.
