Hi Janaka, Immediate/blocking requirements were fixed in 1.0.1 branch[1] and we will do a patch release of 1.0.0. All the features and major improvements will go with 1.1.0 and has planed to release at least an Alpha by the end of Q1. [2], [3] and [4] issues reported by Chandana have already been fixed in [1].
/Ruchira [1] https://github.com/wso2/enterprise-store/tree/es-1.0.1-apm-reg [2] https://wso2.org/jira/browse/STORE-391 [3] https://wso2.org/jira/browse/STORE-394 [4] https://wso2.org/jira/browse/STORE-395 On Tue, Mar 11, 2014 at 7:16 AM, Janaka Ranabahu <jan...@wso2.com> wrote: > Hi Guys, > > Will these limitations get fixed in the upcoming release? If so do we have > a timeline for that? > > Thanks, > Janaka > > > On Sat, Mar 8, 2014 at 10:43 AM, Chandana Napagoda <chand...@wso2.com>wrote: > >> Hi Samisa >> >> In addition to above issue, ES is still not supporting all the RXT >> configuration elements(ex: unbounded table option) which are currently >> supported by G-Reg. We have reported JIRAs to get those added to coming up >> releases. >> >> Regards, >> Chandana >> >> >> On Mar 8, 2014 7:09 AM, "Janaka Ranabahu" <jan...@wso2.com> wrote: >> >>> Hi Samisa, >>> >>> IMO, it should be ES. But the current ES architecture does not pick new >>> RXT types automatically and some configurations to jaggery config files are >>> required to show the new asset in both Store and Publisher[1]. Until we >>> have a more flexible way of generating the Store and Publisher UI, I >>> believe we have to stick with G-Reg. >>> >>> Thanks, >>> Janaka >>> >>> [1] https://docs.wso2.org/display/ES100/Adding+a+New+Asset+Type >>> >>> >>> On Fri, Mar 7, 2014 at 8:08 PM, Samisa Abeysinghe <sam...@wso2.com>wrote: >>> >>>> We used to position G-Reg as a store of anything with RXT. >>>> >>>> Now what ES is there, and is more capable, do we propose the users use >>>> ES or G-Reg RXT like use cases? >>>> >>>> Thanks, >>>> Samisa... >>>> >>>> >>>> Samisa Abeysinghe >>>> >>>> Vice President Developer Evangelism >>>> >>>> WSO2 Inc. >>>> http://wso2.com >>>> >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> Architecture@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> *Janaka Ranabahu* >>> Senior Software Engineer; WSO2 Inc.; http://wso2.com >>> >>> >>> * E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861 >>> <%2B94%20718370861>* >>> >>> Lean . Enterprise . Middleware >>> >>> _______________________________________________ >>> Architecture mailing list >>> Architecture@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> _______________________________________________ >> Architecture mailing list >> Architecture@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *Janaka Ranabahu* > Senior Software Engineer; WSO2 Inc.; http://wso2.com > > > * E-mail: jan...@wso2.com <http://wso2.com>**M: **+94 718370861 > <%2B94%20718370861>* > > Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > Architecture@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Ruchira Wageesha**Associate Technical Lead* *WSO2 Inc. - lean . enterprise . middleware | wso2.com <http://wso2.com>* *email: ruch...@wso2.com <ruch...@wso2.com>, blog: ruchirawageesha.blogspot.com <http://ruchirawageesha.blogspot.com>, mobile: +94 77 5493444*
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
