Hi everyone,<br><br>Today marks the beginning of the next biweekly development cycle (June 28-July 9).<br><br>To kick off each cycle, we would normally have a discussion at ~10:30am CST on the applicable Monday. However, we missed last cycle (June 14-25) since I was out of the office. And since Aivar and Brian are away today, we will instead meet tomorrow to discuss goals for this cycle.<br>
<br>If you have open tickets, please update them with your progress, closing any tickets that have been completed, and adding comments to describe any progress. That way, the Trac preserves an accurate historical record of the work we completed during each development cycle. Some time tomorrow I will close the previous milestone, which will migrate all remaining open tickets into the next milestone.<br>
<br>Grant, Adam & Lee: We'll look for you guys on Skype tomorrow morning. Once everyone involved is online, we can do a conference call to go over our progress over the past two cycles, and goals for this next one.<br>
<br>-Curtis<br><br><div class="gmail_quote">On Thu, May 27, 2010 at 5:20 PM, Curtis Rueden <span dir="ltr"><<a href="mailto:ctrueden@wisc.edu">ctrueden@wisc.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi everyone,<br><br>As discussed during today's status report, I have configured biweekly milestones through the end of the year on the ImageJ Trac. You can view them at:<br> <a href="http://imagejdev.org/trac/imagej/roadmap" target="_blank">http://imagejdev.org/trac/imagej/roadmap</a><br>
<br>Please use these milestones as a todo list over the course of each two-week interval. These milestones will serve as an organizational tool, quick reference and declaration to the community of how we are directing our individual efforts.<br>
<br>Associated tickets (filed by logging in and clicking the "new ticket" button on the top right) need not be complex—just one or two lines to remind yourself of the task. When you can, try to break it down to actual "next physical action" style tasks (see <a href="http://zenhabits.net/why-whats-the-next-action-is-the-most-important-question/" target="_blank">http://zenhabits.net/why-whats-the-next-action-is-the-most-important-question/</a> for a nice article about this), even if you list more than one "next action" on the same ticket sometimes.<br>
<br>Cycles will begin on alternating Mondays (starting this Tuesday, June 1, due to Memorial Day). On these Mondays, we will review our progress on the previous cycle, troubleshoot any roadblocks with existing tickets, push incomplete work into the next cycle, etc. On these Mondays, we can do this instead of our usual "stand-up" meeting. Grant, it would be good if you could join us for these biweekly reviews—we usually meet around 10:30am CST (11:30am CST).<br>
<br>Please let me know if you have any questions about it!<br><font color="#888888"><br>-Curtis<br>
</font></blockquote></div><br>