Re: Shall we plan for a 4.1.0-M2 developer preview?

Great! Thanks Nirmal! On Mon, Oct 6, 2014 at 11:03 AM, Nirmal Fernando wrote: > Ya, Imesh.. I was worrying about breaking existing clients (including our > own UI /CLI) . Yes, I also felt the same after thinking a bit more and > initiated a thread here: Versioning Stratos REST API > > On Mon, O

Re: Shall we plan for a 4.1.0-M2 developer preview?

Ya, Imesh.. I was worrying about breaking existing clients (including our own UI /CLI) . Yes, I also felt the same after thinking a bit more and initiated a thread here: Versioning Stratos REST API On Mon, Oct 6, 2014 at 10:45 AM, Imesh Gunaratne wrote: > Hi Nirmal, > > I think that's the appro

Re: Shall we plan for a 4.1.0-M2 developer preview?

Hi Nirmal, I think that's the approach most of the well known APIs take [1, [2], [3]: - Document APIs by version - If version is not given in the context request is redirected to the latest version - If version is specified relevant API is invoked - Deprecate and remove old API versions according

Re: Shall we plan for a 4.1.0-M2 developer preview?

Another way to version the APIs is to use the Accept header with the default URL (means default URL should always be the latest). But this would make are current API users to change their clients to set the Accept header to the correct version. On Sun, Oct 5, 2014 at 2:18 PM, Nirmal Fernando wrot

Re: Shall we plan for a 4.1.0-M2 developer preview?

Hi Imesh, Since we didn't have a version in the context in 4.0, I think we can't redirect requests without a version to the latest, isn't it? Yes, plan is to introduce a version in the context and mark current APIs as deprecated. I'll start a separate thread on new REST API design. On Sat, Oct 4,

Re: Shall we plan for a 4.1.0-M2 developer preview?

Have we version-ed the APIs? IMO we should add the API version to the context (if not specified redirected to latest) and keep the older versions of the API for some time period before removing them. This should be clearly mentioned in the documentation. On Fri, Oct 3, 2014 at 2:31 PM, Nirmal Fern

Re: Shall we plan for a 4.1.0-M2 developer preview?

+1 On Fri, Oct 3, 2014 at 1:59 PM, Shiroshica Kulatilake wrote: > Hi, > > Shouldn't we also enable the corresponding new rest endpoints in the CLI > > Created a JIRA : https://issues.apache.org/jira/browse/STRATOS-869 > > Thank you, > Shiro > > On Fri, Oct 3, 2014 at 1:26 PM, Nirmal Fernando >

Re: Shall we plan for a 4.1.0-M2 developer preview?

Hi, Shouldn't we also enable the corresponding new rest endpoints in the CLI Created a JIRA : https://issues.apache.org/jira/browse/STRATOS-869 Thank you, Shiro On Fri, Oct 3, 2014 at 1:26 PM, Nirmal Fernando wrote: > I think we should. > > On Fri, Oct 3, 2014 at 1:08 PM, Sajith Kariyawasam

Re: Shall we plan for a 4.1.0-M2 developer preview?

I think we should. On Fri, Oct 3, 2014 at 1:08 PM, Sajith Kariyawasam wrote: > Do we focus on fixing following issues for M2 ? > > STRATOS-862 Kubernetes > scheduler needs to be restarted every 15 min or so. > STRATOS-860

Re: Shall we plan for a 4.1.0-M2 developer preview?

Do we focus on fixing following issues for M2 ? STRATOS-862 Kubernetes scheduler needs to be restarted every 15 min or so. STRATOS-860 Error when publishing to health topic in CEP extensions

Re: Shall we plan for a 4.1.0-M2 developer preview?

Hi Nirmal, Yes, CEP 3.1.0. Sorry for the typo. On Wed, Oct 1, 2014 at 10:56 PM, Nirmal Fernando wrote: > You meant CEP 3.1.0 ? > > On Wed, Oct 1, 2014 at 9:56 PM, Manula Chathurika Thantriwatte < > manu...@wso2.com> wrote: > >> Hi, >> >> Shall we integrate CEP 3.0.0 for M2. I can work on that.

Re: Shall we plan for a 4.1.0-M2 developer preview?

You meant CEP 3.1.0 ? On Wed, Oct 1, 2014 at 9:56 PM, Manula Chathurika Thantriwatte < manu...@wso2.com> wrote: > Hi, > > Shall we integrate CEP 3.0.0 for M2. I can work on that. > > On Wed, Oct 1, 2014 at 11:19 AM, Shiroshica Kulatilake > wrote: > >> +1 for the REST API clean up >> >> Also, we

Re: Shall we plan for a 4.1.0-M2 developer preview?

Hi, Shall we integrate CEP 3.0.0 for M2. I can work on that. On Wed, Oct 1, 2014 at 11:19 AM, Shiroshica Kulatilake wrote: > +1 for the REST API clean up > > Also, we should go for the first cut of the revamped UI > > On Wed, Oct 1, 2014 at 9:49 AM, Lakmal Warusawithana > wrote: > >> >> >> On

Re: Shall we plan for a 4.1.0-M2 developer preview?

+1 for the REST API clean up Also, we should go for the first cut of the revamped UI On Wed, Oct 1, 2014 at 9:49 AM, Lakmal Warusawithana wrote: > > > On Wed, Oct 1, 2014 at 9:43 AM, Akila Ravihansa Perera > wrote: > >> Shall we clean up our REST API to adhere to RESTful design as well? >> >>

Re: Shall we plan for a 4.1.0-M2 developer preview?

On Wed, Oct 1, 2014 at 9:43 AM, Akila Ravihansa Perera wrote: > Shall we clean up our REST API to adhere to RESTful design as well? > > +1 > On Wed, Oct 1, 2014 at 9:34 AM, Nirmal Fernando > wrote: > > Hi All, > > > > Since M1 developer preview is at its final testing stages, I think it's > be

Re: Shall we plan for a 4.1.0-M2 developer preview?

Hi Akila, Yes, we can add that too. IMO we should first deprecate the existing APIs and introduce new ones instead of wiping old ones. I can work on this. Thanks for bringing it up. On Wed, Oct 1, 2014 at 9:43 AM, Akila Ravihansa Perera wrote: > Shall we clean up our REST API to adhere to RESTf

Re: Shall we plan for a 4.1.0-M2 developer preview?

Shall we clean up our REST API to adhere to RESTful design as well? On Wed, Oct 1, 2014 at 9:34 AM, Nirmal Fernando wrote: > Hi All, > > Since M1 developer preview is at its final testing stages, I think it's best > time to plan for M2 (early next week?). I think we should focus on Python > Cartr

Shall we plan for a 4.1.0-M2 developer preview?

Hi All, Since M1 developer preview is at its final testing stages, I think it's best time to plan for M2 (early next week?). I think we should focus on Python Cartridge Agent Integration in M2. Anything else ? -- Best Regards, Nirmal Nirmal Fernando. PPMC Member & Committer of Apache Stratos, S