From dev-return-90695-archive-asf-public=cust-asf.ponee.io@ant.apache.org Wed Feb 28 10:46:53 2018 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 [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id D1096180657 for ; Wed, 28 Feb 2018 10:46:52 +0100 (CET) Received: (qmail 70963 invoked by uid 500); 28 Feb 2018 09:46:51 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 70947 invoked by uid 99); 28 Feb 2018 09:46:51 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Feb 2018 09:46:51 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id A60D6C0FB2 for ; Wed, 28 Feb 2018 09:46:50 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.13 X-Spam-Level: ** X-Spam-Status: No, score=2.13 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, HTML_MESSAGE=2, KAM_SHORT=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Qy5sWSyyD0V9 for ; Wed, 28 Feb 2018 09:46:48 +0000 (UTC) Received: from mail-it0-f41.google.com (mail-it0-f41.google.com [209.85.214.41]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 6D42F5F2A8 for ; Wed, 28 Feb 2018 09:46:47 +0000 (UTC) Received: by mail-it0-f41.google.com with SMTP id l187so2754883ith.4 for ; Wed, 28 Feb 2018 01:46:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:references:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=wI1iSxP9rsNNeWAH5kRRZXR7+77jrwpE+GzYU71stTw=; b=ZIQDLuVvlKBG30C3+IZy3fKQUe61ExVq+w+y6t9S4t0ClgzhLn8yCZxYZwi65fz8qv PKSQVQZPQDRcFZQhFQQx9EEtrSvbUHiABU3k0QLYAASTgQ45opsQhp8ZYWgrXbavENAs Lyvoe+R5doSEjafPIF6Lk/AoDljbuaZT7hAYDpfeT7cF4DilsNFqQA8D4S9ACDzAlcEy nqb/m5jgWnVNJm01tNZnvVQe8chEONlVuAF1JzPGAAK+r9GSt6jDt8GIrPxrmCgTZ5qd uNgRCqdv5sBxB65QIh7MfqsoVbp83tPnpYZY6zVzw1YvbzGFbagj2T9hE2sBNY3KAr1V 2Ykw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:references:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=wI1iSxP9rsNNeWAH5kRRZXR7+77jrwpE+GzYU71stTw=; b=tDsIyaalUO4zIeZhAujkOBj/Zd0kTEdrr0CdSv350za1skmh6yAbPMPux69Hr0cf8C vDA6+0CrJ8fZJUvbLipYqkJLM3atinCERsiRQ8wnVQ1bbOWIlU5SNtreRxVVpLkZWg9j Uyjp4nweDhb8i4wpanHWMkqzNjhwU0OnyEcm6pXeSlZpXvQ1J1rPQP7GJJDL9VXPqx8D IDdvQT4uReV53WYEbrl/mHP0CRTVH3msSPtzDCc6p3Dle1GcFxq+k7Jknp4X9/514IbA gGqezGOgh1n/ILFlJU/HNcGbrlTRIAs6CNCO1+K46vWCsFEvdwaLmmF9ALSv16kl4UHk g13A== X-Gm-Message-State: APf1xPDpWUUO12xku9OI32UaeZie9WOpJURq0UVgVTxDGOX+AUdHlKIc EM7xvPzfzPPDvBTdEk1VU8diBX9u X-Google-Smtp-Source: AH8x225wVMIzYl8OcNHO/I7XUvevsYM3PjbgG4/Af6PH84Z6skcG79rc25zwkyGV+eCAKjQBodw2GQ== X-Received: by 10.36.81.208 with SMTP id s199mr22146069ita.46.1519811205456; Wed, 28 Feb 2018 01:46:45 -0800 (PST) Received: from whiteoffice.local ([223.227.114.184]) by smtp.gmail.com with ESMTPSA id u68sm1132083iou.0.2018.02.28.01.46.43 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Feb 2018 01:46:44 -0800 (PST) From: Jaikiran Pai X-Google-Original-From: Jaikiran Pai Subject: Re: ant-ivy git commit: initial WIP version of release instructions to follow for releasing Ivy To: Ant Developers List References: <7432c0f9c56d4fa0a6a290e48332bcda@git.apache.org> <002d01d3afd8$3106c3c0$93144b40$@de> Message-ID: Date: Wed, 28 Feb 2018 15:16:41 +0530 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------53299C5D0C2CBE471D71F8A7" Content-Language: en-US --------------53299C5D0C2CBE471D71F8A7 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit I read through it and (obviously) it covers the necessary details. So my new doc that I committed isn't needed. As for automating/changing things in that doc, I think it's something one of us can do once we try out that doc for this release. -Jaikiran On 27/02/18 8:12 PM, Jaikiran Pai wrote: > No I hadn’t :) Will check it out tonight. > > -Jaikiran > > On Tuesday, February 27, 2018, Jan Matèrne (jhm) > wrote: > > Have you seen doc/dev/makerelease.html ? > But updating (and maybe automating) is a good idea. ;) > > Jan > > > -----Ursprüngliche Nachricht----- > > Von: jaikiran@apache.org > [mailto:jaikiran@apache.org ] > > Gesendet: Dienstag, 27. Februar 2018 13:59 > > An: notifications@ant.apache.org > > > Betreff: ant-ivy git commit: initial WIP version of release > > instructions to follow for releasing Ivy > > > > Repository: ant-ivy > > Updated Branches: > >   refs/heads/master 86eacb6b5 -> 1a19f2f83 > > > > > > initial WIP version of release instructions to follow for > releasing Ivy > > > > > > Project: http://git-wip-us.apache.org/repos/asf/ant-ivy/repo > > > Commit: > http://git-wip-us.apache.org/repos/asf/ant-ivy/commit/1a19f2f8 > > > Tree: > http://git-wip-us.apache.org/repos/asf/ant-ivy/tree/1a19f2f8 > > > Diff: > http://git-wip-us.apache.org/repos/asf/ant-ivy/diff/1a19f2f8 > > > > > Branch: refs/heads/master > > Commit: 1a19f2f836cd33a25d458ed8ba9bbb3c7ce4ff96 > > Parents: 86eacb6 > > Author: Jaikiran Pai > > > Authored: Tue Feb 27 18:28:16 2018 +0530 > > Committer: Jaikiran Pai > > > Committed: Tue Feb 27 18:28:16 2018 +0530 > > > > > ---------------------------------------------------------------------- > >  release-instructions.adoc | 186 > > +++++++++++++++++++++++++++++++++++++++++ > >  1 file changed, 186 insertions(+) > > > ---------------------------------------------------------------------- > > > > > > > http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/1a19f2f8/release- > > > instructions.adoc > > > ---------------------------------------------------------------------- > > diff --git a/release-instructions.adoc > b/release-instructions.adoc new > > file mode 100644 index 0000000..ba8bd5d > > --- /dev/null > > +++ b/release-instructions.adoc > > @@ -0,0 +1,186 @@ > > += Instructions for releasing Apache Ivy > > + > > + > > +NOTE: This document is adapted from the Ant release process. > > + > > +== Propose a release plan > > + > > +This should set out the timetable for the release under ideal > > circumstances. In reality, you send a note to the list that you > intend > > to cut the release and wait for a few days whether anybody objects. > > + > > +We don't create extra branches for release and the release will be > > done from the `master` branch. > > + > > +This document assumes you are familiar with `git` http://git- > > scm.com/book/en/v2/ may be a good > guide if you are not. > > + > > +== Checkout the repo > > + > > +We don't want tags for failed votes to end up on out branches > so the > > release is first created from a detached head. > > + > > +Checkout the `HEAD` of the `master` branch as a detached head: > > + > > +[source] > > +---- > > +    git checkout master^0 > > + > > +---- > > + > > +Make sure that your directory tree is clean by running `git > status`. > > + > > +== Update the version number > > + > > +The `version.properties` contains the version number of the Ivy > > project being released. Update the following properties to the right > > values (which is decided based on what version number and > qualifier you > > want to associate with the release): > > + > > +[source] > > +---- > > +target.ivy.version=2.5.0 > > +# Following OSGi spec: have to be 3 numbers separated by dots > > +target.ivy.bundle.version=2.5.0 # in case we want to add a > qualifier > > +such as alpha, beta, etc... > > +# if non empty, add a '_' at the end of the qualifier, so the > version > > +would look like 1.2.3.alpha_200901011200 > > +target.ivy.bundle.version.qualifier=alpha_ > > +---- > > + > > +== Trigger the release build > > + > > +Trigger the release by running the `build-release.xml`'s `release` > > target. This compiles the project, runs the tests, generates the > > documentation and tutorials and finally creates the distribution > > artifacts. > > + > > +[source] > > +---- > > +    ant -f build-release.xml release > > + > > +---- > > + > > +Upon successful completion, the distribution artifacts will be > > generated in the `build/distrib` directory of the checked out > project, > > locally. > > + > > +== Sign the distribution artifacts > > + > > +TODO: This section needs more details about setting up KEYS and > making > > +them available to the public (similar to the Ant project's KEYS > file > > in > > +the repo) > > + > > +The `build-release.xml` has a `sign` target which can be used > to sign > > the generated distribution artifacts. Run the following command > to sign > > these artifacts: > > + > > +[source] > > +---- > > +    ant -f build-release.xml sign > > +---- > > + > > +== Commit the changes and create a RC tag for the release > > + > > +At this point the distribution artifacts have been generated > and have > > been successfully signed too. We can now commit the changes > (which most > > likely will just be the version file changes) and create a RC > tag for > > the release. > > + > > +If we are releasing `2.5.0` and if this is the first RC for it, > then > > we create a `2.5.0-RC1` tag for it. > > + > > +Be sure to replace the version number appropriately in the > following > > command: > > + > > +[source] > > +---- > > +    git tag -m "Release " > > +---- > > + > > +The commit and the tag can now be pushed to the asf hosted repo: > > + > > +[source] > > +---- > > +    git push --tags master > > +---- > > + > > +== Upload the distribution artifacts > > + > > +TODO: This needs more details and some verification that it's a > > similar process as that we do in Ant release. The process might > involve > > the following: > > + > > +=== Upload to https://dist.apache.org/repos/dist/dev/ant/ivy/ > > > + > > +- Create a SVN sandbox on your computer with > > https://dist.apache.org/repos/dist/dev/ant/ivy/ > in it. > > + > > +- Copy the distribution folder to the location of the sandbox. > > + > > +- `svn add` the files and `commit` into > > +https://dist.apache.org/repos/dist/dev/ant/ivy/ > > > + > > +=== Upload the Maven artifacts > > +TODO: This section needs work > > + > > +== Initiate a vote > > + > > +Once the above steps are done, initiate a vote by sending a > email on > > dev@ant. > > + > > +The email will typically mention : > > + > > +- the git tag for the release including commit hash, > > + > > +- the location of the tarballs, including revision number in > > +dist.apache.org repository > > + > > +- the URL for the maven artifacts > > + > > +- TODO: link to documentation? (where do we upload it?) > > + > > +The vote will only pass if at least three PMC members have voted +1 > > and more +1s than -1s have been cast.  The vote will run for 3 days. > > + > > +If the vote fails, address the problems and recreate the next > RC build > > +(by redoing the release process) > > + > > +== Promote the RC to Final > > + > > +=== Create the tag in the repo > > +Once the vote has passed, tag the last RC created with the > final tag > > + > > +[source] > > +---- > > +    git checkout > > +    git tag -m "Tagging release of Ivy" > > +    git push --tags master > > +---- > > + > > +=== Promote the distribution artifacts to > > +https://dist.apache.org/repos/dist/release/ant/ivy/ > > > + > > +The distrib artifacts should be published the apache dist. It is > > managed via `svnpubsub` so the release should be committed to the > > subversion repository at > > https://dist.apache.org/repos/dist/release/ant/ivy/ > . > > + > > +TODO: This needs more details on what needs to be done > > + > > +== Release the project in the Ivy's JIRA > > + > > +Mark the newly released version as "released" in the JIRA and > create a > > newer version for tracking upcoming tasks. > > + > > +== Update the version in the repo to next release > > + > > +Checkout the master branch and update the `version.properties` > to use > > newer version number for a subsequent release. Commit the > changes and > > push to master branch. > > + > > +[source] > > +---- > > +    git checkout master > > +    ... edit the version.properties to use newer version > > +    git commit -m "next dev version" ./version.properties > > +    git push master > > +---- > > + > > +== Wait for mirrors to catch up > > + > > +Now that distribution artifacts have been uploaded, wait a few > hours > > for the mirrors to catch up. > > + > > +== Update the Ivy site https://ant.apache.org/ivy/ > > + > > +The website is managed here: > > +https://svn.apache.org/repos/asf/ant/site/ivy/ > > > + > > +TODO: This needs more details/verification > > + > > +Copy the manual of the release into the production folder - > since the > > site still uses svn and Ivy proper uses git there currently is > no way > > to use the scm for this. > > + > > +Regenerate the site > > + > > +== Announce the release > > + > > +At this point in time, the release is done and announcements > are made. > > PGP-sign your announcement posts. > > + > > +Apache mailing lists that should get the announcements: > > + > > + announce@apache.org , > dev@ant.apache.org and ivy- > > user@ant.apache.org . > > + > > +== Get some fresh air! > > + > > +You can now reacquaint yourself with your family and friends ;) > > + > > +== Remove the older releases > > + > > +TODO: This needs details > > + > > + > > + > > + > > + > > + > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org > > For additional commands, e-mail: dev-help@ant.apache.org > > --------------53299C5D0C2CBE471D71F8A7--