[Pulp-dev] Twitter Announcements for Release
pcreech at redhat.com
Thu Oct 26 20:02:54 UTC 2017
I don't mind picking this up as part of the release process, as I hope to automate these annoucements in the future and having access will help with that. I do ask that with 2.14.2 being imminent (a
matter of hours), would you be able to handle it one more time for 2.14.2 since we don't have the process in place and the credentials handed over?
On Tue, 2017-10-24 at 20:07 -0400, Bihan Zhang 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 .
> > 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?
> > : https://twitter.com/pulpproj/status/920643150007472129
> > : https://twitter.com/pulpproj/status/895402133956292609
> > _______________________________________________
> > 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
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: This is a digitally signed message part
More information about the Pulp-dev