Difference between revisions of "Development Team"

From Sugar Labs
Jump to: navigation, search
(Platform Release Cycles)
Line 50: Line 50:
 
== Platform Release Cycles ==
 
== Platform Release Cycles ==
  
'''Sugar platform release''' version cycle: | [[0.82]] | [[0.84]] | [[0.86]] | [[0.88]] | '''[[0.90]]''' | [[0.92]]
+
{{Template:Platform Cycle Linkbar}}
  
 
[[Template:Current Stable Release]] holds the release number.
 
[[Template:Current Stable Release]] holds the release number.
Line 57: Line 57:
  
 
[[Development Team/Release]]
 
[[Development Team/Release]]
 +
 
== Subpages ==
 
== Subpages ==
 
{{Special:PrefixIndex/Development Team/}}
 
{{Special:PrefixIndex/Development Team/}}

Revision as of 02:25, 8 December 2011

Team Home   ·   Join   ·   Contacts   ·   Resources   ·   FAQ   ·   Roadmap   ·   To Do   ·   Meetings

Mission

The mission of the Development Team is to build and maintain the core Sugar environment. This includes specifying and implementing new features in conjunction with the Design Team, fixing bugs as they are found by the Testing team and the Sugar community, and generally making Sugar awesome in all ways.


Meetings

The development team has a regular IRC meeting (See the Sugar Labs calendar). Find out more about the meeting time and upcoming and earlier meetings here. Help: Using IRC

Team lead

The Development Team coordinator position carries administrative tasks such as organizing regular meetings, keeping the TODO list updated, keeping the membership list updated, and making sure that the team has clear goals and is kept focused. We are currently accepting nominations for an election for this position, see Development_Team/Team_Lead_Candidates_2010_05.

Releases

See the Development Team/Release page.

Release manager

We have defined the role of the release manager for the past 3 releases as the following:

  • Setting the schedule.
  • Making sure that the Features/Policy is followed by submitters.
  • Keeping this wiki updated with the released modules and making sure to have final release notes available.
  • Sending email reminders about approaching Freezes, tarball due dates, etc.

Schedule

The schedule is based on GNOME releases, a 6-month release cycle.

Development systems

All of core Sugar development except system-dependent modifications can be done on a standard computer by compiling jhbuild and editing with your favorite editor (eclipse/pydev, emacs, vim, etc.). Activity (aka application) development can be done in many environments using pre-compiled packages ("sucrose") or images ("starch").

Document your work

See Features/Feature Template for an example.

Code review

Patches to Sugar are more than welcome. There are guidelines for code review to get them accepted.

Package Sucrose for your distribution

  • Currently there are efforts to maintain Sugar as part of Debian, Ubuntu, and Fedora.
  • Help us maintain good communication with distribution packagers to assist in this. Start a Packaging Team.

Kill Bugs!

Project Ideas

  • Want to work on an interesting Sugar project, or have an idea of your own? Check the project ideas page.
  • Prepare a new Sugar Feature.
  • See the Summer of Code project; ideas, students, mentors, and organization help are welcomed.

Platform Release Cycles

Sugar platform release version cycle: | 0.82 | 0.84 | 0.86 | 0.88 | 0.90 | 0.92 | 0.94 | 0.96 | 0.98 | 0.100 | 0.102 | 0.104 | 0.106 | 0.108 | 0.110 | 0.112 |

Template:Current Stable Release holds the release number.

See 0.112/Notes for the release notes.

Development Team/Release

Subpages