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

[Tatiana Tereshchenko]

pulp_rpm is released.

https://pypi.org/project/pulp-rpm/
https://pulp-rpm.readthedocs.io/en/3.0/
https://pypi.org/project/pulp-rpm-client/3.0.0/
https://rubygems.org/gems/pulp_rpm_client/versions/3.0.0

On Thu, Dec 12, 2019 at 5:51 PM Ina Panova <ipanova at redhat.com> wrote:

> pulp_container is released.
>
> https://pypi.org/project/pulp-container/
> https://pulp-container.readthedocs.io/en/1.0/
> https://pypi.org/project/pulp-container-client/1.0.0/
> https://rubygems.org/gems/pulp_container_client/versions/1.0.0/
>
> --------
> Regards,
>
> Ina Panova
> Senior Software Engineer| Pulp| Red Hat Inc.
>
> "Do not go where the path may lead,
>  go instead where there is no path and leave a trail."
>
>
> On Thu, Dec 12, 2019 at 4:59 PM Brian Bouterse <bmbouter at redhat.com>
> wrote:
>
>> pulp_file is released.
>>
>> https://pypi.org/project/pulp-file/
>> https://pulp-file.readthedocs.io/en/0.1.0/
>> https://pypi.org/project/pulp-file-client/0.1.0/
>> https://rubygems.org/gems/pulp_file_client/versions/0.1.0
>>
>>
>> On Wed, Dec 11, 2019 at 6:45 PM 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
>>
> _______________________________________________
> 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/20191212/6212b4ac/attachment.htm>