On Tue, Jan 13, 2009 at 12:06 PM, Jonas Smedegaard <span dir="ltr"><<a href="mailto:dr@jones.dk">dr@jones.dk</a>></span> wrote:<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Or do you propose that we, if following only a single branch, follow the<br>
newest upstream branch no matter if that is stable or unstable?<br>
</div></blockquote><div class="Ih2E3d"><br>I think at that point sugar is "stable enough" for Debian unstable/testing, assuming we are able to package an even release number by the time testing becomes the new stable.<br>
<br><br><br><br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">Hint: Look first at self-contained activities!<br>
<br>
Example: Write is complex, as it depends on libabiword.</div></blockquote><div><br>Understood. <br></div></div><br>-- <br>Luke Faraone<br><a href="http://luke.faraone.cc">http://luke.faraone.cc</a><br>