pulp_container 1.1.0 is GA with the set of new features and bugfixes. It is
also compatible with pulpcore 3.1.

https://pulp-container.readthedocs.io/en/1.1/changes.html
https://pypi.org/project/pulp-container/1.1.0/


--------
Regards,

Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.

"Do not go where the path may lead,
 go instead where there is no path and leave a trail."


On Fri, Jan 31, 2020 at 1:12 PM Brian Bouterse <bmbou...@redhat.com> wrote:

> Pulpcore 3.1.0 is the first feature release of Pulp 3 and contains some
> significant features and fixes. See the release notes for all the details.
> https://docs.pulpproject.org/en/3.1.0/changes.html Here are some
> highlights:
>
> * Azure support
> * signing services for plugins to use
> * restriction of file:// paths and a new setting to mark filesystem areas
> as safe to import from
> * improved webserver auth support
> * various bugfixes including resolution of a task hanging issue, S3
> filename fix, and more
>
> Pulpcore 3.1.0 contains no user API breaking changes (ever), but plugins
> will require a compatibility release due to the plugin API bringing
> breaking changes in with each Y-release. Users should watch for
> announcements from plugins soon and upgrade when all of your plugins are
> compatible. Plugin writers can see their changelog to see what has changed
> in the plugin API here:
>
> ## New Installations
>
> If you are using a new install, you can use the ansible-installer directly
> and you'll receive 3.1.0. The quick start guides below are useful for
> that.
>
> * pulp_rpm installation -- https://pulp-rpm.readthedocs.io/en/3.0
> /installation.html
> * pulp_container installation -- https://pulp-container.readthedocs.io/en/
> 1.0/installation.html
> * pulp_file installation -- https://pulp-file.readthedocs.io/en/0.1
> .0/installation.html
>
> ## Updating from 3.0.z
>
> You should first upgrade your installer to the latest one from PyPI and
> re-run it. Starting with 3.1.0 each release will push a new version of the
> installer. If you get the new installer, you'll get a newer pulpcore
> release.
>
> ## Quickstart
>
> Pulp_rpm offers a quickstart guide (link below) which uses pulplift (link
> below) to create a not-long-living installation just to try it out. These
> same instructions can be adapted to the other plugins also.
>
> https://pulp-rpm.readthedocs.io/en/3.0/quickstart.html
> https://github.com/pulp/pulplift
>
> ## Migrating from Pulp2 -> Pulp3
>
> A Pulp 2 -> Pulp 3 migration tool is now in beta and can migrate docker
> and iso content ( https://github.com/pulp/pulp-2to3-migration ). RPM
> migrations are coming soon, but are not ready yet.
>
> ## Getting Help or Reporting Bugs
>
> Find where to get help or report bugs via the help page on the website (
> https://pulpproject.org/help/ ). If you're unsure where to start, we
> recommend emailing your question to the Pulp user mailing list (
> https://www.redhat.com/mailman/listinfo/pulp-list ).
>
> ## Feedback
>
> Let us know what you think! Please send feedback to either:
>
> * Pulp user mailing list --
> https://www.redhat.com/mailman/listinfo/pulp-list
> * Pulp developer mailing list --
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
> ## Thanks!
>
> Thank you to all the developers, integrators, testers, and users who have
> contributed to this feature release.
> _______________________________________________
> Pulp-list mailing list
> Pulp-list@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Reply via email to