Re: Repackaging src code to org.apache.geode

[John Blum]

+1

On Thu, Jul 2, 2015 at 5:18 PM, Dick Cavender  wrote:

> +1
>
>
> On 7/2/2015 4:58 PM, Bruce Schuchardt wrote:
>
>> +1
>>
>> Le 7/2/2015 2:06 PM, Kirk Lund a écrit :
>>
>>> Yep, having 99% of the code in org.apache.geode pkgs with 1% in
>>> com.gemstone.gemfire pkgs just to facilitate rolling upgrades seems like
>>> something that would be reasonable to discuss on general@incubator.
>>>
>>>
>>> On Thu, Jul 2, 2015 at 12:35 PM, Bruce Schuchardt <
>>> bschucha...@pivotal.io>
>>> wrote:
>>>
>>>  Hey, if we can do this then we should leave versions of exception
 classes
 in com.gemstone.gemfire so we can send them to old GemFire clients!  If
 we
 do that and swizzle package names in DataSerializer maybe we'll be able
 to
 support migration of GemFire clients to Geode.  That would facilitate
 faster adoption of Geode by users of the commercial product.




 Le 7/2/2015 12:28 PM, Sean Busbey a écrit :

  On Thu, Jul 2, 2015 at 1:25 PM, William Markito 
> wrote:
>
>   My reading of that is it's specifically for incubation, which indeed
> is
>
>> not
>> required based on this thread
>> <
>>
>>
>> https://www.mail-archive.com/search?l=dev@geode.incubator.apache.org&q=subject:%22Package+renaming%5C%3F%22&o=newest&f=1
>> .
>>
>> But for leaving incubation and becoming a TLP my understanding was
>> that
>> it
>> is required.
>>
>>
>>   Many projects leave code in packages that are not org.apache for
>>
> backwards
> compatibility.
>
> Roman is correct, if you want to have things outside of org.apache you
> should bring up the matter on general@incubator. Including the
> reasoning
> for having things outside of org.apache and the long term plan (if any)
> for
> moving things will help avoid a longer set of questions.
>
>
>
>
>>
>


-- 
-John
503-504-8657
john.blum10101 (skype)

Re: Repackaging src code to org.apache.geode

[Dick Cavender]

+1

On 7/2/2015 4:58 PM, Bruce Schuchardt wrote:

+1

Le 7/2/2015 2:06 PM, Kirk Lund a écrit :

Yep, having 99% of the code in org.apache.geode pkgs with 1% in
com.gemstone.gemfire pkgs just to facilitate rolling upgrades seems like
something that would be reasonable to discuss on general@incubator.


On Thu, Jul 2, 2015 at 12:35 PM, Bruce Schuchardt 


wrote:

Hey, if we can do this then we should leave versions of exception 
classes
in com.gemstone.gemfire so we can send them to old GemFire clients!  
If we
do that and swizzle package names in DataSerializer maybe we'll be 
able to

support migration of GemFire clients to Geode.  That would facilitate
faster adoption of Geode by users of the commercial product.




Le 7/2/2015 12:28 PM, Sean Busbey a écrit :


On Thu, Jul 2, 2015 at 1:25 PM, William Markito 
wrote:

  My reading of that is it's specifically for incubation, which 
indeed is

not
required based on this thread
<

https://www.mail-archive.com/search?l=dev@geode.incubator.apache.org&q=subject:%22Package+renaming%5C%3F%22&o=newest&f=1 


.

But for leaving incubation and becoming a TLP my understanding was 
that

it
is required.


  Many projects leave code in packages that are not org.apache for

backwards
compatibility.

Roman is correct, if you want to have things outside of org.apache you
should bring up the matter on general@incubator. Including the 
reasoning
for having things outside of org.apache and the long term plan (if 
any)

for
moving things will help avoid a longer set of questions.

Re: Repackaging src code to org.apache.geode

[Bruce Schuchardt]

+1

Le 7/2/2015 2:06 PM, Kirk Lund a écrit :

