[jira] [Commented] (SINGA-433) Preparation for V2.0 release
[
https://issues.apache.org/jira/browse/SINGA-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846021#comment-16846021
]
Moaz Reyad commented on SINGA-433:
--
I think this issue can be closed now.
> 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
> [release 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 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.
> [http://www.apache.org/dev/release-signing.html]
>
> 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:
> [http://www.apache.org/legal/src-headers.html]. 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:
> [http://commons.apache.org/proper/commons-digester/commons-digester-3.0/RELEASE-NOTES.txt].
> Prepare DISCLAIMER file. modify from
> [http://incubator.apache.org/guides/branding.html#disclaimers]
>
> 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: 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 “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: 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 candidate 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
> apache-singa-X.Y.Z-incubating.tar.gz.sha256
> 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 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 gene...@incubator.apache.org
> Template for singa-dev@ voting (results):
> {code:java}
>
> Subject: [RESULT] [VOTE] Release apache-singa-X.Y.Z-incubating (release
> candidate N)
>
[jira] [Commented] (SINGA-457) Error in ONNX backend.py example
[
https://issues.apache.org/jira/browse/SINGA-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16846020#comment-16846020
]
Moaz Reyad commented on SINGA-457:
--
I also tried the default option (with GPU), but the same error happens:
{code:bash}
$ python backend.py
Using GPU
Traceback (most recent call last):
File "backend.py", line 42, in
backend = sonnx.prepare(model, dev)
File
"/home/moaz/singa-gpu/venv/local/lib/python2.7/site-packages/singa/sonnx.py",
line 254, in prepare
stores_grad=stores_grad,
File
"/home/moaz/singa-gpu/venv/local/lib/python2.7/site-packages/singa/tensor.py",
line 96, in __init__
copy_from_numpy(self.data, data)
File
"/home/moaz/singa-gpu/venv/local/lib/python2.7/site-packages/singa/tensor.py",
line 1522, in copy_from_numpy
'tensor shape should be the same'
AssertionError: tensor shape should be the same
{code}
> Error in ONNX backend.py example
>
>
> Key: SINGA-457
> URL: https://issues.apache.org/jira/browse/SINGA-457
> Project: Singa
> Issue Type: Bug
>Reporter: Moaz Reyad
>Priority: Major
>
> I tried to run the file [backend.py |
> https://github.com/apache/incubator-singa/blob/master/examples/onnx/backend.py]
> example. I followed the instructions in the file:
> {code:python}
> # load and run the onnx model exported from pytorch
> #
> https://github.com/onnx/tutorials/blob/master/tutorials/PytorchOnnxExport.ipynb
> {code}
> and executed the file with "use_cpu" option:
> {code:bash}
> python backend.py --use_cpu
> Using CPU
> Traceback (most recent call last):
> File "backend.py", line 42, in
> backend = sonnx.prepare(model, dev)
> File
> "/home/moaz/singa/venv/local/lib/python2.7/site-packages/singa/sonnx.py",
> line 254, in prepare
> stores_grad=stores_grad,
> File
> "/home/moaz/singa/venv/local/lib/python2.7/site-packages/singa/tensor.py",
> line 96, in __init__
> copy_from_numpy(self.data, data)
> File
> "/home/moaz/singa/venv/local/lib/python2.7/site-packages/singa/tensor.py",
> line 1522, in copy_from_numpy
> 'tensor shape should be the same'
> AssertionError: tensor shape should be the same
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Podling Report Reminder - June 2019
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 19 June 2019, 10:30 am PDT. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, June 05). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://cwiki.apache.org/confluence/display/INCUBATOR/June2019 Note: This is manually populated. You may need to wait a little before this page is created from a template. Note: The format of the report has changed to use markdown. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
