a colleague is considering to use fossil in a setup where he (the group
leader) supervises several students having dedicated tasks within a larger
project. what he would like to do is
* set up master repo
* give student(s) clone/pull/push permisisons for the repo
* require student(s) to branch immediately to individual "feature"
branches (not fossil private branches, or anything, but just an ordinary
branch assigned to the person and his task)
* request students to perform all work on their individual branches, while
allowing them to merge in changes from trunk.
* supervisor looks at results/milestones of students in turn and merges
the branches into trunk as he sees fit.
the "request to work on branch" is the catch: he wants to ensure that
students can never mess up trunk, i.e. must technically not be able to
merge anything into trunk. in the end he asks for branch-specific user
capabilities. my understanding is that this is not possible in fossil. if
so, are there any recommendations how a simple and easily manageable
workflow having this functionality (prevent trunk from getting spoiled)
could look like?
or are there better workflows/alternatives which would serve such a
hierarchical development model? it should be a frequent requirement...
thx/j
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
