Hi All,

G-Reg 4.5.0 M2 is available to download and following is the plan for the
next milestone build.
We are going to fix another 41 issues [1] (all remain L1 and L2) in next
milestone build( Friday ).

Tasks - 5 (L1)
improvements - 1
L1 bugs - 13
L2 bugs -  22

Already fixed issues for the  next build - 4   :)

I'll redistribute those issues among the G-reg team members, with the
availability for the release works.

[1]https://wso2.org/jira/browse/REGISTRY/fixforversion/10568

Thanks
Ajith

On Mon, Jun 11, 2012 at 4:16 AM, Ajith Vitharana <[email protected]> wrote:

>
>
> On Sat, Jun 9, 2012 at 1:32 PM, Senaka Fernando <[email protected]> wrote:
>
>> Hi Samisa,
>>
>> On Sat, Jun 9, 2012 at 5:54 AM, Samisa Abeysinghe <[email protected]>wrote:
>>
>>>
>>>
>>> On Fri, Jun 8, 2012 at 9:20 PM, Ajith Vitharana <[email protected]> wrote:
>>>
>>>>
>>>>
>>>> On Fri, Jun 8, 2012 at 10:14 AM, Samisa Abeysinghe <[email protected]>wrote:
>>>>
>>>>>
>>>>>
>>>>> On Fri, Jun 8, 2012 at 10:12 AM, Ajith Vitharana <[email protected]>wrote:
>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, Jun 6, 2012 at 7:34 PM, Ajith Vitharana <[email protected]>wrote:
>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> Currently, trunk is completely unstable (compilation errors, server
>>>>>>> startup errors , recent changes to kernal ) due to those issues we still
>>>>>>> haven't a stable G-Reg pack for the first milestone (4.5.0 M1).
>>>>>>>
>>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> We were able to fix registry integration test failures (89). Only
>>>>>> contentSearch test is remaining and Eranda working on it.
>>>>>>
>>>>>> @Eranda , Please make sure to fix it before the M1 release.
>>>>>>
>>>>>
>>>>>
>>>>> Are we on track to fix all issues that were allocated for M1?
>>>>>
>>>>
>>>> Hi Samisa,
>>>>
>>>> We have remaining  2 tasks , 1 new feature and 2 improvements for the
>>>> G-Reg 4.5.0 and others are fixed for M1.
>>>>
>>>> Tasks
>>>> https://wso2.org/jira/browse/REGISTRY-711
>>>> https://wso2.org/jira/browse/REGISTRY-733
>>>>
>>>> New feature
>>>> https://wso2.org/jira/browse/REGISTRY-690
>>>>
>>>> Improvements (Not major)
>>>> https://wso2.org/jira/browse/REGISTRY-849
>>>> https://wso2.org/jira/browse/REGISTRY-911
>>>>
>>>> Find the issues are fixed for M1.
>>>>
>>>> [1]
>>>> https://wso2.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+REGISTRY+AND+fixVersion+%3D+%224.5.0+M1%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide
>>>>
>>>> We are going to announce  the M1 pack soon, after fixing all the
>>>> registry test failures.
>>>>
>>>
>>>
>>> Did we slip the deadline for M1?
>>>
>>> If we slip on M1, M2 will slip too. Please make sure to adjust the
>>> timeliness accordingly.
>>>
>>> It is really critical that we have weekly M1s somehow. It looks like we
>>> missed this week's one :(
>>>
>>
>> Yes, we have slipped M1. But, we are trying our best to make it available
>> soon (by at least Monday morning LKT). There was a major platform change
>> introduced during the last week (SUPER_TENANT constants) in the kernel, but
>> the product teams had to test and fix products which left the entire
>> platform unstable. We managed to stabilize G-Reg with all except one test
>> case fixed by the M1 deadline. But, since there was one failure, we wanted
>> to fix that as well before announcing the M1. AFAIU, Ajith fixed it today.
>> So, we should be able to have a stable build soon.
>>
>
> Hi All,
>
> G-Reg 4.5.0-M1 is available to download and this is the plan for second
> milestone(G-Reg 4.5.0 M2).
>
> We are going to fix 56 issues in second milestone[1] (next Friday), it
> contain all the L1 and L2 issues.
> I have assigned 8 issues (L1 and L2) for each person of G-Reg team for M2.
>
> @ G-Reg team, you should follow the process.
>
> 1) Pick the L1 issues early.
> 2) Run unit tests and integration tests before any commit.
> 3) Test your fixes in product, to prevent any regression issues.
> 4) Include the JIRA numbers correctly in commit messages.
> 5) Select the correct milestone as the fix version of the resolved issues.
>
> [1]
> https://wso2.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+REGISTRY+AND+resolution+%3D+Unresolved+AND+fixVersion+%3D+%224.5.0+M2%22+ORDER+BY+priority+DESC&mode=hide
>
> Thanks
> Ajith
>
>
>> Thanks,
>> Senaka.
>>
>>>
>>>
>>>
>>>>
>>>> Thanks
>>>> Ajith
>>>>
>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>> Ajith
>>>>>>
>>>>>> Thanks
>>>>>> Ajith
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Thanks
>>>>>>> Ajith
>>>>>>>
>>>>>>> On Sat, Jun 2, 2012 at 9:57 PM, Senaka Fernando <[email protected]>wrote:
>>>>>>>
>>>>>>>> Hi all,
>>>>>>>>
>>>>>>>> Please note that there are strictly no improvements and/or new
>>>>>>>> features beyond this point. Also, please note that all tasks, 
>>>>>>>> improvements
>>>>>>>> and new features are required to be completed and made available for 
>>>>>>>> M1 due
>>>>>>>> next Thursday. RMs, please make a list of everything that cannot be
>>>>>>>> completed and start discussing about how those are going to be 
>>>>>>>> introduced
>>>>>>>> or whether those are going to postponed.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Senaka.
>>>>>>>>
>>>>>>>> --
>>>>>>>> *Senaka Fernando*
>>>>>>>> Member - Integration Technologies Management Committee;
>>>>>>>> Technical Lead; WSO2 Inc.; http://wso2.com*
>>>>>>>> Member; Apache Software Foundation; http://apache.org
>>>>>>>>
>>>>>>>> E-mail: senaka AT wso2.com
>>>>>>>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>>>>>>>> Linked-In: http://linkedin.com/in/senakafernando
>>>>>>>>
>>>>>>>> *Lean . Enterprise . Middleware
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Ajith Vitharana.
>>>>>>> WSO2 Inc. - http://wso2.org
>>>>>>> Email  :  [email protected]
>>>>>>> Mobile : +94714631794
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Ajith Vitharana.
>>>>>> WSO2 Inc. - http://wso2.org
>>>>>> Email  :  [email protected]
>>>>>> Mobile : +94714631794
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Ajith Vitharana.
>>>> WSO2 Inc. - http://wso2.org
>>>> Email  :  [email protected]
>>>> Mobile : +94714631794
>>>>
>>>>
>>>>
>>>
>>
>>
>> --
>> *Senaka Fernando*
>> Member - Integration Technologies Management Committee;
>> Technical Lead; WSO2 Inc.; http://wso2.com*
>> Member; Apache Software Foundation; http://apache.org
>>
>> E-mail: senaka AT wso2.com
>> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818
>> Linked-In: http://linkedin.com/in/senakafernando
>>
>> *Lean . Enterprise . Middleware
>>
>>
>
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  [email protected]
> Mobile : +94714631794
>
>
>


-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  [email protected]
Mobile : +94714631794
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to