<br><br><div><span class="gmail_quote">On 9/9/05, <b class="gmail_sendername">Martin Meredith</b> <<a href="mailto:martin@sourceguru.net">martin@sourceguru.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I completely agree with what Johnsays, and according to what Matt said<br>when I briefly spoke to him... Breezy backports form Breezy +1<br>infrastructure should be available around same time as breezy +1 uploads..</blockquote>
<div><br>
Ok, excellent to know. <br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">With the point of breezy backports though - I'd like to see it go<br>official only, because having 2 different places for backports is
<br>confusing, and time consuming... Obviously, there will still be<br>breezy-extras on the "unofficial" servers (which - top be quite honest,<br>I probbaly wouldn't be able to cope without), but - I'd like to see it
<br>all in one place, not all over the place...</blockquote><div><br>
Naturally, breezy-extras will start on Breezy's release date, and will be hosted on the old Backports server.<br>
<br>
In addition, Breezy Backports Staging will also have to be hosted
there, unless the official infrastructure for binary copies gets put
into place. I think I've already established the need for a live
testing APT tree in previous e-mails and meeting(s).<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Also, I'd like to see (even though it's going to be hard) hoary<br>backports continue... as, as we know, some people are still on warty,
<br>and while they may not be many, it's nice to let them have updates too<br>... same goes for hoary :D</blockquote><div><br>
I'd love to see that, too, but our current infrastructure has issues
with that. Currently, we use ~hoary1 and ~breezy1 for Backports
package names. This means that package 'foo-1.0-6ubuntu6~hoary1'
actually registers as NEWER than 'foo-1.0-6ubuntu6~breezy1' because H
comes after B. The old 4.10/5.04/5.10 trailers don't suffer from this
problem though :). Some packages will certainly stay unchanged for that
period of time, which is unfortunate.... I'd hate to have to force an
upstream xubuntuy bump, but that may be necessary if we want to do
parallel backporting for different releases.<br>
<br>
The other solution would be to switch back to numeric version trailers.<br>
<br>
<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Anyways... those are my thoughts... :D<br><br>John Dong wrote:<br>> We're about a month (a bit more) away from Breezy's release, which is
<br>> approximately when I stopped Warty Backports to concentrate on<br>> infrastructure changes (and also channel some enthusiasts to beta<br>> testing). I'm thinking we should do the same about now. Virtually<br>
> everything important in Hoary has been backported and is fairly up-to-date.<br>><br>><br>> While we're on the subject of infrastructure, I think official Backports<br>> is working out very well. Thanks, James & others for building the
<br>> packages for us, and thanks, Martin for stepping up to the plate for<br>> communications & relations. With my busy schedule, I couldn't do it<br>> without you guys! The only thing I'd like to bring some attention to is
<br>> a "staging" area...<br>><br>><br>> Matt, you once alluded (at the end of the Backports meeting) to plans<br>> for implementing binary copies, the equivalent of our -staging tree.<br>> Does that appear like it'd happen by the end of October? That'd be great
<br>> to have, since we don't have the resources to build packages for all<br>> architectures for testing. We've seen cases (nvu is a good example)<br>> where a package works fine on one architecture but crashes on another.
<br>> Without a testing repository, it's difficult to find these things out<br>> before they contaminate our stable tree.<br>><br>><br>> Also, to developers (forward to the appropriate contact): Can we get<br>
> breezy-backports lines in Breezy's default sources.list, only commented<br>> out with a disclaimer (sort of like how Universe is there)? That way,<br>> users can simply check a checkbox to activate Backports instead of using
<br>> text editors and cut & pasting long URL's.<br>><br>><br>><br>> Other than that, I think Backports is top-notch now. Together, we've<br>> made a great distribution even better by offering high-quality version
<br>> updates with minimal stability problems.<br>><br><br><br><br>--<br>ubuntu-backports mailing list<br><a href="mailto:ubuntu-backports@lists.ubuntu.com">ubuntu-backports@lists.ubuntu.com</a><br><a href="http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports">
http://lists.ubuntu.com/mailman/listinfo/ubuntu-backports</a><br><br><br><br></blockquote></div><br>