Hi All,
What I feel is the linear versioning scheme (i.e. v 1.0, v 1.1, v1.2) is an
artificial thing. Real app(Web, mobile, site, desktop, IoT, etc) versioning
is something more than that. That has N dimensions.
Lets consider mobile app case for example, however applies to all
application types IMHO.
1. New artifacts are added based on added functionality, bug fixes, etc.
This is the dimension we currently talking about.
2. Same "App", different binaries are available for different platforms. In
case of Mobile{IoS, Android, Winmo, etc), In case of Sites (Desktop,
Mobile, etc) . This is 2nd Dimension.
3. Application promotion. Dev, QA(n), Staging(n), and Production (here
there can be many stages n), and only subset of users/devices see apps in
each stage
4. Roll out strategy. How see the update on an application, when a new
application is added to production. need to be able to define sets of users
based on different criteria (e.g. roles, random N segments). This is
important as we should be conservative in updating a mobile app. Damage can
be controlled, if something goes wrong due to undiscovered bug in new
artefact. This also applies to Webapp, where we allow gradual transition to
new Webapp over some time.
5. There may be other dimensions based on organization need.
So, I would suggest we look at the versioning in non traditional way on
AppM, based on user stories. AppM versioning need to be aligned mote to
"Application Management" rather than traditional version control IMHO.
What I feel is, we need to support extensible way to
1. Add new Dimension(s) (when customizations are necessary)
2. Add a Filter for each dimension. So when a user arrives on store, Each
filter selects allowable apps based on its selection criteria. Then Display
the intersection of all filtered dimension. ( also user should be able to
optionally look up all apps, why it was filtered out)
3. Add a Handler/Filter(s) to do Application Update(on remote device) for
each dimension.
WDYT?
Cheers,
Ruwan
On Fri, Feb 26, 2016 at 12:03 AM, Chathura Dilan <[email protected]> wrote:
> Hi Lahiru,
>
> Can we have a meeting for this. Since mobile apps are in binary files we
> do not need to show multiple versions on the store and it make it more
> complex scenario for users.
>
> It is developer's task to support backward compatibility of the mobile app
> as much as possible. Otherwise he will end up in maintaining multiple
> binary files for each versions.
>
> But in terms of mobile apps there should be a way to publish the new
> version for beta testing and staged roll out. See this video[1]. We could
> support this in App Manager.
>
> We can also support uploading multiple binaries under the same version for
> each hardware configurations[2]. But for that we need to extract
> information[3] from the binary files.
>
> How about having a meeting tomorrow 11.A.M (SL time). Please let me know.
>
> [1] - https://www.youtube.com/watch?v=4IeaPoL7qoo
> [2] -
> http://developer.android.com/google/play/publishing/multiple-apks.html
> [3] - http://developer.android.com/google/play/filters.html
>
>
>
> On Wed, Feb 24, 2016 at 8:47 PM, Lahiru Cooray <[email protected]> wrote:
>
>> Hi,
>>
>> We have implemented multiple versions support to WebApps and Sites in
>> AppM.
>> Here, we allow users to create multiple versions of a WebApp/Site and
>> select a particular version as the default.
>> So users can access the default version of the app with the default URL
>> (eg: host_name/context) and also the previously subscribed non default
>> versions by mentioning the particular version in the URL (eg:
>> host_name/context/version).
>> In the Store we have a deployment level configuration to select either to
>> display all versions of an App or to display only the default version.
>>
>> But as per my understanding the same functionality is not applicable for
>> Mobile Apps. Currently in Mobile Apps we can create multiple versions but
>> the latest version is always considered as the active/default (no option to
>> swap default version). Do we need to change this behaviour in Mobile Apps?
>> If so, what would be the most appropriate functionality? Highly appreciate
>> your suggestions.
>>
>>
>>
>> --
>> *Lahiru Cooray*
>> Software Engineer
>> WSO2, Inc.;http://wso2.com/
>> lean.enterprise.middleware
>>
>> Mobile: +94 715 654154
>>
>
>
>
> --
> Regards,
>
> Chatura Dilan Perera
> *Senior Software Engineer** - WSO2 Inc.*
> www.dilan.me
>
--
*Ruwan Abeykoon*
*Architect,*
*WSO2, Inc. http://wso2.com <http://wso2.com/> *
*lean.enterprise.middleware.*
email: [email protected]
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
