launchpad help|
⇤ ← Revision 1 as of 2010-10-13 21:15:34
Size: 2315
Comment: Created seed for use of private branches.
|
Size: 2341
Comment: s/Restricted/Restricted or Moderated
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 18: | Line 18: |
| Before you can set up private branches for your project, you must have a team that will be given access to the branches; membership in this team will govern who has access to the project's code. Make sure this team is set to Restricted membership. In the rest of this page, we'll refer to this team as the project's devel team. | Before you can set up private branches for your project, you must have a team that will be given access to the branches; membership in this team will govern who has access to the project's code. Make sure this team is set to Restricted or Moderated membership. In the rest of this page, we'll refer to this team as the project's devel team. |
| Line 30: | Line 30: |
| To set up other teams through the devel team, just create a new team as you created the devel team. In particular, remember to set the team to Restricted Membership. Then add the new team as a member to the devel team. The new team and its members should now have access to the private branches for the project. | To set up other teams through the devel team, just create a new team as you created the devel team. In particular, remember to set the team to Restricted or Moderated Membership. Then add the new team as a member to the devel team. The new team and its members should now have access to the private branches for the project. |
Launchpad Help > Code > Private branches
Private branches
Launchpad Supports private code branches. A project's branches can have a set visibility of public, private, or private only.
- Public branches can be seen by anyone.
- Private branches can only be seen by those on the teams associated with the project's branches' visibility. They can be made Public.
- Private only branches are like Private branches, but can never be made public.
Private branches are a feature for commercial projects. For more information, see CommercialHosting.
Setting up private branches for a project
Create a development team
Before you can set up private branches for your project, you must have a team that will be given access to the branches; membership in this team will govern who has access to the project's code. Make sure this team is set to Restricted or Moderated membership. In the rest of this page, we'll refer to this team as the project's devel team.
Once you have created the devel team, you will need to get someone from Canonical's Launchpad team to set up private branches for the devel team. Send an email to commercial@launchpad.net asking to have private branches set up for your devel team and project.
Once you are told private branches have been set up for your team and project, you can create a development focus branch (and other branches) for your project as usual for teams.
Private branches and teams
Any team that wants access to the code for a project once private branches are set up must have access created set up for it. Since it is cumbersome to have to contact Launchpad for each team, the devel team can function as a master team for each team needing access.
Setting up additional teams with the devel as a master team
To set up other teams through the devel team, just create a new team as you created the devel team. In particular, remember to set the team to Restricted or Moderated Membership. Then add the new team as a member to the devel team. The new team and its members should now have access to the private branches for the project.
