[Pulp-dev] pulpcore release freeze and release timeline details

Brian Bouterse bmbouter at redhat.com
Fri Dec 13 21:54:24 UTC 2019

David and I chatted on IRC and we opted to use Sprint/Milestone (the
built-in one, per-project in Redmine). Not to be confused with the "Sprint"
field which is a "custom field".

The 764 pulpcore issues received 3.0.0, and the 54 pulp_file issues
received 0.1.0. Those two milestones are "locked", which is Redmine speak
meaning it's not able to be set on additional issues and doesn't show up on
the roadmap page anymore. These issues are all in a closed state now.

I plan to write down a lot of these as I complete
https://pulp.plan.io/issues/5661 along with the notes you provided
regarding how to work around Redmine preventing an issue from going to
CLOSED if it's blocked by an open issue, or has an open parent task.

On Fri, Dec 13, 2019 at 2:40 AM Tatiana Tereshchenko <ttereshc at redhat.com>

> Apart from setting status to CLOSED-CURRENTRELEASE in redmine, should we
> also set a version which features/bugfixes were released in?
> Target release? Platform release?
> Tanya
> On Thu, Dec 12, 2019 at 12:46 AM Brian Bouterse <bmbouter at redhat.com>
> wrote:
>> The 3.0.0 release is available on PyPI [0], and docs are available [1]
>> along with the bindings [2][3]. This should unblock pulp_rpm,
>> pulp_container, and pulp_file from releasing. For each of these three
>> plugins, please reply-all to this note so we can know each is done. After
>> all 3 are released we will announce publicly on twitter, the blog, and
>> pulp-list. I will handle the pulp_file release.
>> I'll reply to this note with links to release announcements and website
>> revisions as soon as they are drafted (tomorrow morning Eastern time).
>> Tomorrow @dkliban and I will replace https://docs.pulpproject.org/ to
>> show [1] by default. Also tomorrow, I'll do a mass-close to CURRENTRELEASE
>> in pulp.plan.io of both pulpcore and pulp_file issues once announced. It
>> would be great if pulp_rpm and pulp_contianer could handle their own issue
>> transitions.
>> [0]: https://pypi.org/project/pulpcore/
>> [1]: https://docs.pulpproject.org/en/3.0.0/
>> [2]:  https://rubygems.org/gems/pulpcore_client/versions/3.0.0
>> [3]: https://pypi.org/project/pulpcore-client/3.0.0/
>> On Thu, Dec 5, 2019 at 12:51 PM Brian Bouterse <bmbouter at redhat.com>
>> wrote:
>>> Releasing takes time, and we need pulpcore to be available before the
>>> releasing of plugins can start. Here's a proposed timeline to allow that to
>>> happen.
>>> Dec 10 - 22:00 all code merged to 'master'
>>> Dec 11 - pushing pulpcore 3.0.0 GA to pypi, then pulp_file 0.1.0 to
>>> pypi. Announce only to pulp-dev (not the official announcement)
>>> Dec 12 - pulp_rpm, pulp_container release
>>> Dec 12 - the docs.pulpproject.org and pulpproject.org website changes
>>> are applied
>>> Dec 12 - Send out announcement to pulp-dev, twitter, and blog
>>> @ttereshc and @ipanova how does this look to you for releasing pulp_rpm
>>> and pulp_container on the 12th?
>>> Any feedback or adjustment is welcome; please let me know.
>>> Thanks!
>>> Brian
>>> _______________________________________________
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
>> https://www.redhat.com/mailman/listinfo/pulp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20191213/5b5e23e0/attachment.htm>

More information about the Pulp-dev mailing list