Madhava Rao Jalagam (MadhavaRaoJ)
Amerprise Financial
Software Engineer
Amerprise Financial
MadhavaRaoJ Member since 2013 3 posts
Amerprise Financial
Posted: July 19, 2016
Last activity: July 20, 2016
Posted: 19 Jul 2016 14:00 EDT
Last activity: 20 Jul 2016 9:40 EDT

Major version skimming

We are planning to implement major version skimming and currently we have different rule sets like Implementation, Framework, Integration & organizational etc. We are looking to break down these into different tasks at the rule set level and targeting for different releases.


Questions :

  1. After skimming whether it goes at each rule set level or at the entire application level to have same major version. Example skimming applied only to framework rule set CaseFramework: 01-01-xx - 01-80-xx to 02-01-01 and rest others rule sets will be still in minor version like Ameriprise: 01-75-xx, AmpInt: 01-64-xx and Enterprise: 01-65-xx. Is this suggestible or  works ?
  2. What should be skimming strategy in applying to high environments. I mean whether it should be moved as a product or same exercise of skimming should be applied in higher environments and after delete the minor version rule sets.


Please share your thoughts




***Updated by Moderator: Lochan. Removed user added Ask the Expert tag. Apologies for confusion, shouldn't have been an end-user option***

System Administration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.