Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1619E1055F for ; Thu, 20 Feb 2014 19:28:28 +0000 (UTC) Received: (qmail 94179 invoked by uid 500); 20 Feb 2014 19:28:26 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 94141 invoked by uid 500); 20 Feb 2014 19:28:26 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 94132 invoked by uid 99); 20 Feb 2014 19:28:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Feb 2014 19:28:26 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ldeluca@us.ibm.com designates 32.97.110.151 as permitted sender) Received: from [32.97.110.151] (HELO e33.co.us.ibm.com) (32.97.110.151) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Feb 2014 19:28:19 +0000 Received: from /spool/local by e33.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 20 Feb 2014 12:27:57 -0700 Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Thu, 20 Feb 2014 12:27:55 -0700 Received: from b03cxnp08025.gho.boulder.ibm.com (b03cxnp08025.gho.boulder.ibm.com [9.17.130.17]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 1DBBA1FF0044 for ; Thu, 20 Feb 2014 12:27:55 -0700 (MST) Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by b03cxnp08025.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s1KJRs6550462784 for ; Thu, 20 Feb 2014 20:27:54 +0100 Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s1KJRsxc030481 for ; Thu, 20 Feb 2014 12:27:54 -0700 Received: from d03nm133.boulder.ibm.com (d03nm133.boulder.ibm.com [9.63.34.21]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s1KJRsHD030477 for ; Thu, 20 Feb 2014 12:27:54 -0700 In-Reply-To: References: To: dev@cordova.apache.org Cc: brian.leroux@gmail.com MIME-Version: 1.0 Subject: Re: [Vote] Cordova 3.4.0 release X-KeepSent: 3E6D3A0B:FDF6B21E-87257C85:006AC461; type=4; name=$KeepSent X-Mailer: IBM Notes Release 9.0 SHF141 June 05, 2013 From: Lisa Seacat DeLuca Message-ID: Date: Thu, 20 Feb 2014 14:27:57 -0500 X-MIMETrack: Serialize by Router on D03NM133/03/M/IBM(Release 9.0.1IF1|November 26, 2013) at 02/20/2014 12:27:54 PM, Serialize complete at 02/20/2014 12:27:54 PM Content-Type: multipart/related; boundary="=_related 006AEF2385257C85_=" X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 14022019-0928-0000-0000-000006A3F80E X-Virus-Checked: Checked by ClamAV on apache.org --=_related 006AEF2385257C85_= Content-Type: multipart/alternative; boundary="=_alternative 006AEF2385257C85_=" --=_alternative 006AEF2385257C85_= Content-Type: text/plain; charset="US-ASCII" Better yet, let's add it to the wiki for the workflow process. http://wiki.apache.org/cordova/CommitterWorkflow it's *kinda* there now but could use some loving from someone who uses it all the time. Lisa Seacat DeLuca Emerging Mobile Software Engineer - Apache Cordova Committer - IBM Master Inventor SWG Open Technologies and Strategy Phone: 1-410-332-2128 | Mobile: 1-415-787-4589 E-mail: ldeluca@us.ibm.com personal website: lisaseacat.com Chat: ldeluca@us.ibm.com Find me on: and within IBM on: 100 East Pratt St 21-2212 Baltimore, MD 21202-1009 United States From: Brian LeRoux To: "dev@cordova.apache.org" Date: 02/20/2014 02:20 PM Subject: Re: [Vote] Cordova 3.4.0 release Sent by: brian.leroux@gmail.com 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. On Thu, Feb 20, 2014 at 11:06 AM, Michal Mocny wrote: > (I was wrong about firefoxos, its just cli thats missing the tag) > > > On Thu, Feb 20, 2014 at 1:58 PM, Brian LeRoux 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 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 wrote: > > > > On 20 February 2014 14:47, Andrew Grieve > 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 wrote: > > > >> > > > >>> On 18 February 2014 23:26, Steven Gill > > 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 > > > >>> > > > > > > --=_alternative 006AEF2385257C85_= Content-Type: text/html; charset="US-ASCII" Better yet, let's add it to the wiki for the workflow process.  http://wiki.apache.org/cordova/CommitterWorkflow

it's *kinda* there now but could use some loving from someone who uses it all the time.


Lisa Seacat DeLuca
Emerging Mobile Software Engineer - Apache Cordova Committer - IBM Master Inventor
SWG Open Technologies and Strategy
Phone: 1-410-332-2128 | Mobile: 1-415-787-4589
E-mail: ldeluca@us.ibm.com
personal website: lisaseacat.com
Chat:Sametime: ldeluca@us.ibm.com
Find me on: LinkedIn: http://www.linkedin.com/in/lisaseacat Twitter: https://twitter.com/LisaSeacat and within IBM on: IBM Connections: https://w3-connections.ibm.com/profiles/html/profileView.do?key=2e1afd56-daa9-428e-8f4a-2fa7516940c0 
IBM

100 East Pratt St 21-2212
Baltimore, MD 21202-1009
United States





From:        Brian LeRoux <b@brian.io>
To:        "dev@cordova.apache.org" <dev@cordova.apache.org>
Date:        02/20/2014 02:20 PM
Subject:        Re: [Vote] Cordova 3.4.0 release
Sent by:        brian.leroux@gmail.com



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.


On Thu, Feb 20, 2014 at 11:06 AM, Michal Mocny <mmocny@chromium.org> wrote:

> (I was wrong about firefoxos, its just cli thats missing the tag)
>
>
> On Thu, Feb 20, 2014 at 1:58 PM, Brian LeRoux <b@brian.io> 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 <bowserj@gmail.com> 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 <sebbaz@gmail.com> wrote:
> > > > On 20 February 2014 14:47, Andrew Grieve <agrieve@chromium.org>
> 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 <sebbaz@gmail.com> wrote:
> > > >>
> > > >>> On 18 February 2014 23:26, Steven Gill <stevengill97@gmail.com>
> > 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
> > > >>>
> > >
> >
>
--=_alternative 006AEF2385257C85_=-- --=_related 006AEF2385257C85_=--