[Pulp-dev] pulpcore 3.3.0 GA timeline
ttereshc at redhat.com
Tue Apr 14 17:29:29 UTC 2020
The release is currently blocked by:
- the issue with ordering of content https://pulp.plan.io/issues/6347
- issues with CI
We will update this thread when the release is unblocked (likely tomorrow).
On Thu, Apr 9, 2020 at 5:52 PM Tatiana Tereshchenko <ttereshc at redhat.com>
> We decided to wait a bit more to include the import/export basic
> functionality into the release.
> The current plan is to release pulpcore==3.3.0 GA on April 14th.
> The deadline for merging code is April 13th 23:59:59 EDT. We are planning
> to start the release process on Tuesday morning.
> The following items are no longer blocking the release:
> * The new repository repair API /pulp/api/v3/repair/ -
> https://pulp.plan.io/issues/5613 - is done and merged.
> * The setting to increase the accepted header size for pulpcore-content -
> https://pulp.plan.io/issues/6460 - is moved to 3.4.
> On Wed, Apr 1, 2020 at 8:58 PM Brian Bouterse <bmbouter at redhat.com> wrote:
>> We are planning to release pulpcore==3.3.0 GA on April 8th. While we
>> strive for time-based releases, here are two items that we are hoping to
>> include based on feedback from Katello who would like to consume 3.3.0 in
>> their upcoming releases.
>> * The new repository repair API /pulp/api/v3/repair/ -
>> https://pulp.plan.io/issues/5613. This one is a must-have.
>> * The import/export parts that belong in pulpcore -
>> https://pulp.plan.io/issues/6134. This one is a nice-to-have and will
>> tech-preview if not fully complete.
>> ## What plugin writers need to know
>> Look at the backwards incompatible changes in the plugin API release
>> notes to determine if your plugin will require a compatibility release.
>> Those are the *.removal entries here:
>> Feedback, questions, and discussion are welcome.
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev