First, thanks to all who went in and tested 1.10 beta so far and for all the bug fixing, triaging, tallying, etc... After 2 months of beta testing, I feel confident that we are now past the issue discovery phase of the beta.
I will be putting together a wiki page categorizing issues 110Beta2Items -> from what I can see, most of potential blockers are in (1) tiki_objects/categorization/tagging (2) themes/UI (3) Wysiwyg (4) Image/file galleries, and a few in (5) calendar and (6) user login. Many of the past critical bugs have already been fixed, however, new issues have also been discovered - but these are less critical in nature so this indicates we are moving forward.
Moving into the second phase of the beta, which focus on fixing, I am going to need much help. One of the first things that I want to get done is to have TRUNK branch created. At the point of this creation of TRUNK branch from current 1.10 branch, we will also also tag/package beta 2. I would hope as soon as May 24 but it is more important to make sure volunteer commitment for the following administrative activities is available first. In this process, I see my role as, and commit to coordinating, aggregating feedback, and making decisions on what is a blocker for 1.10, as well as what should be committed into 1.10 or TRUNK.
Volunteers are needed for the following. More than one person is encouraged to volunteer for each item. Please indicate in which column of commitment level you are in. In my mind, we need at least 7 points in each item for it to be a "green light".
|Volunteers needed for...||Will do! (4)||Will do but maybe delay due to time limitations (3)||Will help out a bit for sure (2)||Will help out if I have extra time (1)|
|once every 2 weeks to merge 1.10 branch to TRUNK branch||...||nkoth,||...||...|
|package beta 2 and document procedures (this will be the first time in SVN and all our previous docs are in CVS)||...||rodrigo (aka sampaioprimo)||...||...|
|help classify issues into 110Beta2Items||...||chibaguy, xavi||...||...|
|help do focused testing and bug/fix verification (by this I mean create/follow some test plan and document steps taken, and not just in the course of one's own use)||...||chibaguy (themes),mmln||zorp||...|