Skip to main content

Release facilities to ease the management of buildout based projects.

Project description

https://travis-ci.org/derFreitag/freitag.releaser.svg?branch=master

freitag.releaser

Release facilities to ease the management of buildout based projects.

Standing on the shoulder of giants

This distribution intends to be as small as possible by integrating a few custom release choices done by the der Freitag development team.

For that it heavily relies on a couple of well known distributions:

What’s in?

A few zest.releaser plugins that:

  • check that the git repository is updated update_git_branch

  • update development branches after a release update_develop_branches

  • check translation files are updated check_translations

Additions to plone.releaser:

  • ability to release a distribution within the parent (buildout) project

    • check to ensure the correct branch on the parent project is used check_zope_branch

    • check that the distribution about to release exists check_folders

    • update versions.cfg with the new released version update_versions_cfg

  • (TODO): gather the changes on distributions (more than only collect_changelog)

  • push cfg files publish_cfg_files

  • (TODO): update batou version pins (components/{plone,zeo}/versions/versions.cfg

  • (TODO): check which distributions need a release

  • (TODO): add git changelog to CHANGES.rst

Changelog

0.3 (2015-11-13)

  • Cleanups and code reorganization. [gforcada]

  • Add full-release command. [gforcada]

0.2 (2015-11-11)

  • 0.1 was never released, due to not being registered on PyPI. [gforcada]

0.1 (2015-11-11)

  • add zest.releaser plugins:

    • vcs_updated: checkouts master and develop branches, rebases the former on top of the later (master catches up with develop) and leaves the checked out branch as master, ready to be released

    • i18n: runs bin/i18ndude find-untranslated and reports back if there are any strings not marked for translation

    • update_branches: the oposite from vcs_updated, rebased develop branch on top of master (which was used to make the release)

    [gforcada]

  • emulate plone.releaser and create a freitag_manage command with:

    • publish_cfg_files: send two specific files to a specific server

    • release: releases a distribution (with zest.releaser)

    [gforcada]

  • initial release [gforcada]

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

freitag.releaser-0.3.tar.gz (20.9 kB view details)

Uploaded Source

File details

Details for the file freitag.releaser-0.3.tar.gz.

File metadata

File hashes

Hashes for freitag.releaser-0.3.tar.gz
Algorithm Hash digest
SHA256 1cf4e9677670e160b8fbb9285bbb89a10e19e6f4060a1f178c8691a278dc435f
MD5 20713ba4d7c227d3422ffedce8e79ec3
BLAKE2b-256 36df7dfc55582f622749313732fe296a07c8a5c891ea9480a778a52bf3dccc10

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page