Thoughts about versioning changeSets.
- Useful when a change has to be applied to multiple forks.
- Allows for a kind of mix and match.
However, having many versioned change sets that do not have a constant name like a package would be similar to giving every package version a new name. This would be rather difficult to view and navigate. So, I think support for change set must also include ways of associating additional categories/keys to the change sets so they can be more easily managed. Additionally, rules need to be devised that allows the repository garbage collector to know when a change set can be collected. I think a practical way to use the change sets would result in any particular version to have a limited useful life, thus allowing them to be collected and keeping their numbers low.
I think this could be done if change sets are periodically merged/integrated back into the applicable forks and are then marked as obsolete.