[Pulp-dev] Twitter Announcements for Release
bbouters at redhat.com
Thu Oct 26 14:49:19 UTC 2017
Whatever you decide (email or not) is cool w/ me. Thank you for publishing
to PyPI and for any kind of announcement!
On Wed, Oct 25, 2017 at 8:08 PM, Bihan Zhang <bizhang at redhat.com> wrote:
> That is pretty cool! I had no idea that github had a filter like that.
> My initial reservation about sending an email for the alpha releases was
> that there wasn't much to include in the email. I'd be happy to now that
> there is content (changelogs with the merged PR titles) to send.
> On Wed, Oct 25, 2017 at 4:54 PM, Brian Bouterse <bbouters at redhat.com>
>> @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  since the last push. Reading the PR
>> titles probably would tell me a lot about what happened. Does this idea
>> make any sense?
>> : https://help.github.com/articles/searching-issues-and-pull-r
>> 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>
>>>> 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pulp-dev