What are the strategies for managing updates for multiple subfiles and multiple releases?
We have a product with several extensions that come with it, each with a different version number. (Specifically, we have a xulrunner app with multiple extensions). The extension manager for xulrunner provides update functionality so that it will call the function anytime the version number of this extension has increased. This gives us the ability to do any necessary cleanup with update.
However, it has become very difficult to find a good way to keep track of which extensions require an increase in version number and which ones have remained largely unchanged. The best process we can imagine is 1) adding an upfront job when closing tickets (each individual ticket can have a series of flags indicating which extensions need to be modified)
2) writing queries that look for which tickets have changes in an extension since the latest version for a specific client, and 3) Updating extension version numbers throughout the product.
This all seems tedious both during development and during release - and error prone. Any suggestions?
a source to share
It looks like you are leaning towards using your work tickets to spot changes to your extensions. I wonder if you need to look at it the other way around and use your version control system to determine where the changes were made.
The version history should give you all the information you need about what has changed depending on the changes made and released. He will also provide a certain amount of audit that corresponds to the expected volume of changes, which corresponds to the volume of changes made.
Based on this information, you can implement your version change decisions.
a source to share