Apologize if someone consider this marketing, but I find it relevant for
this thread: on Thursday November 21st Atlassian is organizing a
webinar about git branching for agile teams: http://ow.ly/qtXEp
Looks interesting; I hope to have time to attend it.
On 03/11/13 08:22, Sergio Fernández wrote:
Hi,
On 31/10/13 23:31, Peter Ansell wrote:
On 31 Oct 2013 09:36, "Sergio Fernández"wrote:
(...) we are considering only releases as stable code. And I think
we should do that more often.
GitFlow is a well known and accepted distributed VCS strategy [1].
Rather than changing that strategy, potential developers who want to
work with the codebase should be learning it (and the other main Git
workflows [2]) as a Git exercise. They are likely to need to use it or
similar workflows on other open source projects in the future.
So, it I understood correctly, according GitFlow we are doing right
considering stable code (so merging to master) only releases, is that
correct?
If we all agree, that's fine for me. We'd just need to update the
documentation. And, of course, be aware all team of such workflow. After
all, we are learning in the trip :-)
Thanks Peter for the clarification.
Cheers,
--
Sergio Fernández
Senior Researcher
Knowledge and Media Technologies
Salzburg Research Forschungsgesellschaft mbH
Jakob-Haringer-Straße 5/3 | 5020 Salzburg, Austria
T: +43 662 2288 318 | M: +43 660 2747 925
sergio.fernan...@salzburgresearch.at
http://www.salzburgresearch.at
