Hi Dave and Willem, We have one release[2] and one tag[4] in GitHub made after entering incubation. The detail as following:
[1] 2018-07-18 Project enters incubation; [2] 2018-08-25 Github release 0.8.2. [3] 2018-08-30 Migration of Palo to Apache Github Organization is Done. [4] 2018-10-27 Made a tag 0.8.2.1 [5] 2018-12-11 Made a tag 0.9.0-rc01 and now still pending to wait voting in Apache community. I’m not sure that if [2] and [4] are non-Apache releases, if they are, I can remove them. Best Regards, Reed On 2019/1/9 上午11:11， "Dave Fisher" <dave2w...@comcast.net> wrote: >Yes! Please review. There are no bad questions. Please ask to clarify any >doubts! > >I have one question. Have there been any non-Apache releases since >Incubation started? > >Regards, >Dave > >Sent from my iPhone > >> On Jan 8, 2019, at 7:06 PM, Willem Jiang <willem.ji...@gmail.com> wrote: >> >> Hi Team， >> >> I'm not sure if you are aware the official release and unreleased code >> in Apache Incubator. >> Please take some time read through the code and let me know what you >>think. >> >> Willem Jiang >> >> Twitter: willemjiang >> Weibo: 姜宁willem >> >> >> ---------- Forwarded message --------- >> From: Justin Mclean <jus...@classsoftware.com> >> Date: Sun, Jan 6, 2019 at 7:21 AM >> Subject: Official releases vs unreleased code >> To: <gene...@incubator.apache.org> >> >> >> Hi, >> >> Over the last few months I’ve run into 1/2 dozen podlings who are >> making and promoting releases to the wider community that contain >> unreleased code, and I’m a little surprised that they were unaware >> that this is not allowed. This also has come up in feedback received >> from the exit questionnaire. >> >> In the release policy [3] it clearly states: >> "Projects MUST direct outsiders towards official releases rather than >> raw source repositories, nightly builds, snapshots, release >> candidates, or any other similar packages.” >> >> This has been discussed many times but these two legal JIRAs [1][2] >> spell it out quite clearly. And while these tickets refer to docker >> the same applies to any distribution mechanism. >> >> In short “It is appropriate to distribute official releases through >> downstream channels, but inappropriate to distribute unreleased >> materials through them.” >> >> So if your projects is using docker, PiPY, GitHub releases, npm or any >> other ways of distribution please make sure that the wider community >> is only pointed at official release and the best way to do this is not >> to publish unreleased code on those platforms. Ask yourself is someone >> outside of the project likely to use this and if the answer is yes >> then reconsider how you are using that distribution channel and make >> sure it only contains official releases. >> >> Thanks, >> Justin >> >> 1. https://issues.apache.org/jira/browse/LEGAL-270 >> 2. https://issues.apache.org/jira/browse/LEGAL-427 >> 3. http://www.apache.org/legal/release-policy.html#publication >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@doris.apache.org >> For additional commands, e-mail: dev-h...@doris.apache.org >> > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: dev-unsubscr...@doris.apache.org >For additional commands, e-mail: dev-h...@doris.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@doris.apache.org For additional commands, e-mail: dev-h...@doris.apache.org