Yep, having 99% of the code in org.apache.geode pkgs with 1% in
com.gemstone.gemfire pkgs just to facilitate rolling upgrades seems like
something that would be reasonable to discuss on general@incubator.


On Thu, Jul 2, 2015 at 12:35 PM, Bruce Schuchardt 
wrote:


Hey, if we can do this then we should leave versions of exception classes
in com.gemstone.gemfire so we can send them to old GemFire clients!  If we
do that and swizzle package names in DataSerializer maybe we'll be able to
support migration of GemFire clients to Geode.  That would facilitate
faster adoption of Geode by users of the commercial product.




Le 7/2/2015 12:28 PM, Sean Busbey a écrit :


On Thu, Jul 2, 2015 at 1:25 PM, William Markito 
wrote:

  My reading of that is it's specifically for incubation, which indeed is

not
required based on this thread
<

https://www.mail-archive.com/search?l=dev@geode.incubator.apache.org&q=subject:%22Package+renaming%5C%3F%22&o=newest&f=1
.

But for leaving incubation and becoming a TLP my understanding was that
it
is required.


  Many projects leave code in packages that are not org.apache for

backwards
compatibility.

Roman is correct, if you want to have things outside of org.apache you
should bring up the matter on general@incubator. Including the reasoning
for having things outside of org.apache and the long term plan (if any)
for
moving things will help avoid a longer set of questions.

Re: Repackaging src code to org.apache.geode

[Anilkumar Gingade]

+1

On Thu, Jul 2, 2015 at 3:36 PM, William Markito  wrote:

> +1
>
> On Thu, Jul 2, 2015 at 2:06 PM, Kirk Lund  wrote:
>
> > Yep, having 99% of the code in org.apache.geode pkgs with 1% in
> > com.gemstone.gemfire pkgs just to facilitate rolling upgrades seems like
> > something that would be reasonable to discuss on general@incubator.
> >
> >
> > On Thu, Jul 2, 2015 at 12:35 PM, Bruce Schuchardt <
> bschucha...@pivotal.io>
> > wrote:
> >
> > > Hey, if we can do this then we should leave versions of exception
> classes
> > > in com.gemstone.gemfire so we can send them to old GemFire clients!  If
> > we
> > > do that and swizzle package names in DataSerializer maybe we'll be able
> > to
> > > support migration of GemFire clients to Geode.  That would facilitate
> > > faster adoption of Geode by users of the commercial product.
> > >
> > >
> > >
> > >
> > > Le 7/2/2015 12:28 PM, Sean Busbey a écrit :
> > >
> > >> On Thu, Jul 2, 2015 at 1:25 PM, William Markito 
> > >> wrote:
> > >>
> > >>  My reading of that is it's specifically for incubation, which indeed
> is
> > >>> not
> > >>> required based on this thread
> > >>> <
> > >>>
> > >>>
> >
> https://www.mail-archive.com/search?l=dev@geode.incubator.apache.org&q=subject:%22Package+renaming%5C%3F%22&o=newest&f=1
> > >>> .
> > >>>
> > >>> But for leaving incubation and becoming a TLP my understanding was
> that
> > >>> it
> > >>> is required.
> > >>>
> > >>>
> > >>>  Many projects leave code in packages that are not org.apache for
> > >> backwards
> > >> compatibility.
> > >>
> > >> Roman is correct, if you want to have things outside of org.apache you
> > >> should bring up the matter on general@incubator. Including the
> > reasoning
> > >> for having things outside of org.apache and the long term plan (if
> any)
> > >> for
> > >> moving things will help avoid a longer set of questions.
> > >>
> > >>
> > >>
> > >
> >
>
>
>
> --
>
> William Markito Oliveira
>
> -- For questions about Apache Geode, please write to
> *dev@geode.incubator.apache.org
> *
>

Re: Repackaging src code to org.apache.geode

[William Markito]

+1

On Thu, Jul 2, 2015 at 2:06 PM, Kirk Lund  wrote:

