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 <[email protected]>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 > <[email protected]>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 > > >
