Sure Andrew. Alternatively, you can update the WIki to references the
README.md section.
Personally, I like keeping the release instructions with the project source
code. I know others have different opinions on that.
Michael
On Thu, Apr 18, 2013 at 3:04 PM, Andrew Grieve wrote:
> Michael als
Michael also pointed out that there are also release time instructions in
cordova-app-hello-world's README.md file.
I'd like to move these to the wiki as well.
On Thu, Apr 18, 2013 at 4:16 PM, Andrew Grieve wrote:
> Good catch. I did update the version for cordova-js.
>
> Incrementing the vers
Good catch. I did update the version for cordova-js.
Incrementing the version is in the Android release checklist on the wiki,
but it's not in the list of JIRA sub-tasks. I also failed to update release
notes.
I think I actually like it better on the wiki, and maybe we can just point
to the wiki
Remember to increment the versions. I had to re-tag on Android
because the version wasn't incremented. Did it get incremented on
cordova-js? If not, we'll have to re-tag again.
On Thu, Apr 18, 2013 at 12:49 PM, Andrew Grieve wrote:
> Also wanted to remind that we can still re-tag, but should n
Also wanted to remind that we can still re-tag, but should not be doing any
merges between branches. Cherry-picks only.
On Thu, Apr 18, 2013 at 3:45 PM, Andrew Grieve wrote:
> Alrighty!
>
> Thanks Joe for creating the JIRA issues!
>
> What I just did:
> - branched & tagged cordova-js.
> - close
Alrighty!
Thanks Joe for creating the JIRA issues!
What I just did:
- branched & tagged cordova-js.
- closed all of the sample-app issues after merging it into iOS showed
there to be no changes.
- for Android & iOS: updated the JS, branched & tagged
- updated the CuttingReleases wiki page (still
New goal - let's aim for today!
I'd like to take a look and at CB-2698, but since this is iOS-specific (and
native-code only), I'll go ahead with creating issues & branching the JS.
If CB-2698 gets fixed, we can cherry-pick it.
On Tue, Apr 16, 2013 at 2:45 PM, Giorgio Natili wrote:
> +1
>
> On
+1
On 4/16/13 7:52 PM, "Filip Maj" wrote:
>+1.
>
>So, how do we feel about starting an RC soon?
>
>On 4/16/13 10:19 AM, "Brian LeRoux" wrote:
>
>>It would be ideal to see 2.7 ship before the month is out for sure.
>>
>>
>>On Tue, Apr 16, 2013 at 7:41 AM, Joe Bowser wrote:
>>
>>> I think that t
Sounds good! I'll throw out EOD tomorrow as a target. Has anyone got
anything that they want to get in before we cut?
On Tue, Apr 16, 2013 at 1:52 PM, Filip Maj wrote:
> +1.
>
> So, how do we feel about starting an RC soon?
>
> On 4/16/13 10:19 AM, "Brian LeRoux" wrote:
>
> >It would be ideal
+1.
So, how do we feel about starting an RC soon?
On 4/16/13 10:19 AM, "Brian LeRoux" wrote:
>It would be ideal to see 2.7 ship before the month is out for sure.
>
>
>On Tue, Apr 16, 2013 at 7:41 AM, Joe Bowser wrote:
>
>> I think that this would be a good thing. It'd be nice to get a
>> rele
It would be ideal to see 2.7 ship before the month is out for sure.
On Tue, Apr 16, 2013 at 7:41 AM, Joe Bowser wrote:
> I think that this would be a good thing. It'd be nice to get a
> released lined up for Conf-Month! (Adobe Max, Google IO, JSConf, etc).
>
> On Tue, Apr 16, 2013 at 7:35 AM,
I think that this would be a good thing. It'd be nice to get a
released lined up for Conf-Month! (Adobe Max, Google IO, JSConf, etc).
On Tue, Apr 16, 2013 at 7:35 AM, Andrew Grieve wrote:
> Wanted to see what people thought of trying to get 2.7 out the door in time
> for Adobe Max. The main moti
Wanted to see what people thought of trying to get 2.7 out the door in time
for Adobe Max. The main motivation I see is to have a version that will
work the "future" branch of CLI. 2.6 is missing the plugin_loader.js code
required to load a plugin's JS.
13 matches
Mail list logo
