Re:Now this is how you pitch your product to an open source ...
by jedberg on Sunday May 02, 2010 @07:44PM
(#1313525)
> Well, part of the git workflow is branches.
Internally we use a lot of branches and tagging and versioning, etc. The problem is if we published everything live, it would add a lot of overhead for us.
While we do eventually publish everything, we are still a for profit company, and occasionally have to keep things secret for business reasons (like new features). Keeping track of what code is for a new features vs a fix to an old one would add a lot of overhead that we just have the time for.
In the name of reduced overhead, we only publish to the public repository once we have released a feature and it is fully baked.
Internally we use a lot of branches and tagging and versioning, etc. The problem is if we published everything live, it would add a lot of overhead for us.
While we do eventually publish everything, we are still a for profit company, and occasionally have to keep things secret for business reasons (like new features). Keeping track of what code is for a new features vs a fix to an old one would add a lot of overhead that we just have the time for.
In the name of reduced overhead, we only publish to the public repository once we have released a feature and it is fully baked.