<div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div class="gmail_default" style="font-size:small">Hi Tim,</div><br><div class="gmail_quote"><span class="gmail-im"><div dir="ltr">On Sun, Jun 24, 2018 at 11:59 AM Tim Sutton <<a href="mailto:tim@kartoza.com" target="_blank">tim@kartoza.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word">Hi<div>Did you draft it on Wordpress? I can’t see it there.</div></div></blockquote><div><br></div></span><div><div class="gmail_default" style="font-size:small">​Yes, <a href="https://qgisblog.wordpress.com/wp-admin/post.php?post=2009&action=edit" target="_blank">https://qgisblog.wordpress.com/wp-admin/post.php?post=2009&action=edit</a></div><div class="gmail_default" style="font-size:small"><br></div></div><span class="gmail-im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word">I think that it would be good to message to users that making the release and having packages available for all platforms are not necessarily the same thing. I would lean towards publishing it after unless the content is of the ‘help us get the release ready’ variety.</div></blockquote><div><br></div></span><div><div class="gmail_default" style="font-size:small">​I understand the sentiment but as a recommendation for this specific blog post, these statements sound a bit contradictory since, if we publish it after everything is ready, we imho don't need to stress the difference between release and having packages ready. </div><br></div><div><div class="gmail_default" style="font-size:small">​Regards,</div><div class="gmail_default" style="font-size:small">Anita​</div></div></div><br></div></blockquote></div></div>