On Wed, Jun 16, 2010 at 7:43 PM, Milan Dinić <span dir="ltr"><<a href="mailto:liste@srpski.biz">liste@srpski.biz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<div class="im"><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<span style="font-family: arial, sans-serif; font-size: 13px; border-collapse: collapse; ">Sure, Ryan will post here when 3.0 is released.</span></blockquote><div><br></div></div></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
This is not a permanent solution since Ryan will post it for 3.0, but what about minor releases in branch (3.0.1, 3.0.2 etc)? Ryan is not the only one who is making those releases.</blockquote><div><br></div><div>All minor/major releases are always going to be deployed by the lead developer. (Not referring to alpha/beta/RC pre-releases; those might be done by other lead devs.) Emailing polyglots should indeed be part of our launch routine and I don't see a reason to develop a notification service other than us manually sending an email as we are prepping everything for release.<div>
<br></div><div>I would prepare for a launch tomorrow, during the afternoon (GMT time).</div></div>