On Fri, Apr 22, 2016 at 09:59:40AM -0400, Joe Brockmeier wrote: > Hi all, > > Somehow despite me sending this last night - this was published. How can > we prevent communication breakdowns like this in the future? > > This was sent prior to or during the magazine meeting, if I'm not mistaken. > > If there's *any* uncertainty around something like this, it should not > be published. Agreed, and it's incumbent on whoever schedules a post to confirm it's meant to go out. The bar is higher for articles about what we deliver, as opposed to helpful how-to articles. It's hard to see how a premature article like that would cause any issues, but clearly this one could. Also, this was picked up by at least one venue that checks our feeds for reportable news: https://www.phoronix.com/scan.php?page=news_item&px=Fedora-Cloud-32-bit-Dead Does someone have a contact with Phoronix so we could explain the snafu here? -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ The open source story continues to grow: http://opensource.com _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx
