PlumbingFreeze

Differences between revisions 4 and 5
Revision 4 as of 2011-05-06 15:06:12
Size: 717
Editor: business-89-133-214-82
Comment:
Revision 5 as of 2011-05-08 10:36:19
Size: 889
Editor: business-89-133-214-82
Comment:
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
  * python toolchain
  * java infrastructure
  * multiarch support
  * Graphic subsystems (X, GTK/Gnome 3)
  * interpretive language toolchain infrastructure - ie. python, java, perl, etc.
  * features that span multiple architectures
Line 12: Line 12:
  * Features that other teams have dependencies on before feature freeze.
Basically
we need to identify projects that other teams depend on landing, so they can test their features, before we go into feature freeze. 

DRAFT - this is WORK IN PROGRESS

After this point the packages which are considered "plumbing" used for building the release should not change without significant regression testing and written signoff from release team and management.

Components that are to be classified as "plumbing" are TBD.

Candidates to consider are:

  • Graphic subsystems (X, GTK/Gnome 3)
  • interpretive language toolchain infrastructure - ie. python, java, perl, etc.
  • features that span multiple architectures
  • Features that impact the boot

Basically we need to identify projects that other teams depend on landing, so they can test their features, before we go into feature freeze.

Process needs to be defined still, as does infrastructure to do the testing and what the tests should be (which is obviously dependent on the packages considered to be "plumbing")

PlumbingFreeze (last edited 2011-05-08 10:45:16 by business-89-133-214-82)