Hello,

how is Deimos supposed to address different versions of a library?
In the case at hand, I have a Deimos repository for LLVM 3.1. Now I want
to add support for version 3.2. Should I create a different branch or
just a tag?

BTW I updated my documentation for creating Deimos repositories. http://jkm.github.com/d-programming-language.org/deimos.html

Jens

On Mon, 25 Mar 2013 13:50:37 +0100
Jens Mueller <jens.k.mueller@gmx.de> wrote:

> Hello,
> 
> how is Deimos supposed to address different versions of a library? In the case at hand, I have a Deimos repository for LLVM 3.1. Now I want to add support for version 3.2. Should I create a different branch or just a tag?
> 
> BTW I updated my documentation for creating Deimos repositories. http://jkm.github.com/d-programming-language.org/deimos.html
> 
> Jens

I've been meaning to bring up that question, too. It would make sense that each version of the target library would have its own branch in its Deimos repo, because that way you can update it if any problems are discovered. Tags would be a bad idea because of that. But the problem is, there doesn't seem to be a way to do a "pull branch" request.

Nick Sabalausky wrote:
> On Mon, 25 Mar 2013 13:50:37 +0100
> Jens Mueller <jens.k.mueller@gmx.de> wrote:
> 
> > Hello,
> > 
> > how is Deimos supposed to address different versions of a library? In the case at hand, I have a Deimos repository for LLVM 3.1. Now I want to add support for version 3.2. Should I create a different branch or just a tag?
> > 
> > BTW I updated my documentation for creating Deimos repositories. http://jkm.github.com/d-programming-language.org/deimos.html
> > 
> > Jens
> 
> I've been meaning to bring up that question, too. It would make sense that each version of the target library would have its own branch in its Deimos repo, because that way you can update it if any problems are discovered. Tags would be a bad idea because of that. But the problem is, there doesn't seem to be a way to do a "pull branch" request.

Having different branches for each version seems like the right choice. What would be the role of the master branch then? The latest version?

Jens

On 2013-03-25 13:59, Nick Sabalausky wrote:

> I've been meaning to bring up that question, too. It would make sense
> that each version of the target library would have its own branch in
> its Deimos repo, because that way you can update it if any problems are
> discovered. Tags would be a bad idea because of that. But the problem
> is, there doesn't seem to be a way to do a "pull branch" request.

I would say add a tag for each version. Keep the a couple of the latest versions as a branch, or for as long as a version is in use.

-- 
/Jacob Carlborg

On 2013-03-25 13:59, Nick Sabalausky wrote:

> But the problem is, there doesn't seem to be a way to do a "pull branch" request.

It doesn't make a different from which branch the new branch originated?

-- 
/Jacob Carlborg

Jacob Carlborg wrote:
> On 2013-03-25 13:59, Nick Sabalausky wrote:
> 
> >I've been meaning to bring up that question, too. It would make sense that each version of the target library would have its own branch in its Deimos repo, because that way you can update it if any problems are discovered. Tags would be a bad idea because of that. But the problem is, there doesn't seem to be a way to do a "pull branch" request.
> 
> I would say add a tag for each version. Keep the a couple of the latest versions as a branch, or for as long as a version is in use.

You mean basically using both tags and branches. Because tags are easy to use to access a specific version. Can these be used across branches?

Jens

On 2013-03-25 15:01, Jens Mueller wrote:

> You mean basically using both tags and branches. Because tags are easy
> to use to access a specific version. Can these be used across branches?

Branches are only useful if you want to keep updating the code for a given version. If that's not the case, I think tags are better.

-- 
/Jacob Carlborg

On Mon, 25 Mar 2013 14:25:01 +0100
Jacob Carlborg <doob@me.com> wrote:

> On 2013-03-25 13:59, Nick Sabalausky wrote:
> 
> > But the problem is, there doesn't seem to be a way to do a "pull branch" request.
> 
> It doesn't make a different from which branch the new branch originated?
> 

Unless things have changed since the last time I tried, GitHub has no way to setup your pull request to mean "Please pull this new branch XXXX *as* a new branch." No matter what the source branch is, GitHub only lets you request it to be pulled into a branch that *already* exists in the destination repo.

Always seemed like a goofy limitation to me.

On 2013-03-25 17:56, Nick Sabalausky wrote:

> Unless things have changed since the last time I tried, GitHub has no
> way to setup your pull request to mean "Please pull this new branch
> XXXX *as* a new branch." No matter what the source branch is, GitHub
> only lets you request it to be pulled into a branch that *already*
> exists in the destination repo.
>
> Always seemed like a goofy limitation to me.


Aha, I didn't understood you talked about new branches.

-- 
/Jacob Carlborg

Jacob Carlborg wrote:
> On 2013-03-25 15:01, Jens Mueller wrote:
> 
> >You mean basically using both tags and branches. Because tags are easy to use to access a specific version. Can these be used across branches?
> 
> Branches are only useful if you want to keep updating the code for a given version. If that's not the case, I think tags are better.

>From my experience you don't always get right. So I think having the
branches is recommended. But we should use the tags for the version since one can update them.

Jens