[Pulp-dev] Twitter Announcements for Release

Brian Bouterse bbouters at redhat.com
Wed Oct 25 20:54:09 UTC 2017

@bizhang, that sounds great! Thank you. Speaking of alpha pushes to PyPI,
does it make any sense to also email pulp-dev when its pushed also? If not
that's ok too.

I also had another idea I wanted to share. Since we don't identify
changelogs for each alpha release, either a tweet and/or email could
contain a link to the PRs merged [0] since the last push. Reading the PR
titles probably would tell me a lot about what happened. Does this idea
make any sense?

[0]: https://help.github.com/articles/searching-issues-and-

On Tue, Oct 24, 2017 at 8:07 PM, Bihan Zhang <bizhang at redhat.com> wrote:

> Hey Brian,
> I can't speak for our 2.y line releases (but AFAIK it should be easy
> enough to add to the internal release process document, with some details
> on how to get the credentials), but I would love to start doing this for
> the pulp3 pypi alpha releases.
> Currently there is some uncertainty about when the alphas come out. A
> tweet is, I think, the best way to communicate this due to their short and
> relatively informal nature.
> On Tue, Oct 24, 2017 at 2:34 PM, Brian Bouterse <bbouters at redhat.com>
> wrote:
>> A few months ago, I informally started tweeting about releases (beta, RC,
>> and GA) from @pulpproj. Examples [0][1].
>> I'm not in a good position to do this because I'm not always sure when
>> releases will occur and/or may not be available. Is there some way that
>> this communication can be handled as part of the release process itself
>> similar to the pulp-list announcements that go out?
>> [0]: https://twitter.com/pulpproj/status/920643150007472129
>> [1]: https://twitter.com/pulpproj/status/895402133956292609
>> _______________________________________________
>> 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/20171025/cda17ac2/attachment.htm>

More information about the Pulp-dev mailing list