You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/intro/community.rst
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -62,12 +62,12 @@ Submitting a PEP
62
62
Python Conferences
63
63
--------------------------
64
64
65
-
The major venue of the Python community are developer conferences. The two most notable conferences are PyCon, which is held in the US and it's overseas sibling EuroPython.
65
+
The major venue of the Python community are developer conferences. The two most notable conferences are PyCon, which is held in the US and it's european sibling, called EuroPython.
66
66
67
-
A comprehensive list of conferences is maintained `here<http://www.pycon.org/>`_.
67
+
A comprehensive list of conferences is maintained `at pycon.org<http://www.pycon.org/>`_.
68
68
69
69
70
70
Python User Groups
71
71
--------------------------
72
72
73
-
User Groups are where a bunch of Python developers meet to present or talk about python topics of interest. A list of local user groups is maintained in the `Python Software Foundation Wiki <http://wiki.python.org/moin/LocalUserGroups>`_.
73
+
User Groups are where a bunch of Python developers meet to present or talk about Python topics of interest. A list of local user groups is maintained at the `Python Software Foundation Wiki <http://wiki.python.org/moin/LocalUserGroups>`_.
Copy file name to clipboardExpand all lines: docs/scenarios/ci.rst
+5Lines changed: 5 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -5,6 +5,11 @@ Continuous Integration
5
5
Why?
6
6
----
7
7
8
+
Martin Folwer, who first wrote about Continuous Integration (short: CI) together with Kent Beck, describes the CI as follows:
9
+
10
+
Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly. This article is a quick overview of Continuous Integration summarizing the technique and its current usage.
0 commit comments