singa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [singa] dcslin edited a comment on issue #585: Release, versioning and continous integration
Date Fri, 13 Mar 2020 03:03:15 GMT
dcslin edited a comment on issue #585: Release, versioning and continous integration
URL: https://github.com/apache/singa/issues/585#issuecomment-598525352
 
 
   > 1. if the building of the conda package fails, we need to delete the newly updated
tag? Alternatively, we may need to consider a pre-release version like 3.0.0-alpha0.  Then,
we need to parse the version ID with `-alphaX`.
   > 2. both the CMake and Conda building scripts need to parse the version from the git
tag.
   > 3. The CI needs to monitor both the dev and master branch. Only when the tag of the
master branch changes, it uploads the pacakges (and docker images?).
   
   Regarding 1, after comparing other framework, like tf. 
   - For `major` release, they have `alpha` and `beta`, then followed by `rc`, release candidate.
   - And for `minor`, pre release starts from `rc`. 
   - While `patch` will be released directly.
   
   For torch, similarily:
   - `major` starts from `alpha`, followed by `rc`
   - `minor` starts from `rc`
   - patch is released directly.
   
   By right, simply speaking, `alpha` is first phase of testing internally. `beta` is testing
publicly. `rc` is almost like stable release unless serious bug is discovered.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message