Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
镜像
Python_Packaging_Authority
pip
提交
dec22c92
P
pip
项目概览
镜像
/
Python_Packaging_Authority
/
pip
11 个月 前同步成功
通知
0
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
P
pip
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
dec22c92
编写于
4月 22, 2018
作者:
D
Donald Stufft
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Switch to CalVer and set a release cadence
上级
3c0d97a0
变更
6
隐藏空白更改
内联
并排
Showing
6 changed file
with
41 addition
and
8 deletion
+41
-8
docs/development.rst
docs/development.rst
+32
-6
news/_template.rst
news/_template.rst
+1
-1
news/calver.process
news/calver.process
+1
-0
news/release-cadence.process
news/release-cadence.process
+1
-0
pyproject.toml
pyproject.toml
+5
-0
src/pip/__init__.py
src/pip/__init__.py
+1
-1
未找到文件。
docs/development.rst
浏览文件 @
dec22c92
...
...
@@ -131,6 +131,30 @@ bugfixes, or other kinds of news that pulling in this library may have. This
uses the library name as the key so that updating the same library twice doesn't
produce two news file entries.
Changes to the processes, policies, or other non code related changed that are
otherwise notable can be done using a ``news/<name>.process`` file. This is not
typically used, but can be used for things like changing version schemes,
updating deprecation policy, etc.
Release Cadence
===============
The pip project has a release cadence of releasing whatever is on `master`
every 3 months. This gives users a predictable pattern for when releases
are going to happen and prevents locking up improvements for fixes for long
periods of time, while still preventing massively fracturing the user base
with version numbers.
Our release months are January, April, July, October. The release date within
that month will be up to the release manager for that release. If there are
no changes, then that release month is skipped and the next release will be
3 month later.
The release manager may, at their discretion, choose whether or not there
will be a pre-release period for a release, and if there is may extend that
period into the next month if needed.
Release Process
===============
...
...
@@ -139,7 +163,9 @@ Release Process
running ``invoke generate.authors`` and commit the results.
#. On the current pip ``master`` branch, make a new commit which bumps the
version in ``pip/__init__.py`` to the release version and adjust the
``CHANGES.txt`` file to reflect the current date.
``CHANGES.txt`` file to reflect the current date. The release version should
follow a YY.N scheme, where YY is the two digit year, and N is the Nth release
within that year.
#. On the current pip ``master`` branch, generate a new ``NEWS.rst`` by running
``invoke generate.news`` and commit the results.
#. Create a signed tag of the ``master`` branch of the form ``X.Y.Z`` using the
...
...
@@ -162,14 +188,14 @@ Sometimes we need to release a bugfix release of the form ``X.Y.Z+1``. In order
to create one of these the changes should already be merged into the
``master`` branch.
#. Create a new ``release/
X.Y.Z+1`` branch off of the ``X.Y.Z
`` tag using the
command ``git checkout -b release/
X.Y.Z+1 X.Y.Z
``.
#. Create a new ``release/
YY.N.Z+1`` branch off of the ``YY.N
`` tag using the
command ``git checkout -b release/
YY.N.Z+1 YY.N
``.
#. Cherry pick the fixed commits off of the ``master`` branch, fixing any
conflicts and moving any changelog entries from the development version's
changelog section to the ``
X.Y
.Z+1`` section.
#. Push the ``release/
X.Y
.Z+1`` branch to github and submit a PR for it against
changelog section to the ``
YY.N
.Z+1`` section.
#. Push the ``release/
YY.N
.Z+1`` branch to github and submit a PR for it against
the ``master`` branch and wait for the tests to run.
#. Once tests run, merge the ``release/
X.Y
.Z+1`` branch into master, and follow
#. Once tests run, merge the ``release/
YY.N
.Z+1`` branch into master, and follow
the above release process starting with step 4.
...
...
news/_template.rst
浏览文件 @
dec22c92
...
...
@@ -13,7 +13,7 @@
{% if definitions[category]['showcontent'] %}
{% for text, values in sections[section][category]|dictsort(by='value') %}
- {{ text }}{% if category != 'vendor' %} ({{ values|sort|join(', ') }}){% endif %}
- {{ text }}{% if category != 'vendor'
and category != 'process'
%} ({{ values|sort|join(', ') }}){% endif %}
{% endfor %}
{% else %}
...
...
news/calver.process
0 → 100644
浏览文件 @
dec22c92
Switch to a Calendar based versioning scheme.
news/release-cadence.process
0 → 100644
浏览文件 @
dec22c92
Switch to releasing a new, non bug fix version of pip every 3 months.
pyproject.toml
浏览文件 @
dec22c92
...
...
@@ -9,6 +9,11 @@ directory = "news/"
title_format
=
"{version} ({project_date})"
template
=
"news/_template.rst"
[[tool.towncrier.type]]
directory
=
"process"
name
=
"Process"
showcontent
=
true
[[tool.towncrier.type]]
directory
=
"removal"
name
=
"Deprecations and Removals"
...
...
src/pip/__init__.py
浏览文件 @
dec22c92
__version__
=
"1
0.0.1
"
__version__
=
"1
8.0.dev0
"
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录