no - PostgreSQL wiki

frightenedfroggeryData Management

Dec 16, 2012 (4 years and 8 months ago)

154 views

Dave Page
2
nd
April 2008
How the PostgreSQL Project Works
PostgreSQL
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
2
Elephants
are not like
Dolphins
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
3

BSD licenced:

Anyone can use the code as they please

No one copyright holder

No one can take over the project
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
4

Project workforce:

Hobbyists

End users

Corporate contributors
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
5
Project Organisation
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
6

The big boss:
Slonik
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
7

Slonik‟s “other” life:
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
8

The Core Team:

Josh Berkus

Peter Eisentraut

Marc Fournier

Tom Lane

Bruce Momjian

Dave Page

Jan Wieck
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
9

Core are responsible for:

Scheduling, planning & release management.

Security contact point

Project liaison/contact for confidential issues.

Discipline

Decision making (when the community at large
cannot reach consensus)
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
10

Other distinct groups:

Developers

Advocacy group

Funds group

Web team

Infrastructure team

Translators
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
11
The release cycle
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
12

First things first:
Branch the code
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
13

Code development:

“Scratching itches”

hobbyists

Fulfilling a need

end users

Yes boss, right away boss!
-
corporates
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
14

Patch lifecycle:

Discussion

Problem identification

Design development
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
15

Patch lifecycle:

Coding

don‟t forget the docs!

Patch submission to the queue

Patch review & feedback

Lather, rinse, repeat until ready
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
16
Feature freeze…
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
17
… doesn‟t scale


Patches „bitrot‟ in the queue

Developers wait months for feedback

Months spent reviewing patches:

Difficult work, even for the experienced

It‟s a long and boring job
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
18
The solution:
Commit fests
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
19

Every two months:

Review
all
patches in the queue:

Commit to CVS,

Return to author with feedback

Reject outright

Accept
no
new patches until the fest is complete.

Committers focus entirely on clearing the patch
queue
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
20

Final stages of the cycle:

Feature freeze/final commit fest:

No new features accepted

Concentrate on applying all patches

Translators start work

Advocacy/press machine gets underway
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
21

Beta releases:

Build and release „beta‟ versions

Q/A is a joint effort:

User testing

Benchmarking

Regression testing

not just for the buildfarm!
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
22

Release candidates:

We think it‟s ready!

Any last bugs? Anyone? Bueller? Bueller?
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
23

Release day:

Press releases

Website & mailing list announcements

Web team watching for the Slashdot Effect
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
24

Take a deep breath:

Fix any early bugs reported

Take a long, hot bath

Start again!
2nd April 2008
Dave Page, EnterpriseDB UK
Slide
25
Questions?
Thank you.