On Mon, Dec 13, 2010 at 9:54 PM, Felipe Crochik <span dir="ltr"><<a href="mailto:felipe@crochik.com">felipe@crochik.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Having the experimental packages break from time to time is a small price to<br>
pay for being able to develop with the latest and greatest. Any user willing<br>
to TEST the applications under extras-devel/extras-testing should also be OK<br>
with a surprise now and then. It also should benefit the Trolls to have<br></blockquote><div><br>I agree for extras-devel completely, but testing is a bit of a mystery to me in this context. You push to testing, people test, get it tested and... then what ? Extras should by definition not contain/force on people untested stuff with known breakage potential. That is not mean that we cannot change definitions, just saying that we have to be clear about that :)<br>
<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Who is in charge of the qt experimental? What is the current "schedule" for<br>
it? How much the council and community in general can be involved?<br>
Last but not least: Anything I can do to help?<br><br></blockquote><div><br>Try talking to harryF on #qt-maemo, he was looking for a maintainer. Currently there is a slight vacuum - unlike the previous jump with QML, 4.7 updates are not significantly different from the one in the PR to warrant anyone from linking to it, and the the to-be-4.8 has no high-profile new features available for devs yet. As for what happens in extras(-devel) with the new versions, it's certainly a community coordinated effort and AIUI the Council has a large (pretty much final) word on that. As you yourself said it, it's in everybody's interest to have the latest & greatest Qt stuff available not just as gitoriousware, but in an easily testable dev-friendly binary form, too. <br>
</div></div><br>