[IPython-dev] (slightly OT) tags vs. branches
Wed Aug 17 01:36:58 CDT 2011
On Wed, Aug 17, 2011 at 12:33 AM, David Warde-Farley
> On 2011-08-17, at 12:26 AM, Aaron Meurer wrote:
>> I think you'll find that with GitHub, a highly distributed system
>> works very well, because people can just submit pull requests to each
>> other (that's right, to each other, not just to the official repo),
>> and merge the work together very easily.
> I haven't really played with it much, but is there actually a way to direct a pull request somewhere other than the repo you forked from? I didn't see any obvious way to do it in the UI, but it makes sense conceptually.
Yes, although everyone should fork from the official repo, as pull
requests go there by default.
When you are in the pull request form, click on "change commits" at
the top, or click on the black branch name.
>> Going back to the original question, though, I do highly recommend
>> tagging the exact commit you do a release with, as this is a pretty
>> standard practice. The rest will vary from project to project.
> Yep. I just wondered if there was a reason for also having a "frozen in time" *branch* version, as there appeared to be in IPython. It seems the answer is no.
No, tags are frozen in time, and branches are not, so if you want
something that's frozen, you should definitely use a tag.
More information about the IPython-dev