> 1. Add statement in GitHub release versions. Saying these are not Apache release.
Done. The URL is [1] > 2. Add statement in you website home, document and download pages, saying all available releases are not Apache releases Done. The URL is [2], both for English and Chinese pages. > 3. After the first approved release, you only says before this version(4.0.0 maybe) are not Apachre releases. Will do it after Apache release finish. > 4. Add statement in GitHub project readme.md for the same thing. Done. The URL is [3], both for English and Chinese readme.md. [1] https://github.com/apache/incubator-shardingsphere/releases/tag/3.1.0 [2] http://shardingsphere.apache.org/ [3] https://github.com/apache/incubator-shardingsphere/blob/dev/README.md ------------------ Liang Zhang (John) Apache ShardingSphere & Dubbo 吴晟 Sheng Wu <[email protected]> 于2019年1月30日周三 下午5:58写道： > Hi > > > I think I agree the Justin's points. > No matter the release happens in Apache org repo or not, it still happened > after you asked and accepted by Incubator. So, it is not encouraged and not > following the Apache way. > > > I propose these adjustments > 1. Add statement in GitHub release versions. Saying these are not Apache > release. > 2. Add statement in you website home, document and download pages, saying > all available releases are not Apache releases > 3. After the first approved release, you only says before this > version(4.0.0 maybe) are not Apachre releases. > 4. Add statement in GitHub project readme.md for the same thing. > > > Especially for document pages, this needs to be tagged in clear way. > I know, those releases in maven central repo are hard to release, and not > good for the existing community. So, I hope my proposals are good enough. > > > > Sheng Wu > Apache SkyWalking, ShardingSphere, Zipkin > > From Wu Sheng 's phone. > > > ------------------ Original ------------------ > From: [email protected] <[email protected]> > Date: Wed,Jan 30,2019 0:03 PM > To: dev <[email protected]> > Cc: Justin Mclean <[email protected]>, jmclean <[email protected]> > Subject: Re: Unapproved Sharding Sphere releases > > > > Hello Justin, > > Thanks for your advice. > This is a legacy release, which we have discussed on the dev mail list[1] > before. > This release is done before the transfer to ASF repo and package rename. > We are now preparing apache release which begins with new version(4.0.0). > We will not release non-Apache version any more in the future. > Any suggestion to identify versions like these kind of releases? > > > [1] > > https://lists.apache.org/thread.html/a3bba7e53bfed6d18924b592ecf0533aebc8d307f8c7e399a7fec2cf@%3Cdev.shardingsphere.apache.org%3E > > ------------------ > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Justin Mclean <[email protected]> 于2019年1月30日周三 上午6:23写道： > > > Hi, > > > > Looking at [1] there seems to have been releases made after you have > > entered incubation. All releases must be approved by the PPMC and the > IPMC > > (usually by voting). Can you please remove these releases and include in > > your upcoming incubator report what you will do to stop this happening > > going forward. > > > > Thanks, > > Justin > > > > P.S please CC me on any replies as I'm not subscribed to this list > > > > 1.https://github.com/apache/incubator-shardingsphere/releases > > > >
