<br><br>
<div class="gmail_quote">On Thu, May 21, 2009 at 12:56 PM, Harald Sitter <span dir="ltr"><<a href="mailto:apachelogger@ubuntu.com">apachelogger@ubuntu.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div class="im">On Donnerstag, 21. Mai 2009 01:33:03 Richard JOHNSON wrote:<br>> On Thu, May 21, 2009 at 01:20:29AM +0200, Harald Sitter wrote:<br></div>
<div class="im">> > Also, that kind of stuff should probably be done over at KDE, Kubuntu, at<br>> > most, can do a second run every once in a while to ensure that Kubuntu<br>> > specific patches don't cause regressions.<br>
><br>> I think that once we get settled into a release we would go for the<br>> automated testing and really get into the regression testing. We should at<br>> least make sure right now that packages build and install correctly,<br>
> because we don't need more grumpy developers, I think I am all you can<br>> handle :p<br><br></div>True :P<br>
<div class="im"><br>> > Nope, this will be done based on debs built in $PPA (or eventually as<br>> > provided by the developer). In any case the server will also do automatic<br>> > uploading of packages if a new revision was pushed, so it probably makes<br>
> > sense to just check for newly built debs and compare it's content to an<br>> > established database of previous versions.<br>><br>> So we will in essence have 2 buildd's? We will push to this server which<br>
> will do some testing, and then if all goes well it will go to the PPA?<br><br></div>Nah, the server just acts as proxy creating the source packages by merging it<br>with the branch and pushing that to the PPA. Then it grabs the deb (assuming<br>
it built, if not we get spam from soyuz anyway) and does the testing.<br>
<div>
<div></div>
<div class="h5"><br><br>--<br>kubuntu-devel mailing list<br><a href="mailto:kubuntu-devel@lists.ubuntu.com">kubuntu-devel@lists.ubuntu.com</a><br>Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel" target="_blank">https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel</a><br>
</div></div></blockquote></div>
<div><br>However we do this in the future it would nice to make sure the packages are able to be installed before announcing it in such a global way such as <a href="http://kubuntu.org">kubuntu.org</a>. I would have loved to test this in my Jaunty VM and provide the updates/feedback to the list before we release it to the wild.</div>
<div>Now I am going to be reloading my laptop when i get back from vacation. Currently the screen does not display in a way I can read the text, network manager is dropping all the time the hotel wireless (my windows 7 system maintains the link so its not the link thats the problem) and numerous other issues.</div>
<div> </div>
<div>whether we automate it or not, future3 updates should be announced first to kubujntu-devel for testing then an announcement to the rest of the world once that testing is done</div>