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 Tue, 01 Oct 2013 14:50:04 GMT
Thanks for pointing this out Peter - filed CB-4965.


On Tue, Oct 1, 2013 at 6:46 AM, Smith, Peter <peters@fast.au.fujitsu.com>wrote:

> Don't know if this is related to the 'leaking docs' scenario, but FYI
> when we fetched the official 3.0 source zip download yesterday we saw
> there are some inconsistencies between the doc files in the
> cordova-docs.zip and in the plugin zips. For example, compare the
> media.md file in cordova-docs.zip and in cordova-plugin-media.zip. Which
> one is the "correct" one?
>
> Peter.
>
> -----Original Message-----
> From: Marcel Kinard [mailto:cmarcelk@gmail.com]
> Sent: Tuesday, 1 October 2013 2:16 PM
> To: dev@cordova.apache.org
> Subject: Re: Tagging 3.1.0 today?
>
> I noticed that cordova-docs wasn't tagged or branched at the same time
> the platforms were branched into 3.1.x for rc1. This seems to leave open
> the possibility for docs from platforms/plugins master (post 3.1.0) to
> leak into the 3.1.0 docs. I realize that cordova-docs won't get branched
> because of its internal directory structure, but I'm wondering if in the
> future it would be wise to go ahead and do the equivalent of running
> "rake version[3.1.0]" at the time that the 3.1.x branch is created. Then
> during the rc period, docs would behave just like platforms where
> changes would need to be put on 2 branches [master and 3.1.x] / doc
> versions [edge and 3.1.x].
>
> Thoughts?
>
> On Oct 1, 2013, at 12:05 AM, Marcel Kinard <cmarcelk@gmail.com> wrote:
>
> > I believe the docs are now done.
> >
> > https://issues.apache.org/jira/browse/CB-4962
> > https://issues.apache.org/jira/browse/CB-4963
> >
> > The only thing left to do is to change the pointer to use this new
> version.
> >
> > On Sep 30, 2013, at 4:43 PM, Andrew Grieve <agrieve@chromium.org>
> wrote:
> >
> >> Marcel - one big thing that hasn't happened yet is docs.
>
>
>

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