Hi -

Additional information.

> On Feb 7, 2019, at 2:44 PM, Dave Fisher <dave2w...@comcast.net> wrote:
> 
> Hi Devs -
> 
> We need to have a clarifying discussion about Releases, RCs and Tags. We also 
> need to be clear on “pre-apache” releases.
> 
> Let’s discuss from lifecycle.
> 
> (1) The repository is tagged as ready for a release candidate to be created.
> (2) The release candidate is created and may be made available to vote on 
> from the dev/incubator/echarts directory on dist.apache.org. It can also be 
> made into a Draft/pre-release Release on GitHub.
> (3) Once an RC has passed the VOTE on dev@echarts and general@incubator it is 
> svn moved to release/incubator/echarts and can be marked as the Latest on 
> Github. Renaming these to remove the RC# is a good idea.
> 
> https://echarts.apache.org/download.html 
> <https://echarts.apache.org/download.html> should not have been updated since 
> 4.2.1-rc1 has not yet passed an IPMC vote. Sorry sometimes it is slow. We can 
> continue to adjust, but… in Incubation the IPMC vote is required. You need to 
> revert to 4.1.0.
> 
> Let’s discuss the current state on Github Releases tab - 
> https://github.com/apache/incubator-echarts/releases
> 
> The only release listed is still an RC which has yet to pass. This needs to 
> be marked as
> Pre-apache releases edited to adjust their title to include “ (pre-Apache 
> release)”.
> Prior IPMC approved ECharts releases can be left in GitHub. RCs that did not 
> pass should be marked as Draft and or have the “pre-release” flag checked.

Releases mentioned here need to be of two varieties.
(a) Pre-Apache releases.
(b) Approved Apache Releases - (Unapproved Releases may be shown if they are 
Draft or “Pre-Release”)

ALSO - NPM.

https://www.npmjs.com/package/echarts <https://www.npmjs.com/package/echarts>

NO RCs - only (a) pre-Apache and (b) Approved Apache Releases.
Please update the license

Releases to non-Apache distributions are termed NOT OFFICIAL RELEASES - non the 
less these must be built from approved official source releases.

See http://www.apache.org/legal/release-policy.html 
<http://www.apache.org/legal/release-policy.html>

Mentors are here to answer questions.

Regards,
Dave

> 
> Please update and ask your Mentors to review.
> 
> Regards,
> Dave
> 
>> On Feb 7, 2019, at 2:06 PM, Justin Mclean <jmcl...@apache.org> wrote:
>> 
>> Hi,
>> 
>> I just saw that this commit added a link to the download page for a release 
>> candidate. [1] Why was this done?
>> 
>> We've just had a long discussion that the PPMC cannot advertise or link to 
>> unreleased material. [2] Again "Do not include any links on the project 
>> website that might encourage non-developers to download and use nightly 
>> builds, snapshots, release candidates, or any other similar package"
>> 
>> Thanks,
>> Justin
>> 
>> 1. https://echarts.apache.org/download.html
>> 2. http://www.apache.org/legal/release-policy.html#what
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org
>> For additional commands, e-mail: dev-h...@echarts.apache.org
>> 
> 

Reply via email to