The Following 19 Users Say Thank You to timoph For This Useful Post: | ||
|
2012-04-04
, 10:02
|
|
Posts: 738 |
Thanked: 983 times |
Joined on Apr 2010
@ London
|
#2
|
The Following 8 Users Say Thank You to erendorn For This Useful Post: | ||
|
2012-04-04
, 10:06
|
Posts: 1,397 |
Thanked: 2,126 times |
Joined on Nov 2009
@ Dublin, Ireland
|
#3
|
|
2012-04-04
, 10:49
|
Posts: 415 |
Thanked: 732 times |
Joined on Jan 2009
@ Finland
|
#4
|
The problem with blocked packages was discussed in this thread.
There was also further discussion in the testing squad mailing list.
We asked to Nemein to arrange any kind of meeting to try to address the problems and discuss our proposals and see how could them be feasible. You can see that in the mailing list thread.
No answer was received. No I have asked to Quim twice to see if he can help us to approach the administrators in order to fix the issues.
The Following 4 Users Say Thank You to timoph For This Useful Post: | ||
|
2012-04-04
, 12:26
|
Posts: 1,513 |
Thanked: 2,248 times |
Joined on Mar 2006
@ US
|
#5
|
As a long term solution I'd like to see a fremantle target in OBS (apps.formeego.org). This would solve most of the problems (except the lack of testers). But this is also something that needs help from the maintainers. On the other hand this might turn out to be a waste of time since many of the fremantle packages are orphaned and would require work to move stuff into OBS. In the end of the day it comes down to how many peolpe are left that are willing to do work for fremantle stuff. This might phase out just like the older maemo devices did with only a couple of people interested in them. If that's the case it's not worth the effort.
The Following 8 Users Say Thank You to SD69 For This Useful Post: | ||
|
2012-04-04
, 12:56
|
Posts: 415 |
Thanked: 732 times |
Joined on Jan 2009
@ Finland
|
#6
|
There is an IRC chat meeting about community OBS on April 10 where any interested party should speak up. If we want to pursue fremantle as a target on OBS, then we need to decide that soon, and how we obtain that goal.
The Following User Says Thank You to timoph For This Useful Post: | ||
|
2012-04-04
, 13:34
|
Posts: 152 |
Thanked: 620 times |
Joined on Mar 2008
@ Netherlands
|
#7
|
One of the problems is the community QA queue that has been stuck for ages (oldest packages are about a year old). I quickly went through the list yesterday and the situation seems to be (please correct me if I'm wrong) caused by multiple factors: 1) lack of testers 2) lack of automated promotion system 3) communication problems. The combination of the problems makes the community QA pretty much a waste of time.
Personally I'd start with something we can do without paid help as in go though the packages that can be promoted (do what the community QA is supposed to do) all clean the queue. After this it gets a bit more difficult without help from people maintaining the infra. But if we provide them a list of actions needed for each of the packages stuck in the queue instead of demanding root access this thing just might get solved. In any case the problem won't go away just be talking.
As a long term solution I'd like to see a fremantle target in OBS (apps.formeego.org). This would solve most of the problems (except the lack of testers). But this is also something that needs help from the maintainers. On the other hand this might turn out to be a waste of time since many of the fremantle packages are orphaned and would require work to move stuff into OBS. In the end of the day it comes down to how many peolpe are left that are willing to do work for fremantle stuff. This might phase out just like the older maemo devices did with only a couple of people interested in them. If that's the case it's not worth the effort.
The Following 15 Users Say Thank You to X-Fade For This Useful Post: | ||
Andre Klapper, anidel, don_falcone, fw190, Helmuth, Jaffa, MartinK, OVK, pycage, qgil, rcolistete, Reggie, sjgadsby, Texrat, timoph |
|
2012-04-04
, 14:25
|
|
Posts: 2,535 |
Thanked: 6,681 times |
Joined on Mar 2008
@ UK
|
#8
|
There is an IRC chat meeting about community OBS on April 10 where any interested party should speak up. If we want to pursue fremantle as a target on OBS, then we need to decide that soon, and how we obtain that goal.
|
2012-04-04
, 14:27
|
Posts: 1,397 |
Thanked: 2,126 times |
Joined on Nov 2009
@ Dublin, Ireland
|
#9
|
|
2012-04-04
, 14:41
|
Posts: 415 |
Thanked: 732 times |
Joined on Jan 2009
@ Finland
|
#10
|
Cleanup can be done by the supertesters now already. If you have 2 thumbs down by supertesters, the package is removed.
Same thing for promoting. A QA triage meeting like done in the past would already make a lot of difference there.
.
One of the problems is the community QA queue that has been stuck for ages (oldest packages are about a year old). I quickly went through the list yesterday and the situation seems to be (please correct me if I'm wrong) caused by multiple factors: 1) lack of testers 2) lack of automated promotion system 3) communication problems. The combination of the problems makes the community QA pretty much a waste of time.
Personally I'd start with something we can do without paid help as in go though the packages that can be promoted (do what the community QA is supposed to do) all clean the queue. After this it gets a bit more difficult without help from people maintaining the infra. But if we provide them a list of actions needed for each of the packages stuck in the queue instead of demanding root access this thing just might get solved. In any case the problem won't go away just be talking.
As a long term solution I'd like to see a fremantle target in OBS (apps.formeego.org). This would solve most of the problems (except the lack of testers). But this is also something that needs help from the maintainers. On the other hand this might turn out to be a waste of time since many of the fremantle packages are orphaned and would require work to move stuff into OBS. In the end of the day it comes down to how many peolpe are left that are willing to do work for fremantle stuff. This might phase out just like the older maemo devices did with only a couple of people interested in them. If that's the case it's not worth the effort.
One solution is simply to trash the community QA process by letting extas rot in peace and only use extras-devel and -testing where testing would the "stable" repo. this is the way out if it's not possible to get the automated promotion system, etc. working. This would be the solution requiring least work and pretty much already is the current practice.
As I said in the mainling list I'm volunteering myself to be one of the people who goes through the QA queue. I'd like to see at least a two more people doing the same. These decisions can't be made by a single person and it doesn't make sense to much before we get people to commit to put some effort into some solution. Also it would help in making the call to get an answer to what people maintainging the infra are planning/allowed to do.
So what do you say? Do we try to resurrect the community QA process, trash it or do something else?