incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <...@adobe.com>
Subject Re: 1.3 Release
Date Tue, 13 Dec 2011 04:40:48 GMT
BlackBerry tagged 1.3.0rc2

On 11-12-12 8:12 PM, "Jesse" <purplecabbage@gmail.com> wrote:

>Windows Phone repo is tagged 1.3.0rc2
>
>
>On Mon, Dec 12, 2011 at 1:54 PM, Simon MacDonald
><simon.macdonald@gmail.com>wrote:
>
>> I just tagged Android to 1.3.0rc2 which is basically unchanged from
>> 1.3.0rc1. I'm going to send out my rough test plan either later today
>> or early tomorrow.
>>
>> Simon Mac Donald
>> http://hi.im/simonmacdonald
>>
>>
>>
>> On Thu, Dec 8, 2011 at 8:15 PM, Steven Gill <steveng@adobe.com> wrote:
>> > Just a reminder that code freeze and rc2 will be on Monday. I am going
>> > make a blog post for the changes in 1.3 when we release on Friday.
>> >
>> > I will take a look at the short logs and issue tracker, but was
>>wondering
>> > if any of you have anything to add other than general bug fixes.
>> >
>> > Also thinking about doing a post on how to upgrade from 1.2 to 1.3.
>> >
>> > -Steve
>> >
>> > On 11-12-07 12:44 PM, "Brian LeRoux" <b@brian.io> wrote:
>> >
>> >>we need to be consistent on tag naming when we automate release
>>building
>> >>
>> >>
>> >>On Wed, Dec 7, 2011 at 2:04 AM, Jesse <purplecabbage@gmail.com> wrote:
>> >>> Windows Phone has been tagged
>> >>> https://github.com/callback/callback-windows-phone/tags
>> >>> However, It is tagged 1.3.rc1
>> >>>
>> >>> On Thu, Dec 1, 2011 at 1:57 PM, Filip Maj <fil@adobe.com> wrote:
>> >>>
>> >>>> + ... 1 ?
>> >>>>
>> >>>> On 11-12-01 1:11 PM, "Simon MacDonald" <simon.macdonald@gmail.com>
>> >>>>wrote:
>> >>>>
>> >>>> >Do we need to vote on this? Sorry couldn't resist.
>> >>>> >
>> >>>> >Simon Mac Donald
>> >>>> >http://hi.im/simonmacdonald
>> >>>> >
>> >>>> >
>> >>>> >On Thu, Dec 1, 2011 at 4:09 PM, Michael Brooks
>> >>>> ><michael@michaelbrooks.ca>wrote:
>> >>>> >
>> >>>> >> Simon - I agree. I really like a release schedule that
uses
>>release
>> >>>> >> candidates and reserves a few days for solid testing. I
>>appreciate
>> >>>>you
>> >>>> >> suggesting it for 1.3.0!
>> >>>> >>
>> >>>> >> Ken - There's a JIRA and GitHub ticket for the issue, so
we can
>> >>>>move the
>> >>>> >> conversation there. I could use some help testing it once
the
>>patch
>> >>>>is
>> >>>> >>in
>> >>>> >> place.
>> >>>> >>
>> >>>> >> Michael
>> >>>> >>
>> >>>> >> On Thu, Dec 1, 2011 at 1:05 PM, Simon MacDonald
>> >>>> >> <simon.macdonald@gmail.com>wrote:
>> >>>> >>
>> >>>> >> > I have no problem with the change of tag name or you
getting
>>code
>> >>>>into
>> >>>> >> the
>> >>>> >> > release by the 12th. I'm just thinking we need to
leave a few
>> days
>> >>>> >>13-15
>> >>>> >> to
>> >>>> >> > do some testing and make sure we haven't broken anything.
>> >>>> >> >
>> >>>> >> > Simon Mac Donald
>> >>>> >> > http://hi.im/simonmacdonald
>> >>>> >> >
>> >>>> >> >
>> >>>> >> > On Thu, Dec 1, 2011 at 4:03 PM, Michael Brooks
>> >>>> >><michael@michaelbrooks.ca
>> >>>> >> > >wrote:
>> >>>> >> >
>> >>>> >> > > I like it Simon.
>> >>>> >> > >
>> >>>> >> > > I'd suggest tagging as "1.3.0rc1" instead of
"1.3.0_rc1"
>> >>>> >> > >
>> >>>> >> > > I would like to squeak in OS X support for BlackBerry.
>>Should I
>> >>>>have
>> >>>> >> this
>> >>>> >> > > completed by Monday December 5th or Monday December
12th?
>> >>>> >> > >
>> >>>> >> > > Michael
>> >>>> >> > >
>> >>>> >> > > On Thu, Dec 1, 2011 at 12:44 PM, Simon MacDonald
>> >>>> >> > > <simon.macdonald@gmail.com>wrote:
>> >>>> >> > >
>> >>>> >> > > > Hey all,
>> >>>> >> > > >
>> >>>> >> > > > For the upcoming 1.3 release can we throw
down a few
>>dates?
>> >>>>Our
>> >>>> >>last
>> >>>> >> > > > release, 1.2, was tagged and released the
same day. I
>>can't
>> >>>>say
>> >>>> >>for
>> >>>> >> > > certain
>> >>>> >> > > > but I'm guessing the rush was to get it
out before the
>>Adobe
>> >>>> >> > announcement
>> >>>> >> > > > but we are lucky we didn't have major problems
with that
>> >>>>release
>> >>>> >>as
>> >>>> >> we
>> >>>> >> > > were
>> >>>> >> > > > a bit light on end to end testing.
>> >>>> >> > > >
>> >>>> >> > > > Since we are thinking about releasing 1.3
on December
>>16th I
>> >>>> >>thought
>> >>>> >> > I'd
>> >>>> >> > > > work back a bit to identify some milestones.
>> >>>> >> > > >
>> >>>> >> > > > Dec 5th - Tag all repos as 1.3.0_rc1
>> >>>> >> > > > Dec 12th - Tag all repos as 1.3.0_rc2 and
implement a code
>> >>>>freeze
>> >>>> >> > > > Dec 13th - Dec 14th - testing, testing,
testing
>> >>>> >> > > > Dec 15th - Tag all repos as 1.3.0
>> >>>> >> > > > Dec 16th - package and release PhoneGap
1.3
>> >>>> >> > > >
>> >>>> >> > > > Basically we shouldn't be adding new code
the week of the
>> 12th
>> >>>> >>unless
>> >>>> >> > we
>> >>>> >> > > > have broken something that we discover doing
regression
>> >>>>testing.
>> >>>> >> > > >
>> >>>> >> > > > These are only suggestions folks but what
do you think
>>about
>> a
>> >>>> >>little
>> >>>> >> > > more
>> >>>> >> > > > process this time around?
>> >>>> >> > > >
>> >>>> >> > > > Simon Mac Donald
>> >>>> >> > > > http://hi.im/simonmacdonald
>> >>>> >> > > >
>> >>>> >> > >
>> >>>> >> >
>> >>>> >>
>> >>>>
>> >>>>
>> >
>>


Mime
View raw message