Dear Franz, I am in the process of updating the documentation in regard to the used SCM system. For many places a textual replacement (and changing the URL) has been enough. For some other places there will be a policy/process change. I would like to have input for the below wiki pages.
a.) http://www.saros-project.org/ReleaseProcess The process of branching/merging/cherry-picking changes with Git/Gerrit, the naming/placing of branches changes as well. On top of that we had some issues in the last release cycle. E.g we some issues with testing the wrong version of the plugin and I am not sure if the documentation has been updated. >From what I see is that we should make a new release (or at least test the process) and update the documentation. What do you think about a dry run for the release? b.) http://www.saros-project.org/Guidelines I think some of the information needs to be changed, for some other parts we don't have the experience to provide a "best practices". 1.) Branches Branches are local, I don't think it makes sense to allow/forbid a specific branch. Developers can easily create a new repository in their personal sourceforge.net area, on github/bitbucket/gitorious. I am not sure with what to replace this information, e.g. I don't think there is be a point in explaining how to create a repository at github (this is already described by github). 2.) Refactor->Rename We don't have much experience with refactorings in Git and merging. In general both the EGit/JGit and the external "git mergetool" are quite good in handling renames+modifications. In general git is a lot better in merging than svn. The question is how much better and how painful it still is. Again, I am not sure with that to replace the information. I am tempted to remove the paragraph for now and wait for some experience. ideas/comments? holger ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dpp-devel mailing list Dpp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
