Forums : Technical Issue Help
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
Enlistment policy : branches or trunk ?
It might be an already asked question, but I'm still unsure...
I have an 'Artichow' project with a trunk and two branches
- trunk: svn://www.artichow.org/artichow/trunk
- branch 1: svn://www.artichow.org/artichow/branches/1_0 artichow
- branch 2: svn://www.artichow.org/artichow/branches/2_0 artichow
I submit an trunk enlistment, but I'm not sure changes to version 1 an 2 (branches) will be taken into account.
Any help would be much appreciated!
From what I can see there [http://www.ohloh.net/projects/6431/analyses/latest], I'm almost pretty sure I have to had branches respos, since I know the projet is active and lastest public releases were out on April 2007.
Would you please confirm ?
Hi mytto,
We don't have a good answer for you. Ohloh only supports one branch, and the best choice is usually the trunk. If you submit more than one branch, we'll end up with invalid metrics.
Does that answer your question? Let me know if it doesn't.
Thanks for using Ohloh,
Andy
Hey Andy
That indeed answer my question, even if I expected another ;)
Why is that so tough to handle branches properly ? Isn't that possible to links corresponding file revisions, to not take them into account twice ?
The problem lies in getting Ohloh's metrics to distinguish between files duplicated because they are in the more than one branch, and files that are duplicated because they are in the distribution twice.
If you add the trunk and two branches, it assumes that your project releases contain all three versions of the code, so some the metrics are gonna be around 3 times higher than they should be (the LOC graph paticularly).
It is such a shame that this behaviour causes so many problems with repo rearrangement.
