Hi Dulitha, For your requirement, you can use what is provided OOTB. G-Reg has two types of versioning.
1. Revision numbers (as in the case of editing a wiki document) - see http://docs.wso2.org/wiki/display/Governance460/Managing+Metadata 2. Asset versions - see http://docs.wso2.org/wiki/display/Governance460/Managing+Services#ManagingServices-ServiceVersioning The concept of revision is a part of the code, and users can enable this feature if required (see http://docs.wso2.org/wiki/display/Governance460/Configuration+for+Static+%28One-time%29+and+Auto+Versioning+Resources). The asset versions are specific to an asset type and is based on conventions. For example, services do have versions but an asset modelling an organization does not. HTH. Thanks, Senaka. On Wed, Jul 31, 2013 at 1:08 PM, Chan <[email protected]> wrote: > Hi all, > I would like to know what is the best way to handle version management > inside of greg. Our usecase is this - We have an application and we store > that application instance in greg. The developer updates the application - > we are going to store the changes in the greg. > > One way of doing this is to increase the version number when ever the > updating the instance. This allows us to keep a complete copy of previous > instances. But if the application have about 30 updates - there will be 30 > instances in greg. This approach is fairly good since most of the time > there won't be much of updates. For example if a new application version > comes out there might only be a change on the recent changes. But there > might be a case where everything apart from title, category might changes > -(eg:- new icon, new screenshots, new banner, new description etc). > > Other way for it is to store the changes in a single instance as fields - > for example as history. This approach won't have redundancy issues as the > above approach. But the overhead of complication implementation is there. > After 30 updates - we'll have a one fat instance (with history). > > WDYT? > > -- > Chan (Dulitha Wijewantha) > Software Engineer - Mobile Development > WSO2Mobile > Lean.Enterprise.Mobileware > * ~Email [email protected]* > * ~Mobile +94712112165* > * ~Website dulithawijewantha.com > * > * ~Blog blog.dulithawijewantha.com<http://dulichan.github.io/chan/> > * > * ~Twitter @dulitharw <https://twitter.com/dulitharw>* > -- * <http://us13.wso2con.com/> * * * *Senaka Fernando* Senior Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
