META: Contribution Clarification Request

[Guest]

Recently I have been going through contributions looking at what has been done and at what I may want to add. There seems to be a breakdown that makes it a bit harder for those of us looking (and even contributing) and I would like to suggest something that may make life a bit easier for all of us.

 

Contributions ae built on snapshots, and as people upgrade their OSC from a snapshot it becomes harder to "upgrade" your OSC as the version you are running has many changes implemented within it. That means that contributions written for a version well after what you're running may be relying on changes to the CVS that you don't have.

 

Last year there was a somewhat major change in the product when OSC modified the checkout process. So we have two major 2.2 versions that people may be running. 2.2-oldcheckout and 2.2-newcheckout. Then we also have MS1.

 

Now if I go to the GV contribution the version I will want to pull will depend very much on which of these three versions of OSC I have operational (and patched with other contributions).

 

My suggestion/request is that when you create a contribution that is not tied to any one version (say the User Tracking contribution) you preface it [2.2-all] and if the contribution is destined to the new checkout, MS1, or the old checkout that it also be prefaced [2.2-oldco] [2.2-newco] [2.2-ms1]. And please, if you had a version that was running on [2.2-oldco] and you modified it to [2.2-ms1] please make that crystal clear in the contribution section.

 

[credit class and gift voucher comes to mind as one very good example of this confusion - V3.2 is the last one could use with the original checkout, 4.0 is the new checkout and 4.2 is MS1 -now if I was to integrate Linda's free shipping into 3.2 (which was done in 4.1) and wanted to re-release it so others would be able to do what Ian did in 4.2, but with the old shopping cart - um, well, it would lay on top of Ian's 4.2, but as what? 3.2.1? ]

 

Anyway, enough of the meta thoughts... back to looking for the piece I need (a way to integrate the associates program to the GV program so that associates can join and earn credits to spend at the store rather than cash payouts).