Am 30.01.2011 06:30 schrieb Michael Pedersen:
> tg-dev is for 2.1 and up. These repositories have a lot of history
> since they were broken out of SVN, and they were broken out of SVN at
> different points. As a result, we can't really combine them. We're
> going to have to have them separately hosted on sf.net. The question
> becomes what's the best choice for organization?
It seems the 2.1 repositories have the full history, but the 2.0
repository has not. It was created 2009-03-19 as a release branch in its
own repository that has no further history and has see only 50 revisions
since the.
I suggest to merge this 2.0 branch back in the main 2.1 repository. To
do that, pull the 50 changesets of the 2.0 repository (e.g. as bundle),
and merge the first pulled in changeset with whatever appears to be the
closest revision in the main repository (786 or so).
We really should not have separate repositories for the different
versions. We have 3 repositories for core, dev and docs already anyway.
Let's use this opportunity to get things clean and use proper branching
and tagging from now on, as explained here:
http://nvie.com/posts/a-successful-git-branching-model/
Btw, which tool do you use to convert from hg to git?
Generally, we should try to keep our infrastructure as simple and clean
as possible.
Btw, we also need to decide where to host our packages. On the old
server, we had http://files.turbogears.org and
http://pypi.turbogears.org, and they were maintained independently. We
should find a replacement for these and consolidate them.
Concerning subprojects, it should suffice to set up a TG1 and TG2
subproject unless one project can't have more than one repository.
-- Christoph
--
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/turbogears-trunk?hl=en.
