[openi18n-im:01334] Code Frozen and QA Period - What does it mean to all of us [was: Re: code freeze for 12.2 release]

Dear contributors and users,

Firstly congratulations on all contributors, your efforts in r12.2
development cycle has been outstanding. Without all your efforts and hard
work into the current code base, the upcoming version wouldn't be that
far. It isn't finished yet, let's close this release next week!

Secondly, as usual, I encourage all of the subscribers on this
mailing list to give it a go on the existing devel frozen code.

Thirdly, on our process in this period:

1. Single point reviewing system
To ensure the critical fixes has little impact on other aspects as 
possible (i.e. new bugs introduction, regressions), let's use a single 
personnel to approve the patch. 

Steps of getting a patch in:
  a. submit a bug into mantis
  b. set the severity and describe it appropriately
  c. A personnel (I am sponsoring myself to do it this time,) to review 
the patch and the problem
  d.1 once approved, patch can go into branches/r12_2
  d.2 if it is not approved because of the sake of stability, patch can go 
into trunk

I hope you have been comfortable with this sort of system.  Let me know if 
you got any concerns.


2. Testing packages:
svn will be the point to go and Jens will compose tar ball throughout the 
week next week. And I think we got some hands up for building distro's 
packages. Let me know the location I can fetch and I will put it on the web.


3. Testing areas:
 - all functional tests
   - server, client frameworks, LEs
 - all usability
   - GUI
 - new feature area
   - test on the new features that we got
 - run your existing unit testing if you haven't do so

IIIMF is a rich framework, we need every resource we got to cover the 
testing. If you find any problems (either critical or not, let's post it 
to mantis so that we can *track* and *address* on r12.2, or next release)

Lawrence, our current QA "team" :) will go into more systematic way by 
using test cases to complete the IIIMF QA period. 

Let me know how you think on the overall process.

Cheers, Leon

> > Code Freeze      22 April 2005  14:00 UTC
> > QA Period Ends   27 April 2005
> > Release          29 April 2005
> 
> The current im-sdk/trunk has been branched to r12_2 at revision 2578.
> Only fixes to critical bugs should be committed from now on to r12_2.
> 
> May the testing begin!
> 
> Thank you, Jens
> 

-- 
 Leon Ho                       <llch at redhat.com>
 Supervisor, I18N Engineering  Red Hat Asia-Pacific   
 Legal:           http://apac.redhat.com/disclaimer