I've started pushing content to
http://www.getgitorious.com/documentation now (the new official doc is
very much a work in progress but we're gonna keep pushing content to it
over the coming weeks and months).
The new branching model is present under
My one suggestion is to make this policy crystal clear to new
developers. Whenever I write a patch for a project I want to know
what branch do I base this on in order to get it accepted ASAP? If
you make it very clear in the HACKING file, and in the wiki, that
patches should be proposed
On it. I'm starting to migrate doc/content to
http://www.getgitorious.com/documentation later this week, will move it
there.
cheers,
Thomas
On Tue, Oct 16, 2012 at 9:41 AM, Christian Johansen
christ...@cjohansen.nowrote:
My one suggestion is to make this policy crystal clear to new
Dear list,
Since the Gitorious project started, the master branch has been where most
development has been happening; and at the same time we have tried to keep
the master branch stable enough to be used for deployment in a production
environment.
In early 2011, we started creating stable releases
On Mon, Oct 15, 2012 at 5:35 AM, Marius Mårnes Mathiesen
marius.mathie...@gmail.com wrote:
What do you think?
Sounds straightforward to me. Thanks for outlining this.
My one suggestion is to make this policy crystal clear to new
developers. Whenever I write a patch for a project I want to know
On Mon, Oct 15, 2012 at 5:50 PM, Ken Dreyer ktdre...@ktdreyer.com wrote:
On Mon, Oct 15, 2012 at 5:35 AM, Marius Mårnes Mathiesen
marius.mathie...@gmail.com wrote:
What do you think?
Sounds straightforward to me. Thanks for outlining this.
My one suggestion is to make this policy crystal
