Re: Unapproved Sharding Sphere releases

--- Original ------ > From: Chris Lambertus > Date: Sat,Feb 9,2019 4:34 AM > To: general > Cc: dev > Subject: Re: Unapproved Sharding Sphere releases > > > > > >> On Feb 7, 2019, at 1:52 PM, Dave Fisher wrote: >> >> >

Re: Unapproved Sharding Sphere releases

. Sheng Wu Apache SkyWalking, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: Chris Lambertus Date: Sat,Feb 9,2019 4:34 AM To: general Cc: dev Subject: Re: Unapproved Sharding Sphere releases > On Feb 7, 2019, at 1:52 PM, Dave Fis

Re: Unapproved Sharding Sphere releases

> On Feb 7, 2019, at 1:52 PM, Dave Fisher wrote: > > > >> On Feb 7, 2019, at 1:44 PM, Craig Russell wrote: [snip] >> >> Larger discussion: Is there a reason for projects coming into incubation to >> have the old repository moved (i.e. renamed) instead of being copied? I >> cannot think

Re: Unapproved Sharding Sphere releases

> On Feb 7, 2019, at 1:55 PM, Justin Mclean wrote: > > Hi, > >> Do we recommend that the Title be changed to add “Non-Apache release from >> prior to Incubation” or would it be sufficient for that text to be added to >> the Description? > > IMO however the PPMC want to handle it as long

Re: Unapproved Sharding Sphere releases

Hi, > Do we recommend that the Title be changed to add “Non-Apache release from > prior to Incubation” or would it be sufficient for that text to be added to > the Description? IMO however the PPMC want to handle it as long as it’s clear it’s not an Apache release and came before the

Re: Unapproved Sharding Sphere releases

> On Feb 7, 2019, at 1:44 PM, Craig Russell wrote: > >> On Feb 7, 2019, at 11:02 AM, Dave Fisher wrote: >> >>> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17289 >>> >> >> The old repository was moved to the

Re: Unapproved Sharding Sphere releases

> On Feb 7, 2019, at 1:24 PM, Justin Mclean wrote: > > Hi, > >> Prior “Non-Apache Releases” are attached to the repository and come along. >> What to do? I think we have to accept these, but mark them appropriately as >> deleting them would be for the project community during transition. >

Re: Unapproved Sharding Sphere releases

> On Feb 7, 2019, at 11:02 AM, Dave Fisher wrote: > >> https://issues.apache.org/jira/projects/INFRA/issues/INFRA-17289 >> > > The old repository was moved to the ASF and logically that should also have > moved the legacy

Re: Unapproved Sharding Sphere releases

Hi, > Prior “Non-Apache Releases” are attached to the repository and come along. > What to do? I think we have to accept these, but mark them appropriately as > deleting them would be for the project community during transition. +1 Clearly labelling any non-apache releases prior to the the

Re: Unapproved Sharding Sphere releases

> On Feb 7, 2019, at 10:46 AM, Craig Russell wrote: > > Hi Dave, > >> On Feb 7, 2019, at 9:12 AM, Dave Fisher wrote: >> >> >> >>> On Feb 7, 2019, at 8:31 AM, Craig Russell wrote: >>> >>> >>> On Feb 6, 2019, at 10:31 PM, Justin Mclean wrote: HI, > This

Re: Unapproved Sharding Sphere releases

Hi Dave, > On Feb 7, 2019, at 9:12 AM, Dave Fisher wrote: > > > >> On Feb 7, 2019, at 8:31 AM, Craig Russell wrote: >> >> >> >>> On Feb 6, 2019, at 10:31 PM, Justin Mclean wrote: >>> >>> HI, >>> This was done. The issue is that the "3.0.0 outside Apache" release should not

Re: Unapproved Sharding Sphere releases

> On Feb 7, 2019, at 8:31 AM, Craig Russell wrote: > > > >> On Feb 6, 2019, at 10:31 PM, Justin Mclean wrote: >> >> HI, >> >>> This was done. The issue is that the "3.0.0 outside Apache" release should >>> not be associated with Apache but with the previous project. >> >> They also

Re: Unapproved Sharding Sphere releases

> On Feb 6, 2019, at 10:31 PM, Justin Mclean wrote: > > HI, > >> This was done. The issue is that the "3.0.0 outside Apache" release should >> not be associated with Apache but with the previous project. > > They also made a 3.1.0 release as well and it was on the Apache github site >

Re: Unapproved Sharding Sphere releases

HI, > This was done. The issue is that the "3.0.0 outside Apache" release should > not be associated with Apache but with the previous project. They also made a 3.1.0 release as well and it was on the Apache github site (both 3.0 and 3.1 have now been removed from there). > It looks like the

Re: Unapproved Sharding Sphere releases

thub.com/apache/incubator-shardingsphere/releases >> >> Sheng Wu >> Apache SkyWalking, ShardingSphere, Zipkin >> >> From Wu Sheng 's phone. >> >> >> ------ Original ---------- >> From: 吴晟 Sheng Wu >> Date: Wed,Jan 30,2019 5:54 PM >> To: dev

Re: Unapproved Sharding Sphere releases

king, ShardingSphere, Zipkin > > From Wu Sheng 's phone. > > > -- Original -- > From: 吴晟 Sheng Wu > Date: Wed,Jan 30,2019 5:54 PM > To: dev , dev < > d...@shardingsphere.apache.org> > Cc: Justin Mclean , jmclean > Subject

Re: Unapproved Sharding Sphere releases

, ShardingSphere, Zipkin From Wu Sheng 's phone. -- Original -- From: zhangli...@apache.org Date: Wed,Jan 30,2019 0:03 PM To: dev Cc: Justin Mclean , jmclean Subject: Re: Unapproved Sharding Sphere releases Hello Justin, Thanks for your advice. This is a legacy