Release Management

Release Procedure

The following steps must be followed when releasing a new version of the Drupal site code. If needed, the site can be made unavailable during this procedure via the admin maintenance setting in Drupal. Also, major releases may require a database backup to precede this procedure.

  1. Merge all the changes going into the release (see the source control procedure).
  2. Copy the web site subversion repository trunk directory to a release tag (e.g. tags/release_3.16).
  3. ssh into the webadmin@freestateproject.org account.
  4. Export the release into /var/www:
    cd /var/www
    svn export $FSVN/tags/release_3.16
    mv release_3.16 www-r3.16
  5. Set the database password for the new release in www-r3.16/sites/www.freestateproject.org/settings.php, using the current password in the same location in the www-r3.15 folder.
  6. Move the site link over to the new release (it would be pointing at www-r3.15 when we start):
    rm www.freestateproject.org; ln -s ./www-r3.16 ./www.freestateproject.org
  7. Test by reloading the front page. If a problem occurs, switch back to the previous version by:
    rm www.freestateproject.org; ln -s ./www-r3.15 ./www.freestateproject.org
  8. The previous version should not be erased immediately, but kept around as a fall-back position. Older releases (e.g. 3.14 and older in our example), can be deleted at this point.

Release Notes

Release notes for code releases. The release numbers correspond to release_X.Y tags in the source repository.

 


R3.0: Drupal 5.2

This release adds the following functionality:

  1. Drupal 5.2 upgrade.
  2. User read only module, a login button, and the profile edit page set up so users can only edit fields they really should.
  3. Project Issue Extend module allowing user groups to be added to the assignee list for issues.
  4. Customization of base path filter module to keep working with 5.2
  5. Updating custom fsp module to keep working with 5.2

Note that several modules had to be removed, due to the fact that their functionality had been merged into the Drupal core or other modules, or that no 5.x compatible versions of the modules could be found. It is not expected that the absence of these will influence functionality.

  1. browscap: 5.x version is broken.
  2. civicrm: Skipped upgrade because of large investment in time, and it is not being used right now
  3. flexinode: Obsolete, and not being used.
  4. image_pub: No R5 version
  5. page: Appears to be obsolete
  6. statistics_filter: No R5 version
  7. story: Merged into page
  8. taxonomy_xml: No R5 version
  9. urlfilter: Merged into core
Defects fixed:
  1. Oversized admin submenu text reduced in size.
  2. Form checkboxes and radiobuttons arranged vertically instead of horizontally.

R3.0.1: User mail defect fix

Defect fix: : user_mail changed to drupal_mail, for emails going out after approval

R3.0.2: TinyMCE upgrade

Defect fix: TinyMCE upgrade to try and fix non-appearence after 3.0 roll-out

R3.0.3: TinyMCE fix

Defect fix: Added flash to page template, which fixed TinyMCE, as well as blank access control page

R3.0.4: user_readonly fix

Defect fix: Exception in user_readonly module

R3.0.5: Links fixed on registration page

Fixed the following:

- Missing membership kit PDF on registration page

- Incorrect references to JSPs on old site (changed to equivalent content in new site)


Release 3.1: Stats update

The stats calculations were updated:

  1. New queries by Jon put into module
  2. All stats now correctly calculated (weekly / monthly averages were stubs)
  3. Calculated hourly: Participants, Moved to NH, New last week
  4. Calculated daily: By state; By country; By moving plans; Last month; Last six months

Release 3.2: Moved to NH update; E-commerce module

The following changes were rolled out:

  1. The already in NH count will now be updated with every profile update
  2. These modules were rolled out to support the store: ecommerce; token; ec_live_subproducts

Release 3.3: Security updates

Security updates for:

(1) SA-2007-025

(2) SA-2007-024


Release 3.4.1: Membership graph finalization

Fixed configuration for membership graphs - runs without problems now.

Release 3.4: Drupal 5.3; Membership graphs; Analytics

These features were released:

  1. Upgraded CMS platform to latest production release (Drupal 5.3).
  2. Membership graph generation.
  3. Google analytics.
  4. Moved custom FSP theme to /sites folder (from /themes), and cleaned up theme files stored in /images or /misc

Release 3.5

These items were released:

  1. Layout fixes for the new content sidebar.
  2. Automatic generation of the (bi)monthly membership report used by membership admins.
  3. Inclusion of Google Apps identification html file

Release 3.6: Drupal upgrade; Design fixes

The following items are contained in this release:

  1. An upgrade of Drupal to 5.5, in order to plug security holes
  2. Fixes to the site look-and-feel:
    1. Changed content tabs (e.g. edit, etc.) to plain, removing broken rounded edges.
    2. Fixed format of book contents to look like regular links instead of on dark background
    3. Added space around images embedded in node content
    4. Fixed the font size for admin menu submenu items. Font size used to increase with submenu level, now stays the same

Release 3.7: Move Triggers added to registration

Move triggers have been added to the registration page, per the requirements approved by the board. Note the following:

  1. The triggers are presented on the same page as the rest of the registration information.
  2. The trigger-related fields are grouped together, with the existing SOI acceptance flag, into a separate profile group.
  3. This profile group is accessible in a separate tab on the user account page, and is read-only to non-admin users.
  4. The values of the trigger fields are reported via the monthly membership report.

 


Release 3.8: Triggers to member report

The registration trigger fields were added to the member report.

Release 3.9: Changes to support "Latest Blog Entries block on front page"

The following was changed:

1) CCK module added (for "News Item" content type)

2) Panels module added (for two-column content)

3) Views module added (for blocks containing news & blog items)

4) Style changes to support news & blog views on front page


Release 3.10: Fix panel layout for new front page

Style fixes to fix problem with panel layout on new front page: Sometimes right column was rendered next to left, at different horizontal window sizes it was rendered below.

Release 3.11: Style fixes for new menu; Modules to support rich profiles

The menu styles were fixed to lay out the new sidebar menu in a sane way.

The following modules were installed, to support rich profiles:

  1. nodefamily
  2. nodeprofile
  3. views_fusion
  4. usernode
  5. subform_element
  6. pageroute

Release 3.14: UI fixes; Email cleanup

The following changes were made:

  1. Template changes causing html validation failure was fixed.
  2. Some fixes for pages not found.
  3. Registration alert email now sent to registrationadmin@freestateproject.org, instead of to all members of role.
  4. HTML corrector module added to get rid of broken HTML in imported blog items

Release 3.15: Drupal 5.7; Modules cleanup; Modules upgrade

The following were changed:

  1. Drupal was updated to 5.7
  2. All active modules were upgraded to their latest versions
  3. Modules no longer used were removed

Release 3.16: Modules for Roadmap support

Numerous modules were released to support the Roadmap. The authenticated role was moved out to the settings file, in order that the role may be changed without changing code.


Release 3.19: Google Analytics module upgrade; Made front page blog title font smaller

The following changes were made:

  1. Google analytics module upgraded: To fix problem with changed Google operations.
  2. Front page font for blog titles made smaller