Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Updated version and codename, obviously I am liable to forget to do t…
…his for a release... no more, no more!
- Loading branch information
d637d57
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about tagging releases as well, rather than just have everything on 'master'?
d637d57
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See http://github.com/kohana/kohana - that is where tagged releases are. The core is just for core development.
d637d57
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently pulling directly from here though, since http://github.com/kohana/kohana includes files I don't want to pull (basically just want modules and system). Not really sure how to pull/fetch version 3.0.6 (or future releases, e.g. 3.0.7, 3.0.8 etc) without those files since core and the various modules aren't tagged.
d637d57
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, I generally agree with that - one for the BDFL as I have no control over this tree
d637d57
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can use
git submodule
on a clone of kohana/kohana to find out the revision of each submodule that was tagged. It seems like a waste of time to tag every module, but maybe it would be useful in the long run.