On Mon, 2012-04-16 at 10:33 +0100, Richard Hughes wrote:
...
If you had already updated F17 with the upstream 3.4.1 then
the automatic script would have ignored your package completely.
Hey,
I didn't have much time to do so. You script stepped in only two hours
after release on Gnome's ftp. It's not so bad, but still early and
unexpected for me.
There's no way for me to know the difference between
"maintainer not
doing update because he's busy" and "maintainer wants to handle this
himself in his own time".
Maybe he's just _currently_ busy, sleeping (consider different
timezones) and so on? Anyway, I never asked to have those packages part
of the auto-build list, and never was asked for acceptance. This is
easily distinguishable, isn't it?
Now you've told me in a not-so-polite way
I'll just take off evolution from the auto-build list.
evolution*, please.
> I've no idea what it means in reality. Say I'll not add
my build ids
> into your google page, am I still responsible for filling update of my
> packages?
Yes, if you want to be, although I think we should aim to have one
easy-to-qa update for micro-point updates of a single desktop
environment, rather than the huge number of updates we had before that
were *impossible* to QA [1]. Is there a reason evolution is so special
that it shouldn't be considered a core GNOME package that gets
released with everything else?
I cannot answer this objectively now, I'm sorry. There is certainly
nothing extra special about those packages, apart of your auto-build
script not being able to build those packages correctly (which it cannot
do in general anyway), but I currently have bad feelings about this
process, so, well, let me think about it.
Bye,
Milan