<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:10pt">I think a 7 day push out would be better. No need to release and have someone stew about bugs the entire weekend. When I maintained systems releases/upgrades were on Tuesday or Wednesday at the latest. Otherwise, it was pushed to the next week. Of course, there was overtime to pay on weekends if things went wrong.<br><div><br></div><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><br><div style="font-family:arial, helvetica, sans-serif;font-size:13px"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Jacek Antonelli <jacek@kokuaviewer.org><br><b><span style="font-weight: bold;">To:</span></b> impdev@lists.imprudenceviewer.org<br><b><span style="font-weight: bold;">Sent:</span></b> Tue, May 24, 2011 5:28:40 PM<br><b><span
style="font-weight: bold;">Subject:</span></b> [impdev] Release plans for 1.4 beta 1; I'm unavailable this weekend.<br></font><br>
I will be out of town this weekend to attend a family event. I will be<br>leaving Saturday morning, and returning Monday night or Tuesday. I<br>might be able to check email on Sunday, but otherwise I'll be<br>unavailable. I'm anxious to get Imp 1.4 beta 1 released soon, but I<br>think it will need to wait until after I get back.<br><br>Two alternatives would be to rush and try to release it before I<br>leave, or else to release it this weekend without me. I think trying<br>release it before I leave is infeasible; it would be very stressful<br>and lead to poor results anyway. Releasing it this weekend without me<br>is somewhat more feasible, but I think we're going to need "all hands<br>on deck" for the release.<br><br>So, I would advise we push to finish it up in the next 7 days, then<br>release it soon after I have returned. I can help with coding until I<br>leave, then work on the release notes while I'm travelling. 1.4 has a<br>huge number of
differences compared to 1.3, so it will take several<br>days just to assemble the release notes for what we have already done<br>now. While I'm gone, the rest of you can make some final commits to<br>finish the code.<br><br>Let me know your thoughts on this plan.<br><br>- Jacek<br><br>P.S. I could still use help sifting through the open issues on the<br>tracker. If you see any open issues that are important and feasible to<br>fix in the next 7 days, change the target version to "1.4.0 beta 1".<br>If it's less important, or not feasible to do that soon, but still<br>should be done for 1.4, change the target version to "1.4.0 beta 2".<br><br>P.P.S. I patched our Redmine a couple days ago, so only "Team Members"<br>and "Contributors" (as the issue tracker thinks) can change the target<br>version. If you want to help us sort the issues, but it won't let you<br>change the target version, add a comment saying which target version<br>you think the issue should
have.<br>_______________________________________________<br>ImpDev mailing list<br><a ymailto="mailto:ImpDev@lists.imprudenceviewer.org" href="mailto:ImpDev@lists.imprudenceviewer.org">ImpDev@lists.imprudenceviewer.org</a><br><span><a target="_blank" href="http://lists.imprudenceviewer.org/listinfo.cgi/impdev-imprudenceviewer.org">http://lists.imprudenceviewer.org/listinfo.cgi/impdev-imprudenceviewer.org</a></span><br></div></div>
</div></body></html>