[Development] Branches and time based releases

Thiago Macieira thiago.macieira at intel.com
Tue Feb 25 20:12:57 CET 2014


Em ter 25 fev 2014, às 13:13:14, Matthew Woehlke escreveu:
> To add an outsider perspective here... it's bad enough Qt doesn't follow
> the conventions (a) used by (nearly) every other git repository in
> existence and (b) unambiguously recommended by git itself.

Are you referring to patches to the mailing list? Or maybe the use of pull 
requests in GitHub? Maybe it's the direct push access that 1700 repositories 
at projects.kde.org have...

Also, I don't know of any project that has a CI-controlled integration.

We are different, period.

> If I had such a project, I would much prefer to rename a branch (which
> is after all a technically very low cost operation) than violate
> convention, habit and muscle memory by doing something non-standard from
> the start.

I should also point out that the master branch in Git's Git repository is 
*not* the development version. What you check out when you clone it is the 
last tag. If you want the development version, you check out "next".

The Linux kernel uses one repository per branch. If you clone "linux-stable", 
you get the stable branch (called "master"). If you clone "torvalds", you get 
the development branch and it's also called "master".

My point is that there is no single recommended way.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center




More information about the Development mailing list