Namecoin Git Branching Model

Post by **phelix** » Tue May 13, 2014 12:34 pm

http://nvie.com/posts/a-successful-git-branching-model/

Simplified from the above I suggest we use these branches:

namecoinq: development = cutting edge
namecoinq-rc: release candidates used for testing (versions tagged)
namecoinq-release: actual releases (versions tagged)

Why the release candidate branch? Especially on windows it is difficult to build thus it is difficult to test new features without binaries. I hope that with release candidates we will get more people into testing new features and improvements.

domob · Post by **domob** » Tue May 13, 2014 5:14 pm

I support this model. While we are at it, I suggest that we sign git tags for releases via GPG. (I can also do this myself if everyone trusts me with that, or we could use a dedicated and well-published key for this.)

Post by **phelix** » Tue May 13, 2014 7:07 pm

domob wrote:I support this model. While we are at it, I suggest that we sign git tags for releases via GPG. (I can also do this myself if everyone trusts me with that, or we could use a dedicated and well-published key for this.)

Cool. Signing git tags? Your job.

I will see if I can do something for windows binaries.

domob · Post by **domob** » Wed May 14, 2014 5:42 am

phelix wrote:
domob wrote:I support this model. While we are at it, I suggest that we sign git tags for releases via GPG. (I can also do this myself if everyone trusts me with that, or we could use a dedicated and well-published key for this.)
Cool. Signing git tags? Your job. I will see if I can do something for windows binaries.

No problem. Just let me know (or we decide together as a community) when to actually tag a release & sign it in Git.

Namecoin Forum

Namecoin Git Branching Model

Namecoin Git Branching Model

Re: Namecoin Git Branching Model

Re: Namecoin Git Branching Model

Re: Namecoin Git Branching Model