Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 18 additions & 5 deletions docs/release-notes/3.0.z.rst
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,24 @@ pulp-python 3.0 Release Notes
pulp-python 3.0 is currently in Beta. Backwards incompatible changes
might be made until Beta is over.

3.0.0b6
=======

* See all changes `here <https://github.com/pulp/pulp_python/compare/3.0.0b5...3.0.0b6>`_.

* Adds support for `pulpcore 3.0.0.rc2 <https://docs.pulpproject.org/en/3.0/rc/release-notes/pulpcore/3.0.x.html#rc2>`_.

Changes urls for distributions and publications

* Adds lazy sync

* Docs replace snippets with testable scripts

3.0.0b5
=======

* Fix relative_path to allow pip install
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you add a link to a redmine issue for this one?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, I think we should start including links like these: 3.0.0b4...3.0.0b5

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's not new, it's only showing up that way because I reordered our release notes to show the most recent first (b6->b5->b4) to match the way pulpcore does them: https://docs.pulpproject.org/en/3.0/rc/release-notes/pulpcore/3.0.x.html#rc2 instead of the way we had them before (b4->b5)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As for the release comparison links, I like that idea--is github reliable in it being that pattern since I can't otherwise create that link ahead of actually releasing b6?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, you can go ahead and say b6 and the link will work once its tagged.


3.0.0b4
=======

Expand All @@ -21,8 +39,3 @@ might be made until Beta is over.
synced. This mirrors the 'prereleases' flag that packaging.specifiers.SpecifierSet provides.

* Removes Python 3.5 support

3.0.0b5
=======

* Fix relative_path to allow pip install
4 changes: 2 additions & 2 deletions setup.py
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@
from setuptools import setup, find_packages

requirements = [
'pulpcore-plugin~=0.1rc1',
'pulpcore-plugin~=0.1rc2',
'pkginfo',
'packaging',
]
Expand All @@ -13,7 +13,7 @@

setup(
name='pulp-python',
version='3.0.0b5',
version='3.0.0b6',
description='pulp-python plugin for the Pulp Project',
long_description=long_description,
license='GPLv2+',
Expand Down