A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-July/121138.html below:

[Python-Dev] feature freeze questions

[Python-Dev] feature freeze questions [Python-Dev] feature freeze questionsBenjamin Peterson benjamin at python.org
Thu Jul 26 01:29:45 CEST 2012
2012/7/25 Chris Jerdonek <chris.jerdonek at gmail.com>:
> I have a few questions about feature freeze:
>
> (1) Is increasing test coverage acceptable during feature freeze, even
> if it does not involve fixing a bug?
>
> (2) When adding new tests (e.g. in the course of fixing a bug or
> increasing test coverage), are we allowed to refactor other tests so
> that supporting test code can be shared?  Or should the tests be added
> in a less DRY fashion and refactored only after the branch goes back
> to pre-alpha?

You can do basically anything you want to tests just as long as you
don't make them less stable.

>
> (3) What types of documentation changes are allowed during feature
> freeze?  For example, are we only allowed to fix incorrect
> information, or is it acceptable to improve or add to the information
> about existing functionality?

All documentation changes are accepted.


-- 
Regards,
Benjamin
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4