Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.32.0

Request #10624 Generated package.xml mis-orders releases.
Submitted: 2007-04-05 10:18 UTC
From: cipri Assigned: cellog
Status: Closed Package: pearweb
PHP Version: Irrelevant OS: Irrelevant
Roadmaps: 1.15.1    
Subscription  
Comments Add Comment Add patch


Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem : 27 + 27 = ?

 
 [2007-04-05 10:18 UTC] cipri (Cipriano Groenendal)
Description: ------------ As can be seen on http://pear.php.net/bugs/roadmap.php?package=Mail_Mime&packagexml=1&roadmap=1.4.0a2 the automatic package.xml generator doesn't order the releases in the package.xml. This gets quite confusing as many developers use a diferent order to place these old releases in. It would be better if they were automaticly sorted into the right order when needed.

Comments

 [2007-04-05 19:04 UTC] cellog (Greg Beaver)
it doesn't mis-order, it just appends the changelog entry to the end of the changelog. The ordering of changelog is a personal preference, I like to put the most recent at the file end so that to see what is new, I just go to the end of the file (end key with less, or Ctrl-PgDn in my IDE). You like to put it closest to the <contents>. However, I think being smart enough to determine where to put the most recent changelog would be nice. This can be done with some help from PEAR_PFM, there's a bit of code I wrote in that to order the changelog, by snagging that code and then adding auto-detection of preferred order, we can preserve that for you weirdos who do it the opposite of my way ;).
 [2007-05-06 21:46 UTC] cellog (Greg Beaver)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.