Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of khawkins@salesforce.com
 designates 64.18.3.98 as permitted sender)
From: Kevin Hawkins <khawkins@salesforce.com>
To: "callback-dev@incubator.apache.org" <callback-dev@incubator.apache.org>
Date: Sun, 21 Oct 2012 15:07:35 -0700
Subject: Best practices for contributing near a release boundary
Thread-Topic: Best practices for contributing near a release boundary
Thread-Index: Ac2v2HmZDF6pqgkyQyeqDC9rYkoIoQ==
Message-ID: 
 <AB80F08003696A41825710BDB0FE7A91712105EE@EXSFM-MB03.internal.salesforce.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_AB80F08003696A41825710BDB0FE7A91712105EEEXSFMMB03intern_"
MIME-Version: 1.0

--_000_AB80F08003696A41825710BDB0FE7A91712105EEEXSFMMB03intern_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

I've got a couple of "Improvements" I'd like to contribute to the iOS side =
of the Cordova project.  However, I know we're super close to the 2.2 relea=
se boundary, and I don't feel strongly that these changes would need to be =
in 2.2-actually, I feel strongly that, process-wise, this is *not* the time=
 to commit feature updates in a release cycle, at least to the imminent rel=
ease.

So what's the best course of action here?  Would it be better to attach git=
 patches to the Improvement items I create?  Or some other approach?

Thanks,
Kevin


--_000_AB80F08003696A41825710BDB0FE7A91712105EEEXSFMMB03intern_--