Added a coho command to help with this: > coho list-release-urls --version 3.4.0 --repo cadence http://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=shortlog;h=refs/tags/3.4.0 9768e738823ba90213f7b118147ccaf7d5c85887 refs/tags/3.4.0 http://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=shortlog;h=refs/tags/3.4.0 a026bbcd4592717a5bc46222654729cbae958728 refs/tags/3.4.0 http://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;a=shortlog;h=refs/tags/3.4.0 195ea8d4602fffc6b7866a5848ff48c3d618d309 refs/tags/3.4.0 http://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;a=shortlog;h=refs/tags/3.4.0 0b2c38d417776920973254f8bbbced7be126c174 refs/tags/3.4.0 http://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git;a=shortlog;h=refs/tags/3.4.0 c8f7aee9e7a1e07aa9689887cca7271793613121 refs/tags/3.4.0 http://git-wip-us.apache.org/repos/asf?p=cordova-firefoxos.git;a=shortlog;h=refs/tags/3.4.0 3e760cf65d5e6b6433fe0b134398a8e2838b939a refs/tags/3.4.0 http://git-wip-us.apache.org/repos/asf?p=cordova-ubuntu.git;a=shortlog;h=refs/tags/3.4.0 91d453876b4afda7d7f51b7a682292a1f17e7c9e refs/tags/3.4.0 http://git-wip-us.apache.org/repos/asf?p=cordova-amazon-fireos.git;a=shortlog;h=refs/tags/3.4.0 41207ba1ce0b0ea2821edce22d2a3a77123faf55 refs/tags/3.4.0 Tag "3.4.0" does not exist in repo cordova-cli http://git-wip-us.apache.org/repos/asf?p=cordova-js.git;a=shortlog;h=refs/tags/3.4.0 5d558a9c1adbfc11ea5f095d12bf6d1d6ca697fb refs/tags/3.4.0 http://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;a=shortlog;h=refs/tags/3.4.0 32830c4afaf1bdbfc50e2c5bfb2d87b056d902e2 refs/tags/3.4.0 http://git-wip-us.apache.org/repos/asf?p=cordova-app-hello-world.git;a=shortlog;h=refs/tags/3.4.0 23576375e7ee8580f41353aab8b523427b8cd0b3 refs/tags/3.4.0 http://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=shortlog;h=refs/tags/3.4.0 db7ab1ec80915153329c4b1ceaa0718b1b01c8e2 refs/tags/3.4.0
> coho list-release-urls --version 3.4.0-0.1.0 --repo cordova-cli http://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=shortlog;h=refs/tags/3.4.0-0.1.0 8bc03dc00c7ca87d7fa0446ed364875e551db0c1 refs/tags/3.4.0-0.1.0 You have to specify CLI version manually right now, but if someone wants to fix that up in coho it would be sweet. On Thu, Feb 20, 2014 at 3:02 PM, sebb <[email protected]> wrote: > Thanks, that looks good. I'll have a detailed look later. > > Is it possible to modify/delete a git tag? > If so, then the git hashes ought to be provided, as accidents can happen. > The mail archives should contain an immutable reference to the exact > code in the repo that was used to build the release. > > On 20 February 2014 19:52, Michal Mocny <[email protected]> wrote: > > Sebb, is this sufficient? Or do we want a list of git hash's? > > > > > http://git-wip-us.apache.org/repos/asf?p=cordova-android.git;a=shortlog;h=refs/tags/3.4.0 > > > http://git-wip-us.apache.org/repos/asf?p=cordova-ios.git;a=shortlog;h=refs/tags/3.4.0 > > > http://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git;a=shortlog;h=refs/tags/3.4.0 > > > http://git-wip-us.apache.org/repos/asf?p=cordova-windows.git;a=shortlog;h=refs/tags/3.4.0 > > > http://git-wip-us.apache.org/repos/asf?p=cordova-wp8.git;a=shortlog;h=refs/tags/3.4.0 > > > http://git-wip-us.apache.org/repos/asf?p=cordova-firefoxos.git;a=shortlog;h=refs/tags/3.4.0 > > > http://git-wip-us.apache.org/repos/asf?p=cordova-ubuntu.git;a=shortlog;h=refs/tags/3.4.0 > > > http://git-wip-us.apache.org/repos/asf?p=cordova-amazon-fireos.git;a=shortlog;h=refs/tags/3.4.0 > > > http://git-wip-us.apache.org/repos/asf?p=cordova-js.git;a=shortlog;h=refs/tags/3.4.0 > > > http://git-wip-us.apache.org/repos/asf?p=cordova-mobile-spec.git;a=shortlog;h=refs/tags/3.4.0 > > > http://git-wip-us.apache.org/repos/asf?p=cordova-app-hello-world.git;a=shortlog;h=refs/tags/3.4.0 > > > http://git-wip-us.apache.org/repos/asf?p=cordova-docs.git;a=shortlog;h=refs/tags/3.4.0 > > > > > http://git-wip-us.apache.org/repos/asf?p=cordova-cli.git;a=shortlog;h=refs/tags/3.4.0-0.1.0 > > > > > > On Thu, Feb 20, 2014 at 2:28 PM, Joe Bowser <[email protected]> wrote: > > > >> On Thu, Feb 20, 2014 at 11:16 AM, Brian LeRoux <[email protected]> wrote: > >> > we should start a thread about coho. it kind of grew into a tool that > I'm > >> > fairly certain only the googlers use and aligning our flows would be a > >> good > >> > thing. > >> > >> We're pretty much forced to use it to tag now, whether we like it or > not. > >> > >> > > >> > > >> > On Thu, Feb 20, 2014 at 11:06 AM, Michal Mocny <[email protected]> > >> wrote: > >> > > >> >> (I was wrong about firefoxos, its just cli thats missing the tag) > >> >> > >> >> > >> >> On Thu, Feb 20, 2014 at 1:58 PM, Brian LeRoux <[email protected]> wrote: > >> >> > >> >> > C'mon Joe, its our job to help him. You can take the high road and > >> then > >> >> > Sebb can start affording us the same courtesy. > >> >> > > >> >> > > >> >> > On Thu, Feb 20, 2014 at 10:16 AM, Joe Bowser <[email protected]> > >> wrote: > >> >> > > >> >> > > Seriously, you can't find that yourself? You clearly know nothing > >> >> > > about this project. > >> >> > > > >> >> > > On Thu, Feb 20, 2014 at 7:30 AM, sebb <[email protected]> wrote: > >> >> > > > On 20 February 2014 14:47, Andrew Grieve <[email protected] > > > >> >> wrote: > >> >> > > >> SCM == ? > >> >> > > > > >> >> > > > Source Code / Software Configuration Management > >> >> > > > > >> >> > > >> Do you mean the git tags? > >> >> > > >> All of the repositories are tagged with the version number of > the > >> >> > > release. > >> >> > > >> So, "3.4.0" is the tag. > >> >> > > > > >> >> > > > OK, so where are the repos then please? > >> >> > > > Also, if the tag is not immutable, it would help to have the > hash. > >> >> > > > > >> >> > > >> > >> >> > > >> On Thu, Feb 20, 2014 at 9:02 AM, sebb <[email protected]> > wrote: > >> >> > > >> > >> >> > > >>> On 18 February 2014 23:26, Steven Gill < > [email protected]> > >> >> > wrote: > >> >> > > >>> > Please review and vote on the Cordova 3.4.0 release. > >> >> > > >>> > > >> >> > > >>> > You can find the sample release at > >> >> > http://people.apache.org/~steven/ > >> >> > > >>> > >> >> > > >>> At the risk of being flamed, I am concerned that the VOTE > mail > >> does > >> >> > > >>> not include a link to the SCM tag. > >> >> > > >>> > >> >> > > >>> Why is this important? > >> >> > > >>> > >> >> > > >>> The ASF releases source files which come with a LICENSE (and > >> >> NOTICE). > >> >> > > >>> It is vital that the release only contains files that are > >> permitted > >> >> > to > >> >> > > >>> be distributed, and we aren't accidentally including files > that > >> >> > should > >> >> > > >>> not be distributed. > >> >> > > >>> > >> >> > > >>> Equally, it is important that the source release is not > missing > >> any > >> >> > > >>> required files. > >> >> > > >>> > >> >> > > >>> The only practical way to check all the files is to compare > the > >> >> > source > >> >> > > >>> archive against the tag(s) it is supposed to contain. > >> >> > > >>> > >> >> > > >>> In theory, an automated build process will ensure that the > >> archive > >> >> > > >>> only contains files from the tag, and does not omit any > require > >> >> > files. > >> >> > > >>> However, in practice, the archives are built from workspaces > >> that > >> >> > > >>> contain other files (e.g. compilation output). > >> >> > > >>> I know of at least two projects which used standard automated > >> >> > > >>> procedures (Maven), yet their source releases contained files > >> that > >> >> > > >>> should not have been released. > >> >> > > >>> > >> >> > > >>> Should there be a complaint, it's important that the PMC can > >> show > >> >> > that > >> >> > > >>> due diligence was done in checking the source archive > contents. > >> >> > > >>> This will be easier to prove if the VOTE thread contains > >> details of > >> >> > > >>> the SCM tags from which the archive was built. > >> >> > > >>> > >> >> > > >>> The SCM repo provides traceability of provenance. > >> >> > > >>> > >> >> > > >>> So please can someone provide the SCM tag(s) that were used > to > >> >> create > >> >> > > >>> the source release? > >> >> > > >>> > >> >> > > >>> > Voting will go on for 24 hours. > >> >> > > >>> > > >> >> > > >>> > Cheers, > >> >> > > >>> > > >> >> > > >>> > -Steve > >> >> > > >>> > >> >> > > > >> >> > > >> >> > >> >
