Packaging renaming has a few interesting, perhaps unexpected effects on the community. It breaks:
1) API backwards-compatibility 2) Client/Server backwards-compatibility 3) Rolling upgrades These qualities have typically been rather important within the GemFire community. Although the GEODE community is just starting up I’m expecting a fair bit of cross-over. Any thoughts on how to handle this? Assuming we do move ahead with pkg renaming it should be a singular and well-known event that occurs prior to a binary release of GEODE. Anthony > On May 7, 2015, at 3:54 AM, Pid <[email protected]> wrote: > > On 07/05/2015 11:40, Justin Erenkrantz wrote: >> Yes, it is expected that these will be renamed by the time Geode is ready >> for graduation from the Incubator. >> >> Years ago, we tried to make projects do this type of rename before >> incubation and it was silly. So, it is now one of the key criteria for >> exit - not entrance. > > 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. > > > p > > >> Cheers. -- justin >> On May 7, 2015 6:05 AM, "Pid" <[email protected]> wrote: >> >>> Hi, >>> >>> Is there a requirement, or pre-discussed plan, to renamed packages (and >>> subprojects?) from com.gemstone.* to org.apache.geode.*? >>> >>> If so, it would probably be better to do this early, before branches >>> start appearing, because that kind of thing can be painful to merge later. >>> >>> >>> p >>> >>> >>> -- >>> >>> [key:62590808] >>> >> > > > -- > > [key:62590808]
