singa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (SINGA-433) Preparation for V2.0 release
Date Fri, 26 Apr 2019 04:32:00 GMT


ASF subversion and git services commented on SINGA-433:

Commit a7027dd34a34f2863036dafe66ae9e7b7b06f084 in incubator-singa's branch refs/heads/master
from Wang Wei
[;h=a7027dd ]

SINGA-433 Update the website

> Preparation for V2.0 release
> ----------------------------
>                 Key: SINGA-433
>                 URL:
>             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 [release process page|].
If you want to take one task, please include the task name and ID in the comments.
> 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 together with the release. The RM
generates KEY (RSA 4096-bit) and uploads it 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. []
> 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 compatible; 
>  * All source files written by us MUST include the Apache license header: [].
There's a script in there which helps propagating the header to all files.
>  * 
> 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 release package
which is not APL, must state it at the end of the NOTICE file.
>  * 
> 4. Prepare the RELEASE_NOTES file. Introduction, Features, Bugs (link to JIRA), Changes
(N/A for first erlease), Dependency list, Incompatibility issues. Follow this example: [].
Prepare DISCLAIMER file. modify from []
> 5. Package the release. The release should be packaged into : apache-singa-incubating-xx.xx.xx.tar.gz.
The release should not include any binary files including git files. Upload the release. The
release is uploaded to the RM’s Apache page:
>  * apache-singa-incubating-xx.xx.xx.tar.gz
>  * KEY
>  * XX.acs
>  * XX.md5
>  Roll out artifacts to mirrors. svn add to “dist/release/incubator/singa”
>  Delete old artifacts (automatically archived)
>  * 
> 6. Update the Download page. The tar.gz file MUST be downloaded from mirror, using closer.cgi
script; other artifacts MUST be downloaded from main Apache site
>  Good idea to update EC2 image and make it available for download as well
> 7. Make the internal announcements. Template for singa-dev@ voting:
> {code:java}
> To:
>  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 candidate N.
> The artifacts to be voted on are located here:
>  []
> 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:
>  []
> {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 hours 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 feedback. Based
on that, PPMC will decide whether start a vote.
> Vote Check. All PPMC members and committers should check these before vote +1.
> 8. Call for a vote in Apache IPMC. Call a vote in
>  Template for singa-dev@ voting (results):
> {code:java}
>  Subject: [RESULT] [VOTE] Release apache-singa-X.Y.Z-incubating (release candidate N)
>  To:
>  Thanks to everyone who has voted and given their comments. The tally is as follows.
>  N binding +1s:
>  <names>
>  N non-binding +1s:
>  <names>
>  No 0s or -1s.
>  I am delighted to announce that the proposal to release
>  Apache SINGA X.Y.Z-incubating has passed.
>  I'll now start a vote on the general list. Those of you in the IPMC, please recast your
vote on the new thread.
> {code}
> Template for general@ voting - results
> {code:java}
> To:
>  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 results:
> N binding +1s:
>  <names>
> N non-binding +1s:
>  <names>
> No 0s or -1s.
> We’ll now roll the release out to the mirrors.
> {code}
> Publish release. Template for ANNOUNCING the release
> {code:java}
>  To:,
>  Subject: [ANNOUNCE] Apache SINGA (incubating) X.Y.Z released
>  We are pleased to announce that SINGA (incubating) X.Y.Z is released. 
>  SINGA is a general distributed deep learning platform for training big deep learning
models over large datasets. It is designed with an intuitive programming model based on the
layer abstraction. SINGA supports a wide variety of popular deep learning models.
>  The release is available at:
>  []
>  The main features of this release include XXX
>  We look forward to hearing your feedbacks, suggestions, and contributions to the project.

>  On behalf of the SINGA team.
> {code}

This message was sent by Atlassian JIRA

View raw message