DeveloperDocumentation

Differences between revisions 65 and 66
⇤ ← Revision 65 as of 2013-02-05 15:22:44 →
Size: 7090
Editor: h-4-41
Comment:
← Revision 66 as of 2013-02-05 15:50:13 → ⇥
Size: 8729
Editor: h-4-41
Comment:
Deletions are marked like this. Additions are marked like this.
Line 21: Line 21:
Line 26: Line 25:
||<bgcolor="#FFC799">Week||<bgcolor="#FFC799">'''Development Planning'''|| ||<bgcolor="#FFC799">Week||<bgcolor="#FFC799">'''Development Planning''' Week 1-5||
Line 29: Line 28:
||4||<bgcolor="#DED4C1">Register blueprints at [[https://blueprints.launchpad.net/ubuntu]] using this [[https://wiki.ubuntu.com/UbuntuStudio/Blueprints/DevelopmentReleaseTemplate|template for blueprints]], and use the results from the previous brainstorming discussions to create workitems for these blueprints, and possibly create new custom blueprints. (see [[UbuntuStudio/Blueprints]] to get an overview of existing blueprints) ||
||5||<bgcolor="#DED4C1">All blueprints for the development release need to be registered and then approved by someone at the Ubuntu Release Team before [[FeatureDefinitionFreeze|Feature Definition Freeze]]||		 ||3||<bgcolor="#DED4C1">Register blueprints at [[https://blueprints.launchpad.net/ubuntu]] using this [[https://wiki.ubuntu.com/UbuntuStudio/Blueprints/DevelopmentReleaseTemplate|template for blueprints]], and use the results from the previous brainstorming discussions to create workitems for these blueprints, and possibly create new custom blueprints. (see [[UbuntuStudio/Blueprints]] to get an overview of existing blueprints) ||
||4||<bgcolor="#DED4C1">||
||5||<bgcolor="#DED4C1">FeatureDefinitionFreeze - All blueprints for the development release need to have been registered and then approved by someone at the Ubuntu Release Team||
||<bgcolor="#FFC799">Week||<bgcolor="#FFC799">'''Development''' Week 6-22||
||6||<bgcolor="#DED4C1">Begin development and testing. Report bugs as far upstream as possible. Work with appplication developers and Debian maintainers, especially the Debian Multimedia Team to solve bugs for multimedia debian packages.||
||7||<bgcolor="#DED4C1">||
||8||<bgcolor="#DED4C1">||
||9||<bgcolor="#DED4C1">||
||10||<bgcolor="#DED4C1">||
||11||<bgcolor="#DED4C1">||
||12||<bgcolor="#DED4C1">||
||13||<bgcolor="#DED4C1">||
||14||<bgcolor="#DED4C1">||
||15||<bgcolor="#DED4C1">||
||16||<bgcolor="#DED4C1">||
||17||<bgcolor="#DED4C1">DebianImportFreeze occurs here, which means any bugfixes will need special treatment. Possibly by adding patches to the Ubuntu package||
||18||<bgcolor="#DED4C1">||
||19||<bgcolor="#DED4C1">||
||20||<bgcolor="#DED4C1">FeatureFreeze means no new uploads of existing packages, unless it is a critical bugfix||
||21||<bgcolor="#DED4C1">||
||22||<bgcolor="#DED4C1">FinalBetaFreeze - No more changes until the final Beta is released.||
||<bgcolor="#FFC799">Week||<bgcolor="#FFC799">'''Beta Testing''' Week 23-26||
||23||<bgcolor="#DED4C1">FinalBetaRelease - Do thorough testing with this ISO and make sure any critical bugs get fixed.||
||24||<bgcolor="#DED4C1">||
||25||<bgcolor="#DED4C1">KernelFreeze - no more changes to the kernel||
||26||<bgcolor="#DED4C1">FinalFreeze, ReleaseCandidate||
||<bgcolor="#FFC799">Week||<bgcolor="#FFC799">'''Final Release''' Week 27||
||27||<bgcolor="#DED4C1">In preparation for the FinalRelease, prepare [[UbuntuStudio/PublicRelations|PR]] announcements||

Whiteboard

  • Add vocabulary list (words like upstream, SRU, etc)
  • public relations - list of places to make announcements, hashtags

  • Ubuntu membership and benefits - https://wiki.ubuntu.com/Membership

  • Generate gnupg key - needed for things like a launchpad account https://help.ubuntu.com/community/GnuPrivacyGuardHowto (good info on developer.ubuntu.com)

  • Create page(s) about the relationship between Debian / Ubuntu / Ubuntu Studio packages. With hints on what to do, and when to do it when wanting to change a package.

use, standard announcement verbiage, and links to various resources like banners/other graphics

The purpose of Ubuntu Studio:

1.

Provide a desktop base suitable for multimedia production work

2.

Provide system performance needed for multimedia applications

3.

Include relevant and up to date applications that cover all multimedia workflows

4.

Provide documentation for users that covers every aspect of linux multimedia

5.

Provide various tools (application/documentation) to make system management easy for non-hackers

6.

Report/adress bugs/issues/ideas upstream to Ubuntu -> Debian -> Software Developers to improve applications and packages

Ubuntu Studio Development Release Schedule

https://wiki.ubuntu.com/UbuntuDevelopment/ReleaseProcess - The Ubuntu Release Process

Week

Development Planning Week 1-5

1

Declare brainstorming for next relase open on ubuntu-studio-devel mail list

2

A leading team member attends Ubuntu Developer Summit

3

Register blueprints at https://blueprints.launchpad.net/ubuntu using this template for blueprints, and use the results from the previous brainstorming discussions to create workitems for these blueprints, and possibly create new custom blueprints. (see UbuntuStudio/Blueprints to get an overview of existing blueprints)

4

5

FeatureDefinitionFreeze - All blueprints for the development release need to have been registered and then approved by someone at the Ubuntu Release Team

Week

Development Week 6-22

6

Begin development and testing. Report bugs as far upstream as possible. Work with appplication developers and Debian maintainers, especially the Debian Multimedia Team to solve bugs for multimedia debian packages.

7

8

9

10

11

12

13

14

15

16

17

DebianImportFreeze occurs here, which means any bugfixes will need special treatment. Possibly by adding patches to the Ubuntu package

18

19

20

FeatureFreeze means no new uploads of existing packages, unless it is a critical bugfix

21

22

FinalBetaFreeze - No more changes until the final Beta is released.

Week

Beta Testing Week 23-26

23

FinalBetaRelease - Do thorough testing with this ISO and make sure any critical bugs get fixed.

24

25

KernelFreeze - no more changes to the kernel

26

FinalFreeze, ReleaseCandidate

Week

Final Release Week 27

27

In preparation for the FinalRelease, prepare PR announcements

Setup Developer Environment

UbuntuStudio/SetupDeveloperEnvironment

Ubuntu Studio Developer Tasks

  • Create Blueprints for each new release, which contain work items that can be assigned to a developer.

  • Testing and bug management

  • Maintain documentation

  • Update the web site.

  • Keep the list of default Ubuntu Studio applications up to date, and relevant - Seed Management

  • Design application categories and documentation to follow a workflow based format, so that users who want to do a specific task are easily led to relevant applications.

  • Test and tweak the system to find out how performance can be improved for various workflows.
  • Look at revamping ubuntustudio-controls to let the user more easily manage the system, without having to edit files manually, or using the terminal to pass commands (realtime privilege, adjusting rtirq - restarting, etc..)
  • Investigate the possibility of creating an application that helps the user more easily find tools for workflow specific tasks. Possibly a custom panel.

Information Channels

These are all the channels and methods used for communication within the Ubuntu Studio development community.

IRC at irc.freenode.net

  • #ubuntustudio-devel
  • #ubuntustudio (user channel)

IRC chatting is the quickest and most common communication method used in Ubuntu Studio development.

* IRC HowTo - for those not familiar with IRC

Mail lists

Team Structure

By keeping a clear team structure it is easy to keep track of who is doing what, and whom to ask about specific topics.

Developer Reference

UbuntuStudio at Launchpad

Teams

Projects

Documentation Resources

UbuntuStudio/DeveloperDocumentation (last edited 2015-08-21 09:45:06 by 83)