[Pulp-dev] pulpcore rc2 proposal to release May 20th

[Brian Bouterse]

After some off-list feedback (thanks!), we're moving the rc2 release date
back to May 20th. Our goal is to give plugin writers time to update their
source to be compatible with rc2 and then have core and many plugins
release together on May 20th. Here's a recap of the timeline:

# Timeline
May 13 - merge last blocker change (1 left)  -
https://etherpad.net/p/pulpcore_rc2_blocker_list
May 14 - 17th   --  update plugins in 3 ways (see below) to be rc2
compatible
May 20th @ 2:30pm UTC - rc2 publish
May 20th - many other plugins release after rc2 bits are available on PyPI

# Plugin Updates Needed
- All plugins will need to provide a detail Distribution
- All plugins should consider removing their publishers (generally we are
moving away from them)
- Any plugin that uses Publications will need to provide a detail
Publication


All ^ changes are unblocked so you could start those updates now even.
Please send any questions about how to update your plugins (and/or why).

More feedback is welcome!
-Brian


On Thu, May 9, 2019 at 1:32 PM Brian Bouterse <bbouters at redhat.com> wrote:

> I wanted to send an update in preparation for Monday's release core rc2
> release. I *think* we're on track for it.
>
> The pulpcore and pulpcore-plugin verison bumps have happened and some
> release notes for each have been merged. It contains breaking changes
> listed with pulpcore focusing on user changes and pulpcore-plugin focusing
> on plugin writer breaking changes. You can see those docs [0][1] even
> though it's unreleased because these are source-tree docs.
>
> All plugins will need to make updates to handle breaking changes for
> pulpcore-plugin 0.1.0rc2. The release notes outline the changes that are
> already merged (master/detail publications), but doesn't yet describe the
> master/detail distribution changes. Basically you need to account for
> Master/Detail Publications (if you use publications) and Master/Detail
> Distributions (all plugins). Hopefully plugins will be about to release
> versions compatible with pulpcore-plugin 0.1.0rc2 over the week of the 13th.
>
> We're working through the blockers [2]. We have a group of folks on irc
> working through them so I think we've got enough help to get it released
> Monday, if plugins can update their own compatibility over the next week.
> Please reach out if you could use some help.
>
> Any feedback, questions, or concerns are welcome.
>
> [0]:
> https://docs.pulpproject.org/en/3.0/nightly/release-notes/pulpcore/3.0.x.html#rc2
> [1]:
> https://docs.pulpproject.org/en/pulpcore-plugin/nightly/release-notes/index.html#rc2
> [2]: https://etherpad.net/p/pulpcore_rc2_blocker_list
>
> Thanks!
> Brian
>
> On Thu, May 2, 2019 at 1:04 PM Brian Bouterse <bbouters at redhat.com> wrote:
>
>> It's been a little over a month since pulpcore 3.0.0rc1  and
>> pulpcore-plugin 0.1.0rc1 were released. Many bugfixes and several usability
>> improvements have happened since then so we should prepare to release an
>> rc2.
>>
>> # Timeline
>> I propose we release on May 13th giving a week for anyone to wrap up work
>> that needs to go into rc2. @daviddavis and I can work together to release
>> it on that day.
>>
>> # rc2 unfinished blockers
>> If you have a Redmine ticket that should block the rc2 release please add
>> it to this etherpad:  https://etherpad.net/p/pulpcore_rc2_blocker_list
>>
>> # migrations
>> We will be squashing migrations and only ship a 0001 migration. We will
>> clearly communicate that there is not an upgrade path from rc1 -> rc2 in
>> user communication.
>>
>> # release notes and release prep
>> I'll make release note and version bump PRs for pulp/pulpcore and
>> pulp/pulpcore-plugin over the upcoming week.
>>
>> # version numbers
>> We're still working towards the same release as before so we just bump
>> the RC number:
>> pulpcore 3.0.0rc2
>> pulpcore-plugin 0.1.0rc2
>>
>> # communication prep
>> I'll help draft a pulp-list email and get some revision from other devs
>> next week. I don't plan on making a blog post.
>>
>> Feedback, questions, discussion, or concerns are all welcome.
>>
>> Thanks!
>> Brian
>>
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20190510/9f831512/attachment.htm>