From dev-return-4487-archive-asf-public=cust-asf.ponee.io@singa.apache.org Fri Mar 13 03:02:47 2020 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 20A4018064F for ; Fri, 13 Mar 2020 04:02:47 +0100 (CET) Received: (qmail 74435 invoked by uid 500); 13 Mar 2020 03:02:46 -0000 Mailing-List: contact dev-help@singa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@singa.apache.org Delivered-To: mailing list dev@singa.apache.org Received: (qmail 74412 invoked by uid 99); 13 Mar 2020 03:02:45 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Mar 2020 03:02:45 +0000 From: GitBox To: dev@singa.apache.org Subject: [GitHub] [singa] dcslin commented on issue #585: Release, versioning and continous integration Message-ID: <158406856564.20262.12012079168972257010.gitbox@gitbox.apache.org> References: In-Reply-To: Date: Fri, 13 Mar 2020 03:02:45 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit dcslin commented 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 release directly. For torch, similarily: - `major` starts from `alpha`, followed by `rc` - `minor` starts from `rc` - patch is release 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