<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">One of the stated goals of our effort is to move to calendar-based 6-monthly releases of GHC. To this end, I had a conversation with Ben a while ago, where discussed the following schedule for v6.4 & v6.6:<div class=""><br class=""></div><div class=""> 6.4 release planned for Feb</div> - Branch in Nov<br class=""><br class=""> 6.6 release ought to then be in Aug<br class=""> - Branch in May<br class=""><br class=""> Pre-release schedule<br class=""> - On cutting the branch, alpha release<br class=""> - Then, a beta every two weeks until 4 weeks before the targeted release date<br class=""> - RC1 four weeks before the targeted release date<br class=""> - RC2 two weeks before the targeted release date<div class=""><br class=""></div><div class="">For this to be realistic, we do need to have the automatic release artefact building in place by the time of cutting the v6.4 branch. This doesn’t leave us much time to get this up and running.</div><div class=""><br class=""></div><div class="">Ben, this also requires us to settle </div><div class=""><br class=""></div><div class=""> <a href="https://github.com/snowleopard/hadrian/issues/440" class="">https://github.com/snowleopard/hadrian/issues/440</a></div><div class=""><br class=""></div><div class="">soon.</div><div class=""><br class=""></div><div class="">We need to discuss a policy of what can go into the release branch after it has been cut. IMHO, it cannot be major features, but only small changes and fixes until RC1. Then, only fixes.</div><div class=""><br class=""></div><div class="">What do you all think?</div><div class=""><br class=""></div><div class="">Cheers,</div><div class="">Manuel</div><div class=""><br class=""></div></body></html>