ManagingBlueprints

Differences between revisions 9 and 10
Revision 9 as of 2013-09-09 09:12:36
Size: 749
Editor: zequence
Comment:
Revision 10 as of 2013-11-03 16:12:06
Size: 2883
Editor: zequence
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
 * One blueprint for each binary package (including meta packages)
 * One blueprint for each non-package project (docs, artwork, PR, etc)
<<TableOfContents>>
Line 7: Line 6:
Main projects:
 * Installer Image
 * Website
 * Documentation (user and developer)
= Registering a blueprint for a Ubuntu Studio project =
Line 12: Line 8:
-------- A blueprint could be for anything, but it always needs to be registered within a project of some sort.

Things to keep in mind before registering:
 * Register the blueprint within the project it is for. For example, blueprints for [[https://launchpad.net/linux-lowlatency|linux-lowlatency]] go [[https://blueprints.launchpad.net/linux-lowlatency|here]]
 * Is it going to be targeted for a specific release of [[https://launchpad.net/ubuntustudio|Ubuntu Studio]]? If yes, Add it as a dependency to the correct topic blueprint in the [[https://blueprints.launchpad.net/ubuntustudio|ubuntustudio launchpad project]]. See the [[UbuntuStudio/ManagingBlueprints#Dependency_structure_for_Ubuntu_Studio_topics|next section]] about the dependency structure for Ubuntu Studio topics.

= Dependency structure for Ubuntu Studio topics =

'''Example of a release targeted blueprints tree for Ubuntu Studio 14.04:''' https://blueprints.launchpad.net/ubuntustudio/+spec/topic-ubuntustudio-flavor-t

Structure for the [[https://blueprints.launchpad.net/ubuntustudio|ubuntustudio project blueprint]] topics

 * '''ubuntustudio-?''' (main topic)
  * '''core-?''' (subtopic)
  * '''applications-?''' (subtopic)
  * '''art-?''' (subtopic)
  * '''documentation-?''' (subtopic)
  * '''website-social-?''' (subtopic)

Each subtopic will have dependencies to blueprints from other Ubuntu Studio projects. Next is a table that shows the structure of those dependencies:

|| '''Subtopic name''' || '''Dependecy LP Projects''' ||
|| core-? || [[https://launchpad.net/linux-lowlatency|linux-lowlatency]], [[https://launchpad.net/linux-rt|linux-rt]], [[https://launchpad.net/ubuntustudio-meta|ubuntustudio-meta]], [[https://launchpad.net/ubuntustudio-default-settings|ubuntustudio-default-settings]], [[https://launchpad.net/ubuntustudio-live|ubuntustudio-live]] ||
|| applications-? || [[https://launchpad.net/ubuntustudio-controls|ubuntustudio-controls]], [[https://launchpad.net/ubuntustudio-menu|ubuntustudio-menu]], [[https://launchpad.net/ubuntustudio-installer|ubuntustudio-installer]] ||
|| art-? || [[https://launchpad.net/ubuntustudio-icon-theme|ubuntustudio-icon-theme]], [[https://launchpad.net/ubuntustudio-look|ubuntustudio-look]], [[https://launchpad.net/ubuntustudio-lightdm-theme|ubuntustudio-lightdm-theme]], [[https://launchpad.net/usplash-theme-ubuntustudio|usplash-theme-ubuntustudio]] ||
|| documentation-? || -- ||
|| website-social-? || [[https://launchpad.net/ubuntustudio-website|ubuntustudio-website]] ||
----
Line 15: Line 38:

 * Creating a topic (done by a Ubuntu Developer)
 * Creating blueprints (done by the Ubuntu Studio developer in charge of blueprints)
 * Creating workitems (done by any Ubuntu Studio developer)
 * Managing workitems (DONE, POSTPONED, etc)

Registering a blueprint for a Ubuntu Studio project

A blueprint could be for anything, but it always needs to be registered within a project of some sort.

Things to keep in mind before registering:

Dependency structure for Ubuntu Studio topics

Example of a release targeted blueprints tree for Ubuntu Studio 14.04: https://blueprints.launchpad.net/ubuntustudio/+spec/topic-ubuntustudio-flavor-t

Structure for the ubuntustudio project blueprint topics

  • ubuntustudio-? (main topic)

    • core-? (subtopic)

    • applications-? (subtopic)

    • art-? (subtopic)

    • documentation-? (subtopic)

    • website-social-? (subtopic)

Each subtopic will have dependencies to blueprints from other Ubuntu Studio projects. Next is a table that shows the structure of those dependencies:


Release Blueprints Template - used when planning for next release


CategoryUbuntuStudioPlanning CategoryUbuntuStudio

UbuntuStudio/ManagingBlueprints (last edited 2015-04-26 16:27:35 by zequence)