I wish to try to understand why some package updates seem to appear quite quickly (in testing or main repo section) after a packager has updated them and sent them 'to dropbox', while other packages seem to linger in some limbo for a variable length of time.
A similar situation appears to apply to some new packages ..... some appearing quite quickly after being packaged and others not.
To illustrate what I mean I will take two examples ..... and I choose these two only because I have personal use for the packages and for no other reason ....
XBMC Ver 12, updating from Ver 11.
Usually updates take a few days after packaging, to appear in the public mirrors, being (I understand) sent to PASS repo first.
The update was sent 'to dropbox' on or before the 3rd Feb ...... 9 days ago.http://www.pclinuxos.com/forum/index.php/topic,112826.msg964342.html#msg964342
Guvcview ....... the updated package was being tested in September 2012 ...... apparently the repo version was never updated ..... and it was again submitted 'to dropbox' on 6th Febhttp://www.pclinuxos.com/forum/index.php/topic,109623.msg965007.html#msg965007
As of this morning here, neither of the above updated packages has appeared in the public mirror.
I don't know what question to ask ...... I am just trying to understand what happens that causes some packages to be delayed .... or maybe forgotten about ..... or whatever .....
In addition, maybe someone can let me know what determines if a package goes from 'dropbox' to testing (which is not on PASS I understand) or directly to a main section.
Are packages with small incremental updates treated differently to a package with a major update?
I feel sure it can be rather frustrating for someone who has requested a package, and had that package picked up by a willing packager, completed and sent 'to dropbox', and then not see it appear for a considerable time.
An explanation of the process and the criteria for decisions might help understanding of the difficulties being met.