I have 5 L1's assigned to myself. [1] - https://wso2.org/jira/browse/CARBON-10154 [2] - https://wso2.org/jira/browse/CARBON-9916 [3] - https://wso2.org/jira/browse/CARBON-9897 [4] - https://wso2.org/jira/browse/CARBON-9515 [5] - https://wso2.org/jira/browse/CARBON-9996
[6] - https://issues.apache.org/jira/browse/QPID-3259 [7] - https://issues.apache.org/jira/browse/QPID-3234 [1] and [2] I can resolve today. [3] and [4] can be resolved Monday. The long-running had been running when I checked last evening. I would rather that we waited until Monday. [5] is actually does not affect our products as we never reuse sessions in MB/Event. It only occurs if someone uses Qpid client libraries with a JMS client. Fixing that even is not trivial [6]. I am concerned about fixing something of this nature at this point. To me it is just tip of the iceberg. There are certain other fundamental issues that we need to fix in Qpid [7]. Therefore shall we leave it out for now and revisit after the release? Danushka On Fri, May 20, 2011 at 2:59 PM, Prabath Siriwardena <prab...@wso2.com>wrote: > Is it possible to see whether we can distribute the L1 issues assigned > to Pradeep/Kalpanie/Senaka/Dhanushka/Shammi and Fazlan..? PMs can you > please have a look.. > > Pradeep - 4 > Kalpanie - 4 > Senaka - 4 > Dhanushka - 4 > Shammi - 4 > Fazlan - 3 > > Thanks & regards, > -Prabath > > On Fri, May 20, 2011 at 12:42 PM, Afkham Azeez <az...@wso2.com> wrote: > > Not a single person has updated the issues yet? > > > > On Fri, May 20, 2011 at 11:49 AM, Afkham Azeez <az...@wso2.com> wrote: > >> > >> All folks who have L1s assigned to them, > >> Please take some time immediately to update the due date in each of your > >> issues. We want to get a clear idea of how long it will take to fix the > >> existing L1s. Please do this immediately. I will review these at 2PM. > >> Thanks > >> Azeez > >> > >> On Fri, May 20, 2011 at 11:34 AM, Afkham Azeez <az...@wso2.com> wrote: > >>> > >>> Folks, > >>> What is the plan to address these? Are people working on these L1s? > After > >>> the branching, you have to make sure that the fixes are committed to > the > >>> trunk as well as the branch. The proper process is, to fix this in the > >>> trunk, create a patch and attach it to the Jira, and then commit that > patch > >>> to the trunk. Please follow that process. > >>> Thanks > >>> Azeez > >>> > >>> -- > >>> Afkham Azeez > >>> Director of Architecture; WSO2, Inc.; http://wso2.com > >>> Member; Apache Software Foundation; http://www.apache.org/ > >>> > >>> email: az...@wso2.com cell: +94 77 3320919 > >>> blog: http://blog.afkham.org > >>> twitter: http://twitter.com/afkham_azeez > >>> linked-in: http://lk.linkedin.com/in/afkhamazeez > >>> > >>> Lean . Enterprise . Middleware > >> > >> > >> > >> -- > >> Afkham Azeez > >> Director of Architecture; WSO2, Inc.; http://wso2.com > >> Member; Apache Software Foundation; http://www.apache.org/ > >> > >> email: az...@wso2.com cell: +94 77 3320919 > >> blog: http://blog.afkham.org > >> twitter: http://twitter.com/afkham_azeez > >> linked-in: http://lk.linkedin.com/in/afkhamazeez > >> > >> Lean . Enterprise . Middleware > > > > > > > > -- > > Afkham Azeez > > Director of Architecture; WSO2, Inc.; http://wso2.com > > Member; Apache Software Foundation; http://www.apache.org/ > > > > email: az...@wso2.com cell: +94 77 3320919 > > blog: http://blog.afkham.org > > twitter: http://twitter.com/afkham_azeez > > linked-in: http://lk.linkedin.com/in/afkhamazeez > > > > Lean . Enterprise . Middleware > > > > _______________________________________________ > > Carbon-dev mailing list > > Carbon-dev@wso2.org > > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > > > > > > > -- > Thanks & Regards, > Prabath > > http://blog.facilelogin.com > http://RampartFAQ.com > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