> Yep, having 99% of the code in org.apache.geode pkgs with 1% in
> com.gemstone.gemfire pkgs just to facilitate rolling upgrades seems like
> something that would be reasonable to discuss on general@incubator.
>
>
> On Thu, Jul 2, 2015 at 12:35 PM, Bruce Schuchardt 
> wrote:
>
> > Hey, if we can do this then we should leave versions of exception classes
> > in com.gemstone.gemfire so we can send them to old GemFire clients!  If
> we
> > do that and swizzle package names in DataSerializer maybe we'll be able
> to
> > support migration of GemFire clients to Geode.  That would facilitate
> > faster adoption of Geode by users of the commercial product.
> >
> >
> >
> >
> > Le 7/2/2015 12:28 PM, Sean Busbey a écrit :
> >
> >> On Thu, Jul 2, 2015 at 1:25 PM, William Markito 
> >> wrote:
> >>
> >>  My reading of that is it's specifically for incubation, which indeed is
> >>> not
> >>> required based on this thread
> >>> <
> >>>
> >>>
> https://www.mail-archive.com/search?l=dev@geode.incubator.apache.org&q=subject:%22Package+renaming%5C%3F%22&o=newest&f=1
> >>> .
> >>>
> >>> But for leaving incubation and becoming a TLP my understanding was that
> >>> it
> >>> is required.
> >>>
> >>>
> >>>  Many projects leave code in packages that are not org.apache for
> >> backwards
> >> compatibility.
> >>
> >> Roman is correct, if you want to have things outside of org.apache you
> >> should bring up the matter on general@incubator. Including the
> reasoning
> >> for having things outside of org.apache and the long term plan (if any)
> >> for
> >> moving things will help avoid a longer set of questions.
> >>
> >>
> >>
> >
>



-- 

William Markito Oliveira

-- For questions about Apache Geode, please write to
*dev@geode.incubator.apache.org
*

Re: Repackaging src code to org.apache.geode

[Kirk Lund]

Yep, having 99% of the code in org.apache.geode pkgs with 1% in
com.gemstone.gemfire pkgs just to facilitate rolling upgrades seems like
something that would be reasonable to discuss on general@incubator.


On Thu, Jul 2, 2015 at 12:35 PM, Bruce Schuchardt 
wrote:

> Hey, if we can do this then we should leave versions of exception classes
> in com.gemstone.gemfire so we can send them to old GemFire clients!  If we
> do that and swizzle package names in DataSerializer maybe we'll be able to
> support migration of GemFire clients to Geode.  That would facilitate
> faster adoption of Geode by users of the commercial product.
>
>
>
>
> Le 7/2/2015 12:28 PM, Sean Busbey a écrit :
>
>> On Thu, Jul 2, 2015 at 1:25 PM, William Markito 
>> wrote:
>>
>>  My reading of that is it's specifically for incubation, which indeed is
>>> not
>>> required based on this thread
>>> <
>>>
>>> https://www.mail-archive.com/search?l=dev@geode.incubator.apache.org&q=subject:%22Package+renaming%5C%3F%22&o=newest&f=1
>>> .
>>>
>>> But for leaving incubation and becoming a TLP my understanding was that
>>> it
>>> is required.
>>>
>>>
>>>  Many projects leave code in packages that are not org.apache for
>> backwards
>> compatibility.
>>
>> Roman is correct, if you want to have things outside of org.apache you
>> should bring up the matter on general@incubator. Including the reasoning
>> for having things outside of org.apache and the long term plan (if any)
>> for
>> moving things will help avoid a longer set of questions.
>>
>>
>>
>

Re: Repackaging src code to org.apache.geode

[Bruce Schuchardt]

Hey, if we can do this then we should leave versions of exception 
classes in com.gemstone.gemfire so we can send them to old GemFire 
clients!  If we do that and swizzle package names in DataSerializer 
maybe we'll be able to support migration of GemFire clients to Geode.  
That would facilitate faster adoption of Geode by users of the 
commercial product.




Le 7/2/2015 12:28 PM, Sean Busbey a écrit :

On Thu, Jul 2, 2015 at 1:25 PM, William Markito  wrote:


