Launchpad itself

Launchpad organization of a project with modules

Asked by Gabriel Petrovay

Hi,

I want to create a project on Launchpad and I am not sure how to organize it (using multiple Launchpad projects, series, milestones, branches, etc.)

The project has a core component (say CC) and several other components that depend on CC (say DC). The all DC's require CC. DC are optional for CC. How to organize such a project on Launchpad?

1. Should I create on single project for all and let trunk be CC and create series for each DC? (DC only rely on CC, but don't have code from CC inside)

2. Should I create one Launchpad project for each component (CC and DC)? DC components must be somehow linked to versions of the CC because if CC changes it's API, DCs can become obsolete and not compile anymore.

3. Should all components (CC and DC) be branches in a single project?

Any other ideas? (Just ask me questions if I am too abstract)

Thanks!

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Gary Poster (gary) said : 		#1

Hello. It sounds to me like you want to make individual projects for each of your components, and then request a project group to link all of them together. You can read about project groups here: https://help.launchpad.net/ProjectGroups . It also explains there how to request the project group that you want.

Best,

Gary

Can you help with this problem?

Provide an answer of your own, or ask Gabriel Petrovay for more information if necessary.

To post a message you must log in.