Hi,

I don't think there is any policy that requires a package rename and I couldn't 
find anything on the incubator site. There was a similar discussion during the 
Sqoop graduation vote in 2012:

http://incubator.markmail.org/message/g7ehymawoi2cigg7

So I believe its up to the community to decide how to handle this.

Niall


-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Justin Erenkrantz
Sent: 07 May 2015 11:40
To: [email protected]
Subject: Re: Package renaming?

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.

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]
>
This electronic communication and its contents are intended for the recipient 
only and may contain confidential, non-public and/or privileged information.  
If you have received this electronic communication in error, do not read, 
duplicate or distribute.  Please advise the sender immediately and delete it 
from your system (if permitted by law).
  
Newedge makes no representation or warranty that the information contained 
herein is accurate, complete, fair or correct or that any transaction is 
appropriate for any person and it should not be relied on as such.  All 
information is subject to change without notice.  Nothing herein shall be 
construed as a recommendation or solicitation to purchase or sell any financial 
product or security or as an official confirmation of any transaction.  
However, any commentary regarding derivatives contained herein that is prepared 
by Sales and Trading Staff at Newedge is intended to be a general solicitation 
of business, which may include entering into a derivative transaction.  This 
communication is for information purposes only. Any market or other views 
expressed herein are those of the sender only as of the date indicated and not 
necessarily those of Newedge.  E-mails may not be secure or error free and 
information could be lost, destroyed, incomplete, delayed, altered, 
intercepted, corrupted or fail to be delivered.  Newedge makes no 
representation that this e-mail or any attachments are free of computer virus 
or other defects or inherent risks and accepts no responsibility for any loss 
or damage or liability of any kind arising there from.  Newedge reserves the 
right to retain all messages.

“Newedge” refers to Newedge Group SA and all of its worldwide branches and 
subsidiaries. Newedge Group in France and its foreign branches are authorized 
by the Autorité de Contrôle Prudentiel and Autorité des Marchés Financiers in 
France.   Newedge UK Financial Limited  is authorized and regulated  by the 
Financial Services Authority.  Newedge Group (Frankfurt, Zurich, Geneva  and 
Dubai branches) and Newedge UK Financial Limited do not deal with, or for, 
Retail Clients (as defined under MiFID, FSA rules and Dubai Financial Services 
Authority). Only Newedge USA, LLC is a member of FINRA and SIPC (SIPC only 
pertains to securities-related transactions and positions). Only Newedge Canada 
Inc. is a member of the Canadian Investor Protection Fund. Not all products or 
services are available from all Newedge organizations or personnel.

For further information about Newedge and our services, please see our website 
at www.newedge.com.

Reply via email to