Closed Moliholy closed 8 years ago
Alright, there is several things to do here.
push -f
it (GitHub apparently didn't realise that this contains already merged changes)cvmfs/__init__.py
. I didn't find a way yet to DRY this up. Please change there as well. Or maybe you have a bright idea to reference it?ChangeLog
needs to be updated accordinglyHere is a proposal for the ChangeLog
. Feel free to add more things:
0.3.0:
0.2.0:
* Allow for multi-threaded catalog inspection
* Add an optional local disk cache for arbitirary repository objects
* Retrieve repository tags by 'name', 'revision number' or 'date'
* Inspect catalog tree of historic repository revisions
More general comment: Please avoid merging devel
into feature branches. Rather git rebase
the feature branch on the latest devel
. This way you keep a clean git history that simplifies cherry-picking if necessary.
I simply did a git pull origin devel, which internally merges both the current devel and feature branches. I take note for the next one, thanks! ;)
Offtopic, I've added the zip_safe=False option to setup.py. With this the library will be automatically decompressed when installed. This seems to be more portable and I've seen it recommended before. Do you think it's a good idea?
I'm fine with zip_safe
Version number and package name hardcoded. Ready to merge
Fasten your seat belts! Merge in 5, 4, 3, 2, 1 !!!
Now that we have the new revision it might be a good idea to release a tag, no? With the tag one could reference from pip which version should be installed, to avoid incompatibilities
... see eMail. I was about to point out the same... I agree.
Renamed to cvmfsutils Version number 0.3.0