I thought this was the default behavior since it's already working like this in API- M so +1 to make the version change transparent to users. When you say next release, you mean 1.1.0 ? or 1.0.0.
Isabelle. ------------------------------------------------------------------------------------- *Isabelle Mauny* VP, Product Management - WSO2, Inc. - http://wso2.com/ On Mon, May 4, 2015 at 5:35 PM, Sumedha Rubasinghe <[email protected]> wrote: > > > On Mon, May 4, 2015 at 8:30 PM, Dinusha Senanayaka <[email protected]> > wrote: > >> Hi, >> >> We thought of doing some changes to current versioning support in App >> Manager. Current model is similar to "Create new version" functionality in >> API Manager. All versions are appeared on store (unless previous version is >> deprecated) and each app is having separate gateway endpoint with version. >> This result in having different urls for each versioned app. Not like the >> APIs, Apps are end user base and url should be constant while there is only >> latest version off app appeared on the store. >> >> So we thought of adding following changes to current model, >> >> *Current model:* >> *Publisher* >> - All versions are appeared on publisher >> - Can edit all versions except retired/depecated apps >> >> *Store* >> - All versions are appeared on store >> - Users can subscribe to any version >> >> *Gateway * >> - Each versioned app is having different url >> eg: http://localhost/app1/v1 >> http://localhost/app1/v2 >> >> >> *New model:* >> *Publisher* >> - All versions are appeared on publisher >> - Can edit only latest version >> >> *Store* >> - Only latest version is available >> >> *Gateway* >> - GW url is constructed without appending version to url >> eg: http://localhost/app1 >> >> >> *Implementation changes:* >> When new version added to an app: >> > > It should be when a new version of an app is published (not added). > > >> - Make it as the default version >> - Retire all previous versions >> - Move all existing subscriptions to new version (seamless to enduser) >> >> With new model new version creations are not visible to end user, he will >> always use the new version seamlessly. >> >> Appreciate any feedback. >> >> Regards, >> Dinusha. >> >> >> -- >> Dinusha Dilrukshi >> Associate Technical Lead >> WSO2 Inc.: http://wso2.com/ >> Mobile: +94725255071 >> Blog: http://dinushasblog.blogspot.com/ >> > > > > -- > /sumedha > m: +94 773017743 > b : bit.ly/sumedha >
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
