<br><div class="gmail_quote">On Fri, Apr 25, 2008 at 7:50 AM, Stefan Potyra <<a href="mailto:stefan.potyra@informatik.uni-erlangen.de">stefan.potyra@informatik.uni-erlangen.de</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi folks,<br>
<br>
now that hardy is out, and intrepid is still closed, it would be a perfect<br>
time to get going with SRUs for hardy.<br>
<br>
Currently, SRU's [1] have the requirement to be fixed in the development<br>
version first. The main use for this is, to not introduce regressions by<br>
forgetting to fix the development version. Of course we cannot do this right<br>
now.<br>
<br>
So here's my straw-man's plan to get going: Fix stuff in SRU's and drop the<br>
current requirement to have intrepid fixed first, until intrepid actually<br>
opens. Tag each upgrade, which gets accepted by the SRU team<br>
with "needs-fix-intrepid", so that we can later apply the fix for intrepid as<br>
well.<br>
<br>
What do you think? More important, motu-sru: is that OK for you?<br></blockquote></div><br>Sound great. +1 from me. One possible question would be if we should go a bit beyond just opening of Intrepid. Often the archives are generally ready for large scale work for a few weeks after the archives are open, like after UDS.<br>
<br>-Jordan<br>