From dev-return-2768-archive-asf-public=cust-asf.ponee.io@singa.incubator.apache.org Sun Apr 21 13:10:09 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 5B538180658 for ; Sun, 21 Apr 2019 15:10:09 +0200 (CEST) Received: (qmail 16462 invoked by uid 500); 21 Apr 2019 13:10:08 -0000 Mailing-List: contact dev-help@singa.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@singa.incubator.apache.org Delivered-To: mailing list dev@singa.incubator.apache.org Received: (qmail 16452 invoked by uid 99); 21 Apr 2019 13:10:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Apr 2019 13:10:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 1469EC24FB for ; Sun, 21 Apr 2019 13:10:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -108.001 X-Spam-Level: X-Spam-Status: No, score=-108.001 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id GeDz-3-_rQV9 for ; Sun, 21 Apr 2019 13:10:06 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 05B005F3B3 for ; Sun, 21 Apr 2019 13:10:05 +0000 (UTC) Received: (qmail 16311 invoked by uid 99); 21 Apr 2019 13:10:02 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 21 Apr 2019 13:10:02 +0000 Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 8E47FE282F for ; Sun, 21 Apr 2019 13:10:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 56FB225817 for ; Sun, 21 Apr 2019 13:10:00 +0000 (UTC) Date: Sun, 21 Apr 2019 13:10:00 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: dev@singa.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SINGA-433) Preparation for V2.0 release MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SINGA-433?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16822= 691#comment-16822691 ]=20 ASF subversion and git services commented on SINGA-433: ------------------------------------------------------- Commit 7c109b74f019f09288e206238bff8a00764c4935 in incubator-singa's branch= refs/heads/master from Wang Wei [ https://gitbox.apache.org/repos/asf?p=3Dincubator-singa.git;h=3D7c109b7 ] SINGA-433 Update download page and fix some errors in documentation > Preparation for V2.0 release > ---------------------------- > > Key: SINGA-433 > URL: https://issues.apache.org/jira/browse/SINGA-433 > Project: Singa > Issue Type: Task > Reporter: wangwei > Priority: Major > Time Spent: 2h 50m > Remaining Estimate: 0h > > As discussed in the dev list, we are going to release v2.0 with some news= features and API changes. This ticket includes the tasks listed in the [re= lease process page|http://singa.apache.org/en/develop/how-to-release.html].= If you want to take one task, please include the task name and ID in the c= omments. > =C2=A0 > 1. Select a release manager. The release manager (RM) is the coordinator = for the release process. It is the RM's signature (.asc) that is uploaded t= ogether with the release. The RM generates KEY (RSA 4096-bit) and uploads i= t to a public key server. The RM needs to get his key endorsed (signed) by = other Apache user, to be connected to the web of trust. He should first ask= the mentor to help signing his key. [http://www.apache.org/dev/release-sig= ning.html] > =C2=A0 > 2. Check > * the codebase does not include third-party code which is not compatible= to APL; > * The dependencies are compatible with APL. GNU-like licenses are NOT co= mpatible;=C2=A0 > * All source files written by us MUST include the Apache license header:= [http://www.apache.org/legal/src-headers.html]. There's a script in there = which helps propagating the header to all files. > *=20 > 3. Check > * The build process is error-free. > * Unit tests are included (as much as possible) > * The Jupyter notebooks are working with the new release > * The online documentation on the Apache website is up to date. > * Update the NOTICE file. If we include any third party code in the rele= ase package which is not APL, must state it at the end of the NOTICE file. > *=20 > 4. Prepare the RELEASE_NOTES file. Introduction, Features, Bugs (link to = JIRA), Changes (N/A for first erlease), Dependency list, Incompatibility is= sues. Follow this example: [http://commons.apache.org/proper/commons-digest= er/commons-digester-3.0/RELEASE-NOTES.txt]. Prepare DISCLAIMER file. modify= from [http://incubator.apache.org/guides/branding.html#disclaimers] > =C2=A0 > 5. Package the release. The release should be packaged into : apache-sing= a-incubating-xx.xx.xx.tar.gz. The release should not include any binary fil= es including git files. Upload the release. The release is uploaded to the = RM=E2=80=99s Apache page: people.apache.org/~ID/. > * apache-singa-incubating-xx.xx.xx.tar.gz > * KEY > * XX.acs > * XX.md5 > Roll out artifacts to mirrors. svn add to =E2=80=9Cdist/release/incubato= r/singa=E2=80=9D > Delete old artifacts (automatically archived) > *=20 > 6. Update the Download page. The tar.gz file MUST be downloaded from mirr= or, using closer.cgi script; other artifacts MUST be downloaded from main A= pache site > Good idea to update EC2 image and make it available for download as well > =C2=A0 > 7. Make the internal announcements. Template for singa-dev@ voting: > {code:java} > To: dev@singa.incubator.apache.org > Subject: [VOTE] Release apache-singa-X.Y.Z-incubating (release candidate= N) > Hi all, > I have created a build for Apache SINGA X.Y.Z-incubating, release candida= te N. > The artifacts to be voted on are located here: > [https://dist.apache.org/repos/dist/dev/incubator/singa/apache-singa-X.Y= .Z-incubating-rcN/] > The hashes of the artifacts are as follows: > apache-singa-X.Y.Z-incubating.tar.gz.md5 XXXX > apache-singa-X.Y.Z-incubating.tar.gz.sha256 XXXX > Release artifacts are signed with the following key: > [https://people.apache.org/keys/committer/] > {Apache ID of the Release Manager} > .asc > and the signature file is: > apache-singa-X.Y.Z-incubating.tar.gz.asc > Please vote on releasing this package. The vote is open for at least 72 h= ours and passes if a majority of at least three +1 votes are cast. > [ ] +1 Release this package as Apache SINGA X.Y.Z-incubating > [ ] 0 I don't feel strongly about it, but I'm okay with the release > [ ] -1 Do not release this package because... > Here is my vote: > +1 > {code} > Wait at least 48 hours for test responses > Any PPMC, committer or contributor can test features for releasing, and f= eedback. Based on that, PPMC will decide whether start a vote. > Vote Check. All PPMC members and committers should check these before vot= e +1. > =C2=A0 > 8. Call for a vote in Apache IPMC. Call a vote in general@incubator.apach= e.org > Template for singa-dev@ voting (results): > {code:java} > =20 > Subject: [RESULT] [VOTE] Release apache-singa-X.Y.Z-incubating (release = candidate N) > To: dev@singa.incubator.apache.org > =20 > Thanks to everyone who has voted and given their comments. The tally is = as follows. > =20 > N binding +1s: > > =20 > N non-binding +1s: > > =20 > No 0s or -1s. > =20 > I am delighted to announce that the proposal to release > Apache SINGA X.Y.Z-incubating has passed. > =20 > I'll now start a vote on the general list. Those of you in the IPMC, ple= ase recast your vote on the new thread. > {code} > Template for general@ voting - results > {code:java} > To: general@incubator.apache.org > Subject: [RESULT] [VOTE] Release Apache SINGA X.Y.Z (incubating) > Thanks everyone for their votes and comments. > I'm delighted to announce that this vote passes with the following result= s: > N binding +1s: > > N non-binding +1s: > > No 0s or -1s. > We=E2=80=99ll now roll the release out to the mirrors. > {code} > Publish release. Template for ANNOUNCING the release > {code:java} > To: announce@apache.org, dev@singa.apache.org > Subject: [ANNOUNCE] Apache SINGA (incubating) X.Y.Z released > =20 > We are pleased to announce that SINGA (incubating) X.Y.Z is released.=20 > =20 > SINGA is a general distributed deep learning platform for training big d= eep learning models over large datasets. It is designed with an intuitive p= rogramming model based on the layer abstraction. SINGA supports a wide vari= ety of popular deep learning models. > =20 > The release is available at: > [http://singa.incubator.apache.org/downloads.html] > =20 > The main features of this release include XXX > =20 > We look forward to hearing your feedbacks, suggestions, and contribution= s to the project.=20 > =20 > On behalf of the SINGA team. > {code} -- This message was sent by Atlassian JIRA (v7.6.3#76005)