How we maintain the makefiles

What

Only the modules, themes and libraries located in 'sites/all' are updated. Modules, themes and libraries located in an individual website's directory are not updated. This is to allow site maintainers to have their own version of a module if they need a specific version for things to work.

We like stable modules. If a module has a higher major version which is still in dev, alpha, beta or rc, we wait until a stable version is released before using it. On the other side, to follow their development, we maintain minor versions like dev, alpha, beta and rc if there is no stable release yet.

For example:

• We update from 7.x-2.0-alpha1 to 7.x-2.0-alpha2.
• We do not update from 7.x-1.0 to 7.x-2.0-alpha1.
• We update from 7.x-1.0 to 7.x-2.0.

We may still decide to do otherwise to correct an important bug or to use new features.

How

Koumbit maintains the makefiles in the Koumbit Platforms (kplatforms) project following this procedure:

1. Update your local git repository:
   • git pull
2. Verify the Koumbit Platforms (kplatforms) project issue queue to see if there is any modification to do for this release.
3. Verify all the sentinel websites and their 'Available updates' page.
4. Gather information and read the release notes.
5. For each supported Drupal version, verify and, if need be, update all inclusions in the makefiles:
   • Drupal
   • Pressflow
   • CiviCRM (updated by our CiviCRM team)
   • Localized Drupal Distribution (l10n_install)
   • Open Atrium
   • Open Outreach
   • OpenPublish
6. Here are examples if we need to patch Pressflow to get up to date to Drupal core:
   • #2174953: Patching Pressflow 7.24 with Drupal 7.26
   • #2175097: Patching Pressflow 6.29 with Drupal 6.30
7. Make sure the patch(es) to the cores still work and rebuild them if needed:
   • #1317338: Improvements to the core file robots.txt in Drupal
   • #2007316: Enforce not using core module statistics
8. For each branch, verify and update all modules, themes, libraries, profiles, features and patches that need updating in all the makefiles.
9. Update the script kplatforms.sh as necessary.
10. Update documentation as necessary:
    • Project homepage
    • Project documentation pages
    • 'README.txt' file
11. Send your changes to the central git repository:
    • git commit
    • git push
12. Tag a new release for this project (see Release naming conventions):
    • git tag 8.x-2.0
    • git push -u origin 8.x-2.0
13. Create a project release.
14. Build the Debian package using the Jenkins server:
    1. Build the job kplatforms-source.
    2. Build the job kplatforms-binaries.
    3. Migrate the package down into stable.