[openi18n-im:01384] Re: r12.4 and r12.2.1 schedule draft

Hi all,
I have updated the wiki after aligning myself with Jens. Here is my
proposal. I was contemplating whether to perform QA before or after beta
release and finally decided to go with after. If things does not turn
out well, I will then adjust accordingly.

r12.4 
      * Feature Freeze - May 27
      * API/ABI Freeze - Jun 30 

      * r12.3-beta1 - Jul 15
      * QA Period - Jul 18-20
      * r12.3-beta2 - Aug 5
      * QA Period - Aug 8-10 

      * Code Freeze - Aug 19 

      * r12.3-rc1 - Aug 19
      * QA Period - Aug 22-23
      * r12.3-rc2 - Aug 26
      * QA Period - Aug 29-31 

      * Release - Aug 31 

Thanks,
Lawrence

On Wed, 2005-05-18 at 16:49, Jens Petersen wrote:
> Leon Ho wrote:
> > r12.2.1
> >   Code Freeze - Jun 21
> >   QA Period - Jun 22-24
> >   Release - Jun 28
> 
> So there should be an rc (12.2.0.9x) say Jun 21.
> 
> > r12.4
> >   Feature Freeze - May 27
> >   API/ABI Freeze - Jun 30
> >     r12.3-beta1
> 
> How about July 15 for beta1
> 
> >     r12.3-beta2
> 
> and Aug 5 for the beta2?
> 
> All 12.3 releases are development releases anyway, so I would suggest naming the 
> betas just 12.3.x.
> 
> >   Code Freeze - Aug 19
> Implementation Freeze - Aug 12
> 
> Although the schedule is tight enough as it is, I was thinking it might be 
> better to make an "Implementation Freeze" before the Code (devel) Freeze to give 
> more time for release stabilisation and allow developers also to concentrate on 
> bugfixing at the end of the cycle.
> 
> >     r12.3-rc1
> 
> Aug 19
> 
> >     r12.3-rc2
> 
> and Aug 26?
> 
> Again I'd prefer 12.3.9x for RC releases.
> 
> >   QA Period - Aug 22-26
> >   Release - Aug 31
> 
> Does anyone know when the O'bon holiday is in Japan this year,
> I hope it won't overlap too much with our release schedule?
> 
> Jens