News. Development and release plan.

[insspb]

Two weeks ago I was given full permissions to this repository, as well as to readthedocs and pypy.
I see that there is a very small interest in this project from developers, so several things will be changed soon. This is an announcement about these changes.

1. At the Sunday version 1.7.0 will be released to pypy. It will be the current master, with maybe some not-code related changes.
2. This will be the last release with full code reviews from several core committers. Just because it delays development.
3. The final release of 1.7.x expected on December 31. Only bugfixes for 1.7.0 will be reviews at this time.

New year plan.

The history of this project shows two things.

1. It is self-full at this moment. I.e. it does the thing that supposes to do at this moment. All problems have some kinds of workarounds.
2. Waiting for a sponsor is non-effective.

So the decision:

Let's make something new. With honor and respect to the past.

1. From January 1st and later master branch will include new changes that can be non-compatible with the old version but should introduce new functions.
2. Fixes for the old version will be included in new releases of 1.7.x, but only bugfixes for confirmed bugs will be included. All new development should be made in the new version 2.0.x
3. Contributors list for versions 1.x and 2.x will be separated in the documentation.
4. Templates links will be removed from the main master page, as we cannot control templates live and security. I will try to create issue at every template branch, how to implement correct keywords for GitHub search.
5. Most of the issues and pull requests will be closed or merged to 2.0.0 without waiting for contributors. Only live work should be at issues/pr page.

Feel free to comment on this issue. Every thought will be included in the development plan.

[insspb]

• Tag for 1.8.0 for next version where some not deep changes will be made, with still support of Python 2.7 (not sure about 2.7)
• Tag 2.0.0 is wide list of improvements and changes, some will be moved to 1.9 or to 2.1... The goal to make releases more frequently. Not one time in several years :)

All future planning will be in projects tab.

[ljvmiranda921]

The final release of 1.7.x expected on December 31. Only bugfixes for 1.7.0 will be reviews at this time.

Hello @insspb , should we expect a final release of 1.7.X today?

Happy New Year and Happy Holidays!!

[insspb]

Hi @ljvmiranda921, an excuse for missed message, there was a lot of work right before NY (I had a release to production on Jan 7)
There was no significant bugs in 1.7.0 and significant changes, so it was released to pip at Dec without pre-release stage.

[insspb]

Version 1.7.1 released.

1.7.1 (2019-04-21)

This release was focused on internal code and CI/CD changes. During this release all code was verified to match pep8, pep257 and other code-styling guides.
Project CI/CD was significantly changed, Windows platform checks based on Appveyor engine was replaced by GitHub actions tests. Appveyor was removed. Also our CI/CD was extended with Mac builds, to verify project builds on Apple devices.

Important Changes:

