Our API has a version number in it so when we make breaking changes we don't break all our clients and they can upgrade as time allows. Our bulk dumps (http://firefox-marketplace-api.readthedocs.org/en/latest/topics/export.html) on the other hand don't have any kind of versioning so any change that happens there would happen immediately. This bug is to investigate the best way to add versioning to these dumps and then implement it. Since it's running off the same APIs, I assume this isn't too difficult, and then we just add the version to the file path. Expiring after 30 days is still fine, I think, both for removing the older files and for generating version n-1. That means when we release a new version of the API, we'll have two sets of files for each date for the first 30 days, and then we'll stop generating n-1 files. Any concerns with that plan?
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.