incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shazron <shaz...@gmail.com>
Subject Re: tag rc monday?
Date Wed, 23 May 2012 22:11:19 GMT
+1

On Wed, May 23, 2012 at 2:39 PM, Michael Brooks <michael@michaelbrooks.ca>wrote:

> Hello everyone,
>
> Since there has been no objections, let's aim to cut 1.8.0rc1 tomorrow.
>
> How does that sound to everyone?
>
> Michael
>
> On Tue, May 22, 2012 at 10:22 PM, Michael Brooks
> <michael@michaelbrooks.ca>wrote:
>
> > Thanks Jesse!
> >
> > Realistically, I think CB-608 and it's sub-tasks should be reassigned to
> > 1.9.0.
> >
> > Michael
> >
> >
> > On Tue, May 22, 2012 at 3:20 PM, Jesse <purplecabbage@gmail.com> wrote:
> >
> >> I only believe 1 issue in WP7 is a 1.8.0 blocker and that is involving a
> >> couple failing file tests. ( CB-629 )
> >> I have not looked at the WP7 subtask of CB-608, is this a blocker for
> >> 1.8.0?
> >>
> >>
> >>
> >>
> >> On Tue, May 22, 2012 at 2:19 PM, Michael Brooks <
> michael@michaelbrooks.ca
> >> >wrote:
> >>
> >> > I'm kicking this thread back to life.
> >> >
> >> > When are we scheduling the 1.8.0rc1 release? Originally, it was slated
> >> for
> >> > yesterday. At the moment, there are 37 outstanding issues in JIRA. Are
> >> > these blockers for 1.8.0 or should some be moved to 1.9.0?
> >> >
> >> > I've moved a couple documentation issues to 1.9.0 but the remaining 11
> >> > should at least have some platform-specific content added.
> >> >
> >> > 12 Android
> >> > 06 Bada
> >> > 05 BlackBerry
> >> > 03 CordovaJS
> >> > 11 Docs
> >> > 09 iOS
> >> > 04 webOS
> >> > 06 WP7
> >> >
> >> > Michael
> >> >
> >> > On Thu, May 17, 2012 at 1:53 AM, Brian LeRoux <b@brian.io> wrote:
> >> >
> >> > > Has there ever *not* been outstanding doc issues? ;)
> >> > >
> >> > > the latter *could* move to 1.9
> >> > >
> >> > > On Wed, May 16, 2012 at 11:18 PM, Michael Brooks
> >> > > <michael@michaelbrooks.ca> wrote:
> >> > > > A large number of the outstanding issues are around documentation.
> >> For
> >> > > each
> >> > > > platform, there are documentation issues for:
> >> > > >
> >> > > > - Writing the upgrade (1.8.0 and 1.7.0) guide
> >> > > > - Writing the permission name guide
> >> > > >
> >> > > > Michael
> >> > > >
> >> > > > On Wed, May 16, 2012 at 2:13 PM, Shazron <shazron@gmail.com>
> wrote:
> >> > > >
> >> > > >> iOS should be fine to tag.
> >> > > >>
> >> > > >> On Wed, May 16, 2012 at 10:50 AM, Jesse <purplecabbage@gmail.com
> >
> >> > > wrote:
> >> > > >> > Also, Monday is a stat in Canada, not sure if that matters.
> >> > > >> >
> >> > > >> > On Wed, May 16, 2012 at 10:40 AM, Filip Maj <fil@adobe.com>
> >> wrote:
> >> > > >> >
> >> > > >> >> I'm fine with it. Friendly observation that there
are still a
> >> _ton_
> >> > > of
> >> > > >> >> issues slated for 1.8 to be resolved. We're less
than half way
> >> (61
> >> > > out
> >> > > >> of
> >> > > >> >> 132 issues).
> >> > > >> >>
> >> > > >> >> On 5/16/12 2:13 AM, "Brian LeRoux" <b@brian.io>
wrote:
> >> > > >> >>
> >> > > >> >> >I'd say keep focused on the CordovaView and
if this release
> >> has no
> >> > > >> >> >excitement for Android then thats fine. Lets
get this thing
> >> > buried.
> >> > > >> >> >
> >> > > >> >> >On Wed, May 16, 2012 at 10:36 AM, Joe Bowser
<
> >> bowserj@gmail.com>
> >> > > >> wrote:
> >> > > >> >> >> Android with CordovaWebView won't be ready
on Monday. We
> >> should
> >> > > >> decide
> >> > > >> >> >>soon
> >> > > >> >> >> whether to ship the code we have in that
branch or defer.
> If
> >> we
> >> > > >> defer,
> >> > > >> >> >>we
> >> > > >> >> >> need to start working on other fixes asap
so we have
> >> something
> >> > to
> >> > > >> show
> >> > > >> >> >>for
> >> > > >> >> >> this release on Android.
> >> > > >> >> >> On May 15, 2012 9:55 PM, "Brian LeRoux"
<b@brian.io>
> wrote:
> >> > > >> >> >>
> >> > > >> >> >>> how ya guys feeling on 1.8?
> >> > > >> >> >>>
> >> > > >> >>
> >> > > >> >>
> >> > > >> >
> >> > > >> >
> >> > > >> > --
> >> > > >> > @purplecabbage
> >> > > >> > risingj.com
> >> > > >>
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >> @purplecabbage
> >> risingj.com
> >>
> >
> >
>

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