• Added: Added debug messages for get_user_config @ssbarnea (Added debug messages for get_user_config #1357)
• Multiple templates per one repository feature added. @RomHartmann (Added: Support for multiple templates per repository #1224, Support template in a subfolder of a repo #1063)
• Update replay.py json.dump indent for easy viewing @nicain (Updated: replay.py json.dump indent added for easy viewing of generated files #1293)
• 'future' library replaced with 'six' as a more lightweight python porting library @asottile (Changed: future library replaced with six library #941)
• Added extension: Slugify template filter @ppanero (Added: slugify template filter #1336)
• Added command line option: --skip-if-file-exists, allow to skip the existing files when doing overwrite_if_exists. @chhsiao1981 (Added: skip-if-file-exists option for overwrite-if-exists mode #1076)
• Some packages versions limited to be compatible with python2.7 and python 3.5 @insspb (Fix compatibility issues for python 2.7, 3.5 #1349)

Internal CI/CD and tests changes:

• Coverage comment in future merge requests disabled @ssbarnea (Removed: coverage comment on CI/CD tasks #1279)
• Fixed Python 3.8 travis tests and setup.py message @insspb (Add support of python 3.8 #1295, Added: pypy3 environment in travis, python 3.8 build on appveyor #1297)
• Travis builds extended with Windows setup for all supported python versions @insspb (Updated: Travis CI/CD pipeline extended with windows builds #1300, Speed up CI/CD #1301)
• Update .travis.yml to be compatible with latest travis cfg specs @luzfcb (Updated: .travis.yml to be compatible with latest travis configuration specs #1346)
• Added new test to improve tests coverage @amey589 (add more test to improve branch coverage #1023)
• Added missed coverage lines highlight to pytest-coverage report @insspb (Add missed coverage lines highlight to pytest-coverage report #1352)
• pytest-catchlog package removed from test_requirements, as now it is included in pytest @insspb (Fix pitest warning, recheck dependencies versions. #1347)
• Fixed cov-report tox invocation environment @insspb (Fix cov-report tox environment run #1350)
• Added: Release drafter support and configuration to exclude changelog update work and focus on development @ssbarnea @insspb (Added: release-drafter initial configuration #1356, Updated: release-drafter configuration to match our changelog format #1362)
• Added: CI/CD steps for Github actions to speedup CI/CD @insspb (Added: CI/CD configuration based on Github actions to speedup CI/CD #1360)
• Removed: Appveyor CI/CD completely removed @insspb @ssbarnea @insspb (Removed: Appveyor CI/CD engine #1363, Drop appveyor referrences #1367)

Code style and docs changes:

• Added black formatting verification on lint stage + project files reformatting @ssbarnea @insspb (Added: Black formatting verification for whole project #1368)
• Added pep257 docstring for tests/* files @insspb (Updated: test_abbreviation_expansion files refactored #1369, Updated: get_config Function exception extended with config file path information #1370, Added: docstrings to tests/repository directory files #1371, Updated: test_generate_hooks refactored #1372, Added: docstrings for extensions feature test files #1373, Updated: test_abort_generate_on_hook_error file refactored #1374, Added: docstrings for invocation test files #1375, Added: docstrings for cookiecutter test files #1376, Add docstrings to cookiecutter test files and updated fixtures syntax #1377, Updated: test_generate* files refactored #1378, Updated: test_prompt.py refactored #1380, Removed: docstrings exclusions from flake8 tests #1381)
• Added pep257 docstring for tests/conftests.py @kishan (Added: pep257 docstrings for "tests/conftests.py" #1272, PEP257 docstrings for file "./tests/conftest.py" #1263)
• Added pep257 docstring for tests/replay/conftest.py @kishan (Added: docstrings for "./tests/replay/conftest.py" #1270, PEP257 docstrings for file "./tests/replay/conftest.py" #1268)
• Added pep257 docstring for docs/init.py @kishan (Added: pep257 docstrings for "docs/__init__.py" #1273, PEP257 docstrings for file "./docs/__init__.py" #1265)
• Added missing docstring headers to all files @croesnick (PEP257 docstrings compliance #1269, Added: Missing docstring headers to all project files #1283)
• Gitter links replaced by Slack in README @browniebroke (Updated: Project readme. Gitter links replaced by Slack links #1282)
• flake8-docstrings tests added to CI/CD @ssbarnea (Added: flake8-docstrings tests #1284)
• Activated pydocstyle rule: D401 - First line should be in imperative mood @ssbarnea (Added: flake8 D401 rule check #1285)
• Activated pydocstyle rule: D200 - One-line docstring should fit on one line with quotes @ssbarnea (Added: flake8 ABS101, D200, D202 rules check #1288)
• Activated pydocstyle rule: D202 - No blank lines allowed after function docstring @ssbarnea (Added: flake8 ABS101, D200, D202 rules check #1288)
• Activated pydocstyle rule: D205 - 1 blank line required between summary line and description @ssbarnea (D205: rule activation #1286, Added: flake8 D205 rule check #1287)
• Activated pydocstyle rule: ABS101 @ssbarnea (Added: flake8 ABS101, D200, D202 rules check #1288)
• Replaced click documentation links to point to version 7 @igorbasko01 (Update in code http links to current click version help #1303)
• Updated submodule link to latest version with documentation links fix @DanBoothDev (Binaries on windows does have extensions, so checking for git existance will fail #1388)
• Fixed links in main README file. @insspb (Fixed: links in main README file #1342)
• Fix indentation of .cookiecutterrc in README.md @mhsekhavat (Fixed: indentation of .cookiecutterrc in README.md #1322)
• Changed format of loggers invocation @insspb (Reformat log messages with variables #1307)

[geerlingguy]

@insspb - It seems like some new build failures (I'm using molecule, yamllint, ansible-lint, and docker) might be related to the cookiecutter 1.7.1 release which was just published. I noticed on one of my Ansible role CI tests that there are some new dependency conflicts which seem to point back to cookiecutter; see https://travis-ci.org/github/geerlingguy/ansible-role-firewall/jobs/677505674#L336-L374

I may be wrong, but the little amount of tracing I did pointed back to here :/ — see related issue geerlingguy/ansible-role-firewall#74

[geerlingguy]

It seems like it can be traced back to b7fcff0#diff-2eeaed663bd0d25b7e608891384b7298

[insspb]

@geerlingguy Thank you for report. Please try 1.7.2, just released to pip.

[geerlingguy]

@insspb - It looks like that fixed it; thanks so much for a quick fix, my other Ansible CI builds that will run through the night are much happier now :)

[insspb]

@geerlingguy No problem, but I saw this accidentally. I checked for new bugs before sleep, but you answered in old topic :) Please create issue next time. Thank you.

[ssbarnea]

@geerlingguy @insspb Thanks!