From c4bcf1d88784f23d070a863cdaab1b59b25d91f8 Mon Sep 17 00:00:00 2001 From: Petr Viktorin Date: Tue, 5 Dec 2017 13:41:25 +0100 Subject: [PATCH] Add the 3.0.0b1 release date to CHANGES Also, put this in the release checklist --- CHANGES | 2 +- Doc/contributing.rst | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/CHANGES b/CHANGES index df35179..5c46505 100644 --- a/CHANGES +++ b/CHANGES @@ -1,5 +1,5 @@ ---------------------------------------------------------------- -Released 3.0.0b1 xxxx-xx-xx +Released 3.0.0b1 2017-12-04 Changes since 2.4.45: (this list includes changes from 2.5.x) diff --git a/Doc/contributing.rst b/Doc/contributing.rst index aa6097d..c87ccf3 100644 --- a/Doc/contributing.rst +++ b/Doc/contributing.rst @@ -259,6 +259,7 @@ If you are tasked with releasing python-ldap, remember to: * Bump all instances of the version number. * Go through all changes since last version, and add them to ``CHANGES``. * Run :ref:`additional tests` as appropriate, fix any regressions. +* Change the release date in ``CHANGES``. * Merge all that (using pull requests). * Run ``python setup.py sdist``, and smoke-test the resulting package (install in a clean virtual environment, import ``ldap``).