Hi All, Please find the issues [1] which are assigned for G-Reg 4.5.0 Beta release ( 06/Jul/12). Our first priority of this week is test and fix all the possible bugs that can be found in 4.5.0 Aplha.
[1]https://wso2.org/jira/browse/REGISTRY/fixforversion/10575 Thanks Ajith On Sat, Jun 23, 2012 at 6:12 AM, Ajith Vitharana <aji...@wso2.com> wrote: > Hi All, > > We can't create new users in latest G-Reg product [1]. > Therefore, we still haven't a proper build to release as the alpha pack. > > [1] https://wso2.org/jira/browse/CARBON-13513 > [2]http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-252/artifact > > Thanks > Ajith > > > On Fri, Jun 22, 2012 at 7:19 PM, Ajith Vitharana <aji...@wso2.com> wrote: > >> >> >> On Fri, Jun 22, 2012 at 9:47 AM, Samisa Abeysinghe <sam...@wso2.com>wrote: >> >>> >>> >>> On Fri, Jun 22, 2012 at 8:16 AM, Senaka Fernando <sen...@wso2.com>wrote: >>> >>>> Hi Samisa, >>>> >>>> The main reason for this delay is a recent commit that got rid of @scr >>>> annotation processing in some of the key components of G-Reg and across the >>>> platform. What we should have been doing is simply get rid of version and >>>> execution phase declarations, but in certain POM files the entire plugin >>>> was removed (which is wrong). >>>> >>>> The actual reasons were revealed yesterday and we had to drag the smoke >>>> testing to validate these. To make best use of the wasted time, we decided >>>> to continue with fixes ensuring that they do not introduce instabilities. >>>> The plan is to announce the availability of the pack once smoke testing is >>>> complete and we are confident that they are no show stoppers. Also, on a >>>> separate front, we are making progress of isolating issues reported by the >>>> 500 odd tests that were added into the G-Reg integration. >>>> >>> >>> I can understand on the reasoning for the slip in the milestone. >>> >>> However, I would still like to highlight the need to have proactive >>> updates on the delays. >>> >>> I am not the release manager for this product, however, there was no >>> update form the team working on the milestone nor the RMs that there is a >>> delay on the milestone, until I sent the ping this morning. >>> If these were discussed withing the team, there is no point, as the >>> community need to see what is going on. If these were discussed on the >>> other threads, I might have missed those, yet this thread was the one that >>> was originally discussing the milestone plans, so there needs to be an >>> update here. >>> >>> Bottom line is: >>> 1. Update proactively >>> 2. Meet the deadlines, somehow, rather than discussing for not meeting >>> those after the deadline elapsed - this means plan for the unexpected >>> >>> I am so aggressive on these milestone deadlines, because, we have more >>> issues to come, as we have not completed the whole test cycle, and we need >>> future time to fix those issues that are yet to come. >>> >> >> Hi All, >> >> We still haven't a successful product build from bamboo due to various >> failures in kernel and platform. >> However, we did a smoke test cycle with the build [1] that announced by >> dimuthuL and we didn't find any blocker. >> We are looking forward to a successful bamboo build to announce as the >> alpha pack. >> >> [1]http://wso2.org/bamboo/browse/WSO2CARBON-PRODUCTS-248/artifact >> >> Thanks >> Ajith >> >> >>> >>> >>>> >>>> Thanks, >>>> Senaka. >>>> >>>> >>>> On Fri, Jun 22, 2012 at 6:43 AM, Samisa Abeysinghe <sam...@wso2.com>wrote: >>>> >>>>> >>>>> >>>>> On Fri, Jun 22, 2012 at 6:39 AM, Samisa Abeysinghe <sam...@wso2.com>wrote: >>>>> >>>>>> >>>>>> >>>>>> On Fri, Jun 22, 2012 at 6:32 AM, Ajith Vitharana <aji...@wso2.com>wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Fri, Jun 22, 2012 at 6:10 AM, Samisa Abeysinghe >>>>>>> <sam...@wso2.com>wrote: >>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Mon, Jun 18, 2012 at 5:48 AM, Samisa Abeysinghe <sam...@wso2.com >>>>>>>> > wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On Sun, Jun 17, 2012 at 11:09 PM, Ajith Vitharana <aji...@wso2.com >>>>>>>>> > wrote: >>>>>>>>> >>>>>>>>>> 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 :) >>>>>>>>>> >>>>>>>>> >>>>>>>>> However, the milestone was supposed to be on Friday, but came on >>>>>>>>> Sunday. So more time anyway means more issues to be fixed. >>>>>>>>> >>>>>>>>> Please do not plan to work on milestone over the weekend. >>>>>>>>> >>>>>>>>> Schedule the next one to a Thursday and deliver at least by >>>>>>>>> Friday. Never plan milestones for a Friday, hereafter. >>>>>>>>> >>>>>>>> >>>>>>>> Looks like we missed M3 deadline set for yesterday? >>>>>>>> >>>>>>> >>>>>>> Hi Samisa, >>>>>>> >>>>>>> We have to wait for a successful build cycle of Bamboo. >>>>>>> >>>>>> >>>>>> If Bamboo is broken and you guys cannot proceed, please make all the >>>>>> noise possible, pick up who broke the build and get them fixed. >>>>>> >>>>>> As experience shows, the build never get fixed without set of folks >>>>>> working and looking at it aggressively and picking and pingging those who >>>>>> broke it to fix it, so some folks got to own this, and unfortunately, >>>>>> this >>>>>> time around, G-Reg team got to be that "some folks" as they are the ones >>>>>> going first with the release :) >>>>>> >>>>>> >>>>>> >>>>>> >>>>>>> We have already fixed enough issues[1] for the alpha milestone and >>>>>>> pack will be available EOD today. >>>>>>> >>>>>> >>>>> Furthermore, fixed issues are of no use, if we do not have a working >>>>> pack, as they cannot be tried and be tested without a pack. >>>>> So meeting the milestone deadline means not only fixing issues, but >>>>> also ensuring the sipping of the packs - and to ship packs, you need to >>>>> manage not only the internal team plans, but also external factors such as >>>>> platform builds - except for acts of God. >>>>> >>>>> Milestone means the pack availability, on time, and all other matters >>>>> are irrelevant form a release perspective. >>>>> >>>>> >>>>> >>>>>>> [1] >>>>>>> https://wso2.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+REGISTRY+AND+fixVersion+%3D+%224.5.0+Alpha%22+AND+status+%3D+Resolved+ORDER+BY+priority+DESC&mode=hide >>>>>>> >>>>>>> Thanks >>>>>>> Ajith >>>>>>> >>>>>>> >>>>>>>> Samisa... >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Ajith Vitharana. >>>>>>> WSO2 Inc. - http://wso2.org >>>>>>> Email : aji...@wso2.com >>>>>>> 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 >>>> >>>> Thanks, >>> Samisa... >>> >>> Samisa Abeysinghe >>> VP Engineering >>> WSO2 Inc. >>> http://wso2.com >>> http://wso2.org >>> >>> >>> >> >> >> -- >> Ajith Vitharana. >> WSO2 Inc. - http://wso2.org >> Email : aji...@wso2.com >> Mobile : +94714631794 >> >> >> > > > -- > Ajith Vitharana. > WSO2 Inc. - http://wso2.org > Email : aji...@wso2.com > Mobile : +94714631794 > > > -- Ajith Vitharana. WSO2 Inc. - http://wso2.org Email : aji...@wso2.com Mobile : +94714631794
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
