Hi,
João already replied to correct any misunderstandings and (hopefully)
settle the argument here. As for the underlying reasons of the packaging
issues, I believe a major culprit here is the rather fast release
cadence during our beta period: I insisted on it on the grounds that it
makes controlling regressions easier, we get code and bugfixes to the
developers sooner, it fits our two-week scrum sprints well, and making
successive releases is easier if the amount of changes between them is
smaller (especially now that we have a buildbot infrastructure for
multiple platforms in place). So, I am to blame for that.
I still think the two-week release cycle has helped solve some of our
problems, but it also has brought major issues. Doing all the
integration work (which is a huge amount of work -- we're taking the
same hit in our internal releases) for every beta (or even skipping
some) is a major undertaking, especially for volunteers. Nevertheless,
I'd like to keep the current cadence until we have released 1.0, and
then ease down a bit.
Although the working model of the core dev team doing only source code
releases and relying on the rest of the community for the binary
packaging has worked pretty well, we'd of course like to help deal with
any issues. Didier, if you have suggestions how we could help you, let
us know. (The same goes to Roman and other packages as well, of course.)
One thing that might have become feasible is that we could do fully
automated daily releases using the buildbot setup. These wouldn't of
course be a substitute for proper releases, of course, but that would
provide a way for the early adopters to grab the packages and get
working, while waiting for the proper release packages. I'm not sure
about the extra work required for this, and it might still be easier to
carry on as usual until the issue gets resolved by itself after the 1.0
release. What do you think?
Cheers,
ma.
On 17.01.2011 23:32, ext Didier 'OdyX' Raboud wrote:
(I am the PySide PPA maintainer as well as the Debian and Ubuntu maintainer
of the PySide stack)
João Ventura wrote:
Hello,
the same thing happened to me, and i can't seem to work it out. I'm
using ubuntu 10.10 and pyside 1.0~beta1 (because the ppa doesn't seem
to update to beta3), and since today the error occurs on "import
PySide".
Hi João,
"the ppa doesn't seem to update" sounds very funny: "updating to ~beta3" is
not automagical: it implies a certain time of work and compilation. As I
don't update the PPA with a possibly broken PySide, it takes at least 2
compilations of it before the actual release and some actual packaging work.
And I am doing this for 3 Ubuntu releases as well as for Debian.
I'm doing this on my free time, which happens to be limited these days.
Last friday, it all worked fine, so it has to do with any ubuntu
update i have done this weekend.
It's not a Ubuntu update you did; you updated from a PPA, which is far from
being the same: a PPA is not part of the Ubuntu distribution. AFAICS the
PySide version from Ubuntu Maverick works correctly.
When will this be ok? I've just lost today a day of work on this..
Feel free to contract me to do the job faster; otherwise I'll continue to do
this on a best-effort basis, during my free time.
Btw, when will ubuntu ppa be updated to beta3?
Before the end of the week, hopefully.
Thanks,
João Ventura
Although my mail might sound rude, I really feel offended by the tone of
yours. But I acknowledge that the process is not perfect: it might be
possible to wait on PySide being ready to upload before uploading Shiboken,
but it's more complicated for me.
And again, please note that I (as the PPA maintainer) am not reponsible for
disappearing symbols: this is a responsability of PySide upstream and
altough I am mildly annoyed by this fact, this is also normal during "beta"
releases, which you still use despite this "beta" state.
So please refrain from accusing (me in that case) people for work days lost
(in particular when you are using beta free software): it only helps in
taking away people's motivation.
Respectfully,
OdyX
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
_______________________________________________
PySide mailing list
[email protected]
http://lists.openbossa.org/listinfo/pyside
