<div dir="ltr"><div dir="ltr"><div>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:</div><div><br></div><div># Timeline</div><div>May 13 - merge last blocker change (1 left) - <a href="https://etherpad.net/p/pulpcore_rc2_blocker_list">https://etherpad.net/p/pulpcore_rc2_blocker_list</a></div><div>May 14 - 17th -- update plugins in 3 ways (see below) to be rc2 compatible<br></div><div>May 20th @ 2:30pm UTC - rc2 publish</div><div>May 20th - many other plugins release after rc2 bits are available on PyPI</div><div><br></div><div># Plugin Updates Needed</div><div>- All plugins will need to provide a detail Distribution</div><div>- All plugins should consider removing their publishers (generally we are moving away from them)</div><div>- Any plugin that uses Publications will need to provide a detail Publication</div><div><br></div><div><br></div><div>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).</div><div><br></div><div>More feedback is welcome!</div><div>-Brian</div><div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 9, 2019 at 1:32 PM Brian Bouterse <<a href="mailto:bbouters@redhat.com">bbouters@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>I wanted to send an update in preparation for Monday's release core rc2 release. I *think* we're on track for it.</div><div><br></div><div>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.<br></div><div><br></div><div>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.<br></div><div><br></div><div>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.<br></div><div><br></div><div>Any feedback, questions, or concerns are welcome.<br></div><div><br></div><div>[0]: <a href="https://docs.pulpproject.org/en/3.0/nightly/release-notes/pulpcore/3.0.x.html#rc2" target="_blank">https://docs.pulpproject.org/en/3.0/nightly/release-notes/pulpcore/3.0.x.html#rc2</a><br></div><div>[1]: <a href="https://docs.pulpproject.org/en/pulpcore-plugin/nightly/release-notes/index.html#rc2" target="_blank">https://docs.pulpproject.org/en/pulpcore-plugin/nightly/release-notes/index.html#rc2</a></div><div>[2]: <a href="https://etherpad.net/p/pulpcore_rc2_blocker_list" target="_blank">https://etherpad.net/p/pulpcore_rc2_blocker_list</a><br></div><div><br></div><div>Thanks!</div><div>Brian<br></div></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, May 2, 2019 at 1:04 PM Brian Bouterse <<a href="mailto:bbouters@redhat.com" target="_blank">bbouters@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>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.</div><div><br></div><div># Timeline<br></div><div>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.<br></div><div><br></div><div># rc2 unfinished blockers<br></div><div>If you have a Redmine ticket that should block the rc2 release please add it to this etherpad: <a href="https://etherpad.net/p/pulpcore_rc2_blocker_list" target="_blank">https://etherpad.net/p/pulpcore_rc2_blocker_list</a><br></div><div><br></div><div># migrations</div><div>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.<br></div><div><br></div><div># release notes and release prep<br></div><div>I'll make release note and version bump PRs for pulp/pulpcore and pulp/pulpcore-plugin over the upcoming week.</div><div><br></div><div># version numbers</div><div>We're still working towards the same release as before so we just bump the RC number:</div><div>pulpcore 3.0.0rc2</div><div>pulpcore-plugin 0.1.0rc2<br></div><div><br></div><div># communication prep</div><div>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.</div><div><br></div><div>Feedback, questions, discussion, or concerns are all welcome.</div><div><br></div><div>Thanks!</div><div>Brian</div><div><br></div><div><br></div><div><br></div></div></div></div></div></div> </blockquote></div> </blockquote></div></div></div>