[scribus-dev] Sort out the svn repository branches

[Oleksandr Moskalenko]

I'm converting out svn repository to git to create a mirror repository and a git<->svn gateway that can be used to allow easier commit access to more contributors via gitolite access control. However, I'm not certain about the status of some of the svn branches and hope that people involved in their creation could help sort them out. I need to know which ones need to be deleted, which ones converted into tags, and which ones should be left as feature branches. 

For reference, I'm thinking of applying several major principles from the http://nvie.com/posts/a-successful-git-branching-model/ model to the git repository, though I am not sure we need to delete the release branches right away as they are pretty long-lived in our developmental model. Perhaps, applying this model can lead to shorter developmental cycles between releases and much easier merging of contributions outside of the small core team.

Thanks,

Alex.

  remotes/Scribus - ???
  remotes/ScribusOIF - ???
  remotes/ScribusOIF at 15499 - ???
  remotes/ScribusOIF at 454 - ???
  remotes/ScribusOIF at 8494 - ???
  remotes/ScribusOIF at 9671 - ???
  remotes/ScribusOTF - ???
  remotes/ScribusOTF at 12278 - ???
  remotes/ScribusOTF at 454 - ???
  remotes/ScribusOTF at 8494 - ???
  remotes/ScribusOTF at 9671 - ???
  remotes/ScribusUIDStyles - ???
  remotes/ScribusUIDStyles at 12284 - ???
  remotes/ScribusUIDStyles at 454 - ???
  remotes/ScribusUIDStyles at 8494 - ???
  remotes/ScribusUIDStyles at 9671 - ???
  remotes/Version14x - current release branch?
  remotes/Version15x -  alias to trunk?
  remotes/scribus - ???
  remotes/start - ???
  remotes/subik - separate repo needed?
  remotes/trunk - the main devel branch

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.scribus.net/pipermail/scribus-dev/attachments/20120506/8db1009d/attachment.html>