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/2000-September/009227.html below:

[Python-Dev] SF checkin policies

[Python-Dev] SF checkin policies [Python-Dev] SF checkin policiesFredrik Lundh fredrik@pythonware.com
Thu, 7 Sep 2000 16:04:13 +0200
> What are the checkin policies to the sourceforge
> CVS repository?

http://python.sourceforge.net/peps/pep-0200.html

    Use good sense when committing changes.  You should know what we
    mean by good sense or we wouldn't have given you commit privileges
    <0.5 wink>.

    /.../

    Any significant new feature must be described in a PEP and
    approved before it is checked in.

    /.../

    Any significant code addition, such as a new module or large
    patch, must include test cases for the regression test and
    documentation.  A patch should not be checked in until the tests
    and documentation are ready.

    /.../

    It is not acceptable for any checked in code to cause the
    regression test to fail.  If a checkin causes a failure, it must
    be fixed within 24 hours or it will be backed out.

</F>




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