[openi18n-im:01187] *Schedule* Internet Intranet Input Method Framework (IIIMF) r12.2

Hi all,

Here is the schedule for r12.2 after re-updating the proposed schedule
in IRC meeting:

  Feature Freeze - Mar 01
  API/ABI Freeze - Mar 10
  Code Freeze - Apr 22
  QA Period - Apr 25-27
  Release - Apr 29

All date referring to this freeze time (unless there are other
preferences):

  San Fransisco	06:00 
  New York	09:00 
  Pune		07:30
  Beijing	22:00
  Tokyo		23:00
  Brisbane	00:00 (+1day)

I hope this will assist on each one of you on this project. Feature
freeze is early next week, so let's fire up the feature discussions!

Regards,
Leon

Following is the meeting log---
Online: hideki, jens, tagoh, miura, AlexBanh, ervin, Rob, rogerso,
ssriram

13:00 <@llch> while most of the people is here, can we talk about two
things - schedule and feature freeze date for r12.2?
13:00 < Hideki> Surely!
13:01 <@llch> in the initial schedule, we were proposing three major
releases over 12 months period
13:01 <@llch> so it suppose to be:
13:02 <@llch> Jan-April - release+1
13:02 <@llch> May-Aug - release+2
13:02 <@llch> Sep-Dec - release+3
13:03 <@llch> that will give us three stable version over 1 year period.
how do you guys feel - is it too tight? or just right?
13:03 < Hideki> Yup, let's shoot for it. From my end, namespace based
file I/O API implementation will have an incompatible updates from
current trunk, which I hope it would be final.
13:04 < Hideki> To be in r12.2
13:05 < Hideki> It's just about right, in given your great contribution
on managing the releases.
13:06 <@llch> problem for now is we have lost two months from release+1,
so I am hoping we can freeze a the feature very soon together (properly
quick discussion on mailing list) and i will write it on the feature
page for 12.2
13:07 <@llch> and then we will virtually only got 1 1/2 months time for
development until QA and release engineering period
13:08 < Hideki> No problem! We can freeze the feature really soon.
Probably sooner is better(but I simultaneously :-) want to put namespace
I/O API updates :-)
13:09 < Hideki> In your got-feeling, when would be the right line to
freeze the feature in given condition?
13:10 <@llch> how about Tuesday, 1st March 9:00EST?
13:11 <@llch> API/ABI freeze will be 10 days after this
13:11 < Hideki> Sounds reasonable to me.
13:11 <@llch> and then code freeze can go as it -
13:11 <@llch>   Code Freeze - Apr 22
13:11 <@llch>   QA Period - Apr 25-27
13:11 <@llch>   Release - Apr 29
13:13 <@llch> how do contributors feel about this? rogerso, ssriram,
tagoh, jens, ervin, miura ...?
13:13 < Hideki> Fine with me...actually it is OK to be even earier :-).
I was reading feature freeze as API/ABI freeze :-).
13:14 < rogerso> I would be more concerned about packaging releases :D
13:15 < rogerso> shall I only package the stable releases for Debian
from now on?
13:15 <@llch> Hideki: how about refering API/ABI freeze as contributor
cannot commit anything that break those into svn
13:15 < jens> sounds good to me
13:16 <@llch> rogerso: it is distro/vendor choice :) but if you have
stable releases then i suppose you would want to do that :)
13:18 < rogerso> I suppose so
13:18 <@llch> i will resend the schedule again. let's start to locking
feature for r12.2