Re: Re: Statistics for too long unstable packages

On Tue, 14 Nov 2006 09:48:45 +0100, Mark Wiesemann wrote: > Christian Weiske wrote: >>>>> I doubt that the last release of DB_Table was "36 years, 5 weeks" >>>>> ago. >>>> That's because the package.xml doesn't specify the last release >>>> correctly. >>> Can you please explain what's wrong? >>> >>> If I could package and release the last release, how can it be wrong >>> then? >> I don't know what people do when releasing a package; I do change the >> package.xml and put the current version into CVS. >> >> Look at the file: >> >> http://cvs.php.net/viewvc.cgi/pear/DB_Table/package2.xml?view=markup >> Date and Time do have a question mark in them. > > Ah sorry, didn't remember that there was a change after the last > release. And if I alter something, I reset date and time values because > I don't know the exact date for the next release. People using PFM might > don't do that because they update the XML file only directly before a > release, but I (not using PFM) like it for clarity this way. > > For your statistics it is a problem, of course. A solution might be to > download the last tagged version from CVS. Don't know how expensive this > would be and whether everybody tags his releases. Great work Christian but what Mark is doing is done by a lot of developers (well a fair share) that don't use PFM, apparently I can't access cvs.php.net at the moment so I can't point to any particular package (iirc we do this in the Validate packages, Cache and more). But aren't you basically querying for info you can get via the REST interface ? I'm pretty sure you can get last release info on each package via their REST info (same interface the installer is using), that of course means some network traffic but since you anyway would have to do a cvs checkout or similar then that's okey I think plus not all package are in the php cvs of course :/ Maybe a combo of both things could be interesting for QA ... check the last release time + last commit time so QA can quickly see if there has been any activity in the CVS (This idea is actually something we pondered way back on IRC but never came to live, so it would be cool to see you do it :D) Biggest problem with this is to gather the cvs/svn anon checkouts for different projects that don't host at the php.net server but it's doable :-) - Helgi -- There are no stupid questions, only stupid people