-
-
Notifications
You must be signed in to change notification settings - Fork 933
could there be an 0.3.2 (or 0.3.2-RC2 ;-)) release? #164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
reply would be very appreciated -- I want to decide on how to update debian python-git package -- just pick up patches or (ideally) update to current state (thus official release or candidate would help) |
Does it make sense to use # Get latest version in 0.3
pip install git+https://github.com/gitpython-developers/[email protected] Another form of this command can pull a particular commit - more information about this type of |
@Byron For good or for worse, my Debian-rotten soul has limited experience with pip since I am preferring installation/maintenance in implementation-agnostic way (apt-get ;-) ) and offload integration testing upon tests/users on a particular system (e.g. Debian) -- hence was my question, because releases help to identify/compare different versions of the same software, which would be tricky if deployment is always happening from a moving target without clear versioning. AFAIK such pip install should work but upgrades will not fetch new state from the 0.3 (I could be proven wrong!). |
A new release has been made. |
I see that there is some roadmap for 0.3.2 release (with 10 issues to tackle), but in the light of recent fixes (e.g. I care about untracked_files fix) I hoped that there might be some bugfix release along the way?
Thank you in advance!
The text was updated successfully, but these errors were encountered: