This page is used by the TOPP developers to track information that is pertinent to upcoming deployments.
 

You may be looking for these: openplans release notes

 

Deployment Process

Above: diagram showing weekly deployment schedule

•  1 week before scheduled deployment:

• cut release branches for relevant components and deploy to stage as version 0.3.x
• ­write a trac ticket filed under milestone: QA for testing those changes
  
• During the week before deployment
• File and fix any bugs that come up during QA.  Fixes go directly to release branches.
  
• New features go into trunk for the next release
  
• On deployment day
  
• Deploy release branches to live site
• Cut new release branches for 0.3.x+1
• Rinse & repeat

NOTE:  There will be some times when we need to deploy outside of this weekly schedule, so be ready.  Embrace change.

 

Verification after deployments

After deploying to the live site, openplans.org, verify the following:

• live site is actually running
• topp.openplans.org  is running
• wwwroot for openplans is accessible

Javascript and CSS Changes

When a change is made to either the javascript or css files, the query string to load the file should be changed. You can simply add a ?r=0.3.7 to the end of it, or modify this version if it already exists. The browser will fetch the file again, even though the filename hasn't changed.

Searches in "everything" don't always find profiles: opencore 0.9.7.6

The fix for http://trac.openplans.org/openplans/ticket/1689  needs a catalog reindex after zope restarts:

• Go into the ZMI
• go to http://../openplans/portal_catalog/manage_catalogAdvanced
• click the "Update Catalog" button. This might take a while.
  

 

Update Tasktracker: v0.9.7.6

Update source to trunk.

GenericSetup for configuration management: v0.9.7.7

We're now using GenericSetup to create our site and apply configuration, instead of the purely procedural approach that we've been using in our Install.py.  This doesn't change too much, yet; most of the setup widgets are still available in the portal_migrations tool, and will work as before.  A few of the widgets, however, are now gone.  Anything related to portal properties, workflow, portal types, portal actions, or the indexes in the catalogs (both portal_catalog and membrane_tool) are now handled entirely by the GenericSetup profile (in the opencore/configuration/profiles/default directory).  Instead of running a setup widget, you would reimport the settings from the profile using the portal_setup tool.

I (Rob Miller) would like to be involved in this process the first few times we use it, to make sure that things go smoothly, so I'm not going to provided detailed instructions here.  We can coordinate on this together when the time comes to start using this.  Background info on the functioning of GenericSetup can be found in this tutorial, especially chapter 3.

TaskTracker and WordPress configuration changes: v0.9.7.7

TaskTracker and WordPress used to have their URIs defined by values coming out of both zope.conf and ZCML.  Both of these are now gone; the configuration for these now lives in the opencore_properties property sheet.  For this to function on the site, these new properties need to be installed and populated.  You can load the properties from the profile by running the properties tool import step.  You can either put the correct values into the profile before you do the import, or you can import them as empty and then put the correct values in using the ZMI.

 

Wordpress Role Changes: v0.9.7.7

Opencore team members will now be mapped to Author's.  The wordpress database needs to be updated with the following script:

https://svn.openplans.org/svn/build/topp.build.wordpress/trunk/topp/build/wordpress/skel/change-role-migration.py

To run the script do: %python change-role-migration.py contributor author 

mysql-python has to be installed in the working environment.


 

Fixup Project Homepages widget: v0.9.7.7

Our use of Plone's getDefaultPage and setDefaultPage mechanism was intefering with our custom project home page stuff.   New projects should be fine, but there are existing projects that still have the default page set, the "Fix up project home pages" NUI setup widget should fix this.

 

Project home page urls: v0.9.7.7

Home page urls are relative now. A setup widget needs to run to migrate the old absolute home page urls to the relative ones (relative to project url).

Setup widget: Make project home pages relative

 

Email address blacklist: v0.9.7.7

Opencore and Sputnik versions in setup.py: v0.9.7.7

python setup.py develop needs to run on opencore/sputnik. There are entry points that represent version numbers that hook in when this is run.

 

topp.featurelets and topp.utils updated: 0.9.7.7

New deploys and running setup.py develop should bring in these new versions.

topp.featurelets should be 0.2.2

topp.utils should be 0.2.10