On September 30, 2010, Curtis Hovey wrote: > > > > > > > > > > > > Code Branches > > > ............. > > > > > > > > > > > > Branches for private projects and distros (source packages) are > > > private, they cannot be public. Any user with access to the private > > > project or distro can access the branch. The project primary context > > > owner can subscribe a user or restricted team to the branch. Public > > > projects can still have private branches to solve security > > > vulnerabilities or for commercial development. > > > > > > > > This also seems overly restrictive. We have to think about a very common > > use cases where a team works on a project privately and then release it > > to the public. Is the way to model that by switching the privacy of the > > primary context? But this means that you cannot do a graded disclosure > > (when one releases a branch, then all the bugs and branches). > > It is not our intent to support this--the primary context is private, > making the branch public will not give anyone access to it. The branch > will have to be pushed to a public location.
Thanks for the clarifications Curtis. Remember thought that the primary context of a branch is not a project, but the (person, project) tuple. But that's probably not a big deal. -- Francis J. Lacoste [email protected]
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
