Issue tracking and central repository

10 views
Skip to first unread message

Uneron

unread,
Nov 18, 2012, 12:10:41 AM11/18/12
to endgame-sin...@googlegroups.com
Things just start running again and I am already loosing track of who does what. Also, the level of forks seems to be quite excessive for the number of developers (so far everyone seems to be using his own, me included), which is going to cause great merging pains, later on. I see no reason why bugfixes and various improvements (like those styles) shouldn't go directly in the main branch.

Case in point, we need to work more centralized. A single repository for the issue-tracking and most of the commits, and various branches/forks only for the more debatable or experiemental changes.

Personally I would prefer the github repo, because of the social advantages (more likely to get attention) and also because of the nice interface.
https://github.com/singularity/singularity

But if you prefer we can stick with the ugly, old googlecode one.
http://code.google.com/p/endgame-singularity

Cheers
Uneron

P.S.: Could someone do something, that all my posts in the dev mailing list don't need reviewing? Pretty, please?
Reply all
Reply to author
Forward
0 new messages