Re: [Pulp-dev] [Pulp-list] pulpcore 3.2.0 and pulp_file 0.2.0 releases

[Dennis Kliban]

pulp_container 1.2.0 has been released[0]. It is compatible with pulpcore
3.2. For a list of all changes please check the changelog[1].

[0]: https://pypi.org/project/pulp-container/1.2.0/
[1] https://pulp-container.readthedocs.io/en/latest/changes.html#id1

On Thu, Feb 27, 2020 at 4:02 PM David Davis  wrote:

> pulpcore 3.2.0[0] and pulp_file 0.2.0[1] have been released. For a list of
> all changes, please check the changelogs for pulpcore[2] and pulp_file[3].
>
> # Installation and Upgrade
>
> Users should use the 3.2.0 release of ansible-pulp installer[4] to install
> or upgrade their installations. This version of the installer will check
> compatibility of all installed plugins with pulpcore 3.2. The installer
> will abort if any plugin is incompatible.
>
> # Plugin API
>
> Plugin writers can see the plugin API changelog here (
> https://docs.pulpproject.org/en/3.2.0/changes.html#plugin-api ). There
> was only one backwards incompatible change[5], and in keeping with the
> recommended strategy to pin plugins to a 3.y version of pulpcore, plugins
> should release compatibility releases with 3.2 as soon as they can. We
> recommend using "pulpcore>=3.0,<3.3".
>
> The installer also has a backwards incompatible change in 3.2.0 where it
> no longer attempts to handle custom URLs for plugins automatically. If your
> plugin uses URLs outside of /pulp/api/v3/ or /pulp/content/ you will need
> to add a snippet. See these docs[6] for more.
>
> [0]: https://pypi.org/project/pulpcore/3.2.0/
> [1]: https://pypi.org/project/pulp-file/0.2.0/
> [2]: https://docs.pulpproject.org/changes.html#id1
> [3]: https://pulp-file.readthedocs.io/en/0.2.0/changes.html#id1
> [4]: https://github.com/pulp/ansible-pulp/releases/tag/3.2.0
> [5]: https://github.com/pulp/pulpcore/pull/555
> [6]: https://pulp.plan.io/issues/6057
>
> David
> ___
> Pulp-list mailing list
> pulp-l...@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

[Tatiana Tereshchenko]

Pulp 3:

   -

   Copy API Status (dalley out-of-office)
   -

  General API shape + implementation: done
  -

  Depsolving: done
  -

  Incremental update: done
  -

  Multi-repo-copy: almost done
  -

 just need to hook the backend to the API properly, no serious
 implementation effort required
 -

  Thorough functional tests: discussions taking place
  -

   When do we want Z release
   -

  https://pulp.plan.io/issues/6229
  -

  ‘Now’ would be good
  -

   Tests conversion status (ppicka)
   -

  Hopefully today/tomorrow parity w/Pulp2
  -

   Features status (anyone working on features)
   -

  Opensuse support (ppicka)
  -

 started
 -

  Optimize sync (dawalker)
  -

 testing scenarios now
 -

  https://pulp.plan.io/issues/6281
  -

 Looking for volunteer
 -

 pulpcore item driven by rpm needs
 -

   Need to test new createrepo_c which supports parsing of xml_snippets
   (needed for the migration plugin)
   -

   Whenever it’s released, we need to publish new version to PyPI



Pulp 2:

   -

   Check applicability and depsolving for modularity multicontext issues



Open PRs:

   -

   https://github.com/pulp/pulp_rpm/pulls


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30


Sprint planning prep:

   -

   Items planned to be worked on during sprint and estimated time for each
   -

  David
  -

 Copy: 1-2 days
 -

 Importers/exporters 3-4 days
 -

  Pavel
  -

 Opensuse support 1-3 days (hard to say with this one)
 -

 Finish modularity upload or higher prio
 -

  Dana
  -

 Checksum options work, 4 days?
 -

 Available for other work
 -

  Daniel (out today)
  -

 [ttereshc guess] Finishing up Copy work
 -

  Grant
  -

 Import/Export: 5 days
 -

 #4534  (if critical): 2 days
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev