Infrastructure Upgrade

We are going to upgrade the development framework the main site runs on from SourceCast (SC 2.6) to CollabNet Enterprise Edition (CEE 3.5.1, 19.4).

Timeline

• Branding Freeze on Production Site: 4/14/06
• Tests Stage Site: 5/30/06 – 6/16/06
• Date Range for Production Deployment: 6/20/06 – 6/23/06

Release Notes

Please review the full version of the CollabNet Enterprise Edition versions 3.0.0, 3.1.0, 3.5.0, and 3.5.1 release notes prior to your upgrade: http://www.collab.net/rn/.

Staging Test

There are 2 weeks reserved for a test of CEE 3.5.1 on a staging server with our data set.

We are responsible to

• not change site branding after the branding freeze date.
• verify that branding appears as it should on the stage site.
• test all custom functionality, as well as any specialized build processes, or any other processes.
• investigate our favorite areas in addition to testing our host performs.
• ensure as far as localization is concerned that CEE 3.5.1 is the same as 2.6.x or better.

We will file one ticket per issue against the stage site for any questions regarding access or functionality on the stage site. The component is "www" and subcomponent "openoffice.org upgrade".

The stage site is named stage.openoffice.org.

You will be able to access the site with the same username and password you use on our production site.

Preparations

It is a good idea to make a list of features and functionality that we are interested in testing during our test weeks.

If you plan on testing features which send email, such as mailing lists, CVS or SVN commits which trigger email, etc., please note that all email addresses have been changed. Before testing these features, make sure that you edit your user profile and change your email address back to one at which you can receive email.

The stage site was created with data taken from our running production site weeks ago. Any content added to your production site after it has been created will not be reflected on our stage site.

Branding

• How can we remove project headers?

Due to the changes in staticization project home pages look different. All project home pages (like http://api.stage.openoffice.org) start with a project header. In SC26 this was only the case for dynamic pages like http://udk.openoffice.org but not for static pages like http://api.openoffice.org). http://api.stage.openoffice.org/index.html does not contain the header. But the project list (http://www.stage.openoffice.org/servlets/ProjectList?type=Projects&mode=TopLevel) points to the short form and more important every user will use the short form.

• Project specific navigation bar entries are lost (e.g. http://api.openoffice.org)

Webcontent

• Staticization (not yet in place)

Caching Tutorial for Web Authors and Webmasters

HTTP 1.1 RFC: Caching in HTTP

User/role/permission/registration (ST)

• disable click through after registration

Boundary Systems

• EIS (BEI)
• Feature / Interface mails (BEI)
• iBIS (FMA)
• cvsup/anoncvs (MH)
• mailstats (ST)
• broken links (ST)

Production Upgrade

The Production Upgrade is planned for the week beginning June 20th.