cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Grieve <agri...@chromium.org>
Subject Re: Tagging 3.1.0 today?
Date Wed, 02 Oct 2013 19:15:06 GMT
Blog post is primed and ready :)


On Wed, Oct 2, 2013 at 8:14 PM, Andrew Grieve <agrieve@chromium.org> wrote:

> For docs - do we include the docs for 3.1.0 only? otherwise the zip would
> be massive.
>
> I don't feel strongly one way or the other about plugins/tools, but here's
> some thoughts:
> Leave plugins out. Rationale: If we were to release them as zips, we
> should do so at the same time we do plugin releases.
> CLI out of the box is set up to download platforms from git, if we did
> distribute them as zips, we should re-configure it to get the platform from
> the zip, so, no to CLI.
> Plugman might be reasonable to include, but if we're skipping on the
> plugins, might as well skip on plugman
>
>
> On Wed, Oct 2, 2013 at 8:09 PM, Steven Gill <stevengill97@gmail.com>wrote:
>
>> I don't want to hound, but the sooner I get feedback the sooner we
>> release!
>>
>> Out
>>  - OSX
>>
>> In
>> platforms
>> - Android
>> - iOS
>> - BB10
>> - Windows Phone 7 & 8
>> - Windows 8
>> - FFOS
>> - Docs
>> - Cordova JS
>> - Hello World App
>> - Mobile Spec
>>
>> Not Sure
>> - Plugins
>> - CLI
>> - Plugman
>>
>> Once I upload this release, all we have left is to publish blog post and
>> announce!
>>
>> Andrew, can you take care of publishing the blog post and changing the
>> site
>> to reflect 3.1.0 instead of 3.0.0? Once that is done, email the list. I
>> can
>> announce on twitter using @apachecordova
>>
>>
>> On Wed, Oct 2, 2013 at 11:49 AM, Joe Bowser <bowserj@gmail.com> wrote:
>>
>> > On Wed, Oct 2, 2013 at 11:46 AM, Andrew Grieve <agrieve@chromium.org>
>> > wrote:
>> > > Sorry, was away from my computer for a while there.
>> > >
>> > > Joe, sounds like what happened was that you pushed the tag without
>> > pushing
>> > > the branch. That has happened a few times in the past by others
>> > (including
>> > > myself). No biggie. The ASF repos disable git push --force, so I don't
>> > > think it's even possible for tampering to happen.
>> >
>> > I want github back! Apache is breaking git. :(
>> >
>> > As far as tampering, it's totally possible for it to happen.  Sadly,
>> > it looks exactly like this.  I apologize for getting super aggro about
>> > the git screw-up.
>> >
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message