We have already done considerable work on making our release schedules consistent and regular. Typically we do a maintenance cycle every 6 weeks. However, we are occasionally driven by supplier timelines (i.e. the .name go live) and, as anyone in software development is familiar, hitting a specific window isn't always feasible.
That being said, now that we're getting better at our consistency and regularity, the next step is to publish something - as long as it's understood that timing may change at a moments notice. Charles Daminato TUCOWS Product Manager [EMAIL PROTECTED] On Sun, 21 Jul 2002 [EMAIL PROTECTED] wrote: > Can we have a planned release schedule for the client and the reason ? > > I need to be able to plan development work and knowing roughly when and why > to expect a new release would make my life much easier > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Charles Daminato > Sent: 20 July 2002 18:00 > To: Andy Coates > Cc: 'Leonid Igolnik'; [EMAIL PROTECTED] > Subject: RE: Suggest Queing > > > This will be up monday (apologies, a small miscommunication on publishing > the doc) > > Charles Daminato > TUCOWS Product Manager > [EMAIL PROTECTED] > > On Sat, 20 Jul 2002, Andy Coates wrote: > > > > New client code v2.57 has an optional flag that allows it to > > > assume domain > > > availability while supplier it down. For more detail about > > > changes to the > > > API see the API documentation. > > > > Any idea when the docs API for v2.57 will be available? > > http://resellers.tucows.com/opensrs/documentation has v2.55 on it. > > > > Thanks, > > Andy. > > > > > >
