[Pidgin] #3123: Design the ChangeLog

[Pidgin]

#3123: Design the ChangeLog
--------------------------+-------------------------------------------------
  Reporter:  ronofir      |       Owner:  kstange        
      Type:  enhancement  |      Status:  new            
  Priority:  minor        |   Milestone:  Patches welcome
 Component:  webpage      |     Version:                 
Resolution:               |    Keywords:                 
   Pending:  0            |  
--------------------------+-------------------------------------------------
Comment (by kstange):

 My point is there's no reason to push the data into MySQL just to pull it
 back out again linearly.  That's not really cheaper than running a script
 on the whole text file, because, as Luke points out, it would require
 running MySQL in the first place.

 Rather than do that, the lines processed by script 1 could simply be
 converted directly to HTML and output to a file, with the appropriate
 header and footer attached.  Then, we'd have a "static" ChangeLog file
 that doesn't need to be completely rebuilt from a DB (regardless of
 whether that's every time it's loaded or once per release).  The text
 processing won't take more than a few seconds, even on a large file, so
 reprocessing the whole file for each release is not unreasonable, and
 eliminates the need for script 2 and script 3.

 What reasoning were you thinking to justify using a database?

-- 
Ticket URL: <http://developer.pidgin.im/ticket/3123#comment:10>
Pidgin <http://pidgin.im>
Pidgin