On 16 November 2012 13:25, Vadim Zeitlin <[email protected]> wrote:
> On Fri, 16 Nov 2012 12:57:23 +0000 Mateusz Loskot <[email protected]> wrote:
>
> ML> I'm thinking about structuring SOCI development and following
> ML> some well-known GitHub practices regarding branching, tagging, etc.
> ML>
> ML> I've proposed some ideas as a task here:
> ML>
> ML> https://github.com/SOCI/soci/issues/18
> ML>
> ML> I'd like to ask everyone for comments,especially related to the model
> ML> outlined in the article linked in the ticket.
>
> Hello,
>
> This is not a bad model but I wonder if people are not going to be
> confused by the need to make patches to (or make pull requests for) the
> "development" branch instead of the usual "master".
I do have exactly the same concern.
I'm not used to the use of "develop" or "next" branch,
but I have seen projects using it (e.g. CMake, i3wm.org).
I simply integrate my private branches with master directly.
> As it seems that many
> (most?) changes to SOCI come from people not working on it all the time,
Yes.
My aim is to favor some sort of open development with anyone
encouraged to share her/his ideas, and step forward to take some action.
In an ideal world, I'd be happy to grant anyone with write access to Git repo,
anyone who would ask for that, but...
And here GitHub plays great as it enables folks to contribute easily.
It's just that there is someone needed for some kind of traffic control :)
We have the SOCI core team, if you will, and that's fantastic.
But, I don't expect SOCI members to be contribute on daily/weekly/any
frequent basis, so neither of us should feel obliged to be active.
(I do not work on SOCI all the time myself either.)
The point is, it's just great thing if we push the project forward from
time to time, taking tiny steps, even once a year :)
> I think that many of them might not suspect that they need to start from that
> branch instead of "master".
Yes, good point.
> So perhaps this model can be used but with "master" used for development
> and some branch with a different name ("stable"? "release"?) for the
> releases?
Yes, that would simplify the workflow too.
Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net
------------------------------------------------------------------------------
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
_______________________________________________
soci-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/soci-users