My reading of that is it's specifically for incubation, which indeed is not
required based on this thread
<
https://www.mail-archive.com/search?l=dev@geode.incubator.apache.org&q=subject:%22Package+renaming%5C%3F%22&o=newest&f=1
.

But for leaving incubation and becoming a TLP my understanding was that it
is required.



Many projects leave code in packages that are not org.apache for backwards
compatibility.

Roman is correct, if you want to have things outside of org.apache you
should bring up the matter on general@incubator. Including the reasoning
for having things outside of org.apache and the long term plan (if any) for
moving things will help avoid a longer set of questions.

Re: Repackaging src code to org.apache.geode

[Sean Busbey]

On Thu, Jul 2, 2015 at 1:25 PM, William Markito  wrote:

> My reading of that is it's specifically for incubation, which indeed is not
> required based on this thread
> <
> https://www.mail-archive.com/search?l=dev@geode.incubator.apache.org&q=subject:%22Package+renaming%5C%3F%22&o=newest&f=1
> >
> .
>
> But for leaving incubation and becoming a TLP my understanding was that it
> is required.
>
>
Many projects leave code in packages that are not org.apache for backwards
compatibility.

Roman is correct, if you want to have things outside of org.apache you
should bring up the matter on general@incubator. Including the reasoning
for having things outside of org.apache and the long term plan (if any) for
moving things will help avoid a longer set of questions.


-- 
Sean

Re: Repackaging src code to org.apache.geode

[William Markito]

My reading of that is it's specifically for incubation, which indeed is not
required based on this thread

.

But for leaving incubation and becoming a TLP my understanding was that it
is required.

On Thu, Jul 2, 2015 at 11:13 AM, Roman Shaposhnik 
wrote:

> On Thu, Jul 2, 2015 at 9:57 AM, Kirk Lund  wrote:
> > I just want to clarify that the reason we are planning to repackage is
> > because of this policy:
> >
> > http://incubator.apache.org/guides/mentor.html#repackaging
> >
> > ...which states that repackaging is recommended, but not mandated. Is
> there
> > a different source that states that it's mandated?
>
> ASF isn't really much a of a pure policy driven organization, but rather
> institutional memory driven organization. The discussion you really want
> to have is this: will IPMC vote for a podling graduating to the TLP status
> with java packages NOT within org.apache.
>
> This is a good discussion to have, but it really belongs on
> general@incubator.
>
>
> Thanks,
> Roman.
>



-- 

William Markito Oliveira

-- For questions about Apache Geode, please write to
*dev@geode.incubator.apache.org
*

Re: Repackaging src code to org.apache.geode

[Roman Shaposhnik]

On Thu, Jul 2, 2015 at 9:57 AM, Kirk Lund  wrote:
> I just want to clarify that the reason we are planning to repackage is
> because of this policy:
>
> http://incubator.apache.org/guides/mentor.html#repackaging
>
> ...which states that repackaging is recommended, but not mandated. Is there
> a different source that states that it's mandated?

ASF isn't really much a of a pure policy driven organization, but rather
institutional memory driven organization. The discussion you really want
to have is this: will IPMC vote for a podling graduating to the TLP status
with java packages NOT within org.apache.

This is a good discussion to have, but it really belongs on general@incubator.


Thanks,
Roman.

Re: Repackaging src code to org.apache.geode

[Bruce Schuchardt]

Keeping the existing packaging would make it a lot easier for GemFire 
users to move to Geode.  They wouldn't have to rewrite all of their 
client apps.


Le 7/2/2015 9:57 AM, Kirk Lund a écrit :

I just want to clarify that the reason we are planning to repackage is
because of this policy:

http://incubator.apache.org/guides/mentor.html#repackaging

...which states that repackaging is recommended, but not mandated. Is there
a different source that states that it's mandated?

-Kirk

Repackaging src code to org.apache.geode

[Kirk Lund]

I just want to clarify that the reason we are planning to repackage is
because of this policy:

http://incubator.apache.org/guides/mentor.html#repackaging

...which states that repackaging is recommended, but not mandated. Is there
a different source that states that it's mandated?

-Kirk