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". As it seems that many (most?) changes to SOCI come from people not working on it all the time, I think that many of them might not suspect that they need to start from that branch instead of "master". 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? What do you think? VZ
pgpaywCK7TUTQ.pgp
Description: PGP signature
------------------------------------------------------------------------------ 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
