Author: matakagi Date: Tue Aug 7 04:04:53 2007 New Revision: 889 Log: - merge r811.
Modified: trunk/ja/ch07.xml Modified: trunk/ja/ch07.xml ============================================================================== --- trunk/ja/ch07.xml (original) +++ trunk/ja/ch07.xml Tue Aug 7 04:04:53 2007 @@ -1596,7 +1596,16 @@ subject of which releases the project will be making in the near- to medium-term future, and what features will be in them, without at first mentioning anything about dates, except for rough guesses with -wide margins of error. By nailing down feature sets early, you reduce +wide margins of error<footnote><para>For an alternative approach, you +may wish to read Martin Michlmayr's Ph.D. thesis <citetitle>Quality +Improvement in Volunteer Free and Open Source Software Projects: +Exploring the Impact of Release Management</citetitle> +(<ulink url="http://www.cyrius.com/publications/michlmayr-phd.html"/>). +It is about using time-based release processes, as opposed to +feature-based, in large free software projects. Michlmayr also gave a +talk at Google on the subject, available on Google Video at +<ulink url="http://video.google.com/videoplay?docid=-5503858974016723264"; +/>.</para></footnote>. By nailing down feature sets early, you reduce the complexity of the discussion centered on any individual release, and therefore improve predictability. This also creates a kind of inertial bias against anyone who proposes to expand the definition of _______________________________________________ Producingoss-translators mailing list Producingoss-translators@red-bean.com http://www.red-bean.com/mailman/listinfo/producingoss-translators
