plone.releaser 1.3

Plone release management utilities

Introduction

Tools to make managing Plone core releases easier.

Installation

To install plone.releaser add it to your buildout:

[release]
recipe = zc.recipe.egg
eggs =  plone.releaser

To make it available in buildout.coredev, run buildout with releaser.cfg:

$ bin/buildout -c releaser.cfg

Usage

Check PyPi access to all Plone packages for a certain user:

$ bin/manage checkPypi timo

Check a package for updates:

$ bin/manage checkPackageForUpdates Products.CMFPlone

Report packages with changes:

$ bin/manage report --interactive

Pulls:

$ bin/manage pulls

Changelog:

$ bin/manage changelog

Launchpad:

$ bin/manage launchpad

Check checkout:

$ bin/manage check-checkout

Append Jenkins build number to package version:

$ bin/append-jenkins-build-number-to-package-version

Set package version:

$ bin/set-package-version

Changelog

1.3 (2015-09-27)

• Fail nicely if a Plone versions.cfg can’t be located [esteele]

• When showing the changelog, accept 1.7.2.1 as version. So loose version numbers instead of strict version numbers with only one or two dots. [maurits]

• Run git pull on buildout.coredev to make sure it is up-to-date. [timo]

• Refactor checkPackageForUpdates to be more flexible. Made it a class on its own module. [gforcada]

• Create a jenkins report based on checkPackageForUpdates. [gforcada]

1.2 (2015-03-21)

• Rename esteele.manager to plone.releaser. [timo]

1.1 (2014-04-23)

• add feature: add the package to the version file if it doesn’t exists [jfroche]

• add command to set the package version in a versions config file [jfroche]

• return the new version number when appending jenkins build number to the versions of a package [jfroche]

1.0 (2014-04-23)

• Initial release [esteele]