#3607 cannot move from testing to stable
Closed: Invalid None Opened 14 years ago by mcrha.

I have made a build update for F13 like usually, few packages in one update,
https://admin.fedoraproject.org/updates/evolution-mapi-0.30.0-1.fc13,evolution-exchange-2.30.0-1.fc13,evolution-2.30.0-1.fc13,evolution-data-server-2.30.0-1.fc13,gtkhtml3-3.30.0-1.fc13?_csrf_token=1500add7675aa074f38a3fcbc7564e8aa423cf35

My problem is that I usually was able to move things from testing to stale by clicking something in the above url, but I do not see there that option now, for some reason. I see there only "Unpush" and "Edit", but beside these used to be something like "Move to stable", which I used to use on other builds earlier.

Am I doing anything wrong or you did?


it's marked critical-path, so I think that means it requires at least one +1 karma from a proventester (which it apparently hasn't received yet).

Is it necessary? I know I built it, I added it to admins, and it's all mine, but I only can either take it off, or change details, which is pretty strange to me. I want to be able to do anything I want to updates I did.

What is the proper type for the usual update between versions, on an upstream release? I confess I do not understand them, none fits to "the upstream release" update. I'll be glad to use the right one. I see I marked it as "bugfix update", same as most of other build I did in the past, except the previous one for F13, which I marked as new-page type.

Who did mark this a critical path? I do not remember doing so, neither with the previous builds, where I was able to push to stable.

The package itself is critical path, regardless of the update type. https://fedoraproject.org/wiki/Critical_Path_Packages

OK, so should I just disable karma next time, to be able to influence when the packages will be moved to stable? And as I said, this used to work properly earlier, just now it isn't working as I expect.

You can't force a critpath package to go into stable until it gets appropriate karma, that's the point of critical path, karma is /required/.

The whole new behaviour (note I was able to push to stable myself few weeks ago) doesn't make any sense to me. Imagine we have a new update from upstream, which is fixing some serious issue, which is not shown for the "proven testers". Does the rest of the world have just bad luck because of this strange policy? Note I'm not just building and posting to stable, I keep it in testing for about a week, and when nothing serious arises, then I'm pushing to stable (I used to push to stable). Also, there are about 508 packages listed in branched-20100414/logs/critpath.txt, do you really expect those "proven testers" to hunt and comment on each update for each package from there? I agree that some QA testing is needed, just this seems to me like too much.

Please don't shoot the messenger (rel-eng). Feedback on related policy should be taken to FESCo.

hehe, do not worry, I'm not going to shoot anyone, I just hope my thoughts about this are small arguments why such a decision can be wrong. But, of course, I can be wrong too. Nonetheless, I understand I do not talk to the right group, which I thought I do at the beginning. Thanks for the explanation.

Are you maintaining the updates [at] fedoraproject [dot] org? I was just spammed by it with a very nice text which I would like to share with you. Guess what's wrong with it:

Subject: [Fedora Update] [CRITPATH] [old_testing] evolution-mapi-0.30.0-1.fc13, evolution-exchange-2.30.0-1.fc13, evolution-2.30.0-1.fc13, evolution-data-server-2.30.0-1.fc13, gtkhtml3-3.30.0-1.fc13

The update for evolution-mapi-0.30.0-1.fc13,evolution-exchange-2.30.0-1.fc13,evolution-2.30.0-1.fc13,evolution-data-server-2.30.0-1.fc13,gtkhtml3-3.30.0-1.fc13 has been in 'testing' status for over 2 weeks.
This update can be marked as stable after it achieves a karma of 3
or by clicking 'Push to Stable'.

This is just a courtesy nagmail. Updates may reside in the testing repository
for more than 2 weeks if you deem it necessary.

You can submit this update to be pushed to the stable repository by going to
the following URL:

https://admin.fedoraproject.org/updates/request/stable/evolution-mapi-0.30.0-1.fc13,evolution-exchange-2.30.0-1.fc13,evolution-2.30.0-1.fc13,evolution-data-server-2.30.0-1.fc13,gtkhtml3-3.30.0-1.fc13

or by running the following command with the bodhi-client:

bodhi -R stable evolution-mapi-0.30.0-1.fc13,evolution-exchange-2.30.0-1.fc13,evolution-2.30.0-1.fc13,evolution-data-server-2.30.0-1.fc13,gtkhtml3-3.30.0-1.fc13

================================================================================
evolution-mapi-0.30.0-1.fc13, evolution-exchange-2.30.0-1.fc13,
evolution-2.30.0-1.fc13, evolution-data-server-2.30.0-1.fc13,
gtkhtml3-3.30.0-1.fc13
================================================================================
Update ID: FEDORA-2010-5695
Release: Fedora 13
Status: testing
Type: bugfix
Karma: 3
...

Login to comment on this ticket.

Metadata