<div>I don't mind if the change log isn't stored in the ini, no big deal really. Was just throwing it out there.</div><div><br></div>In the end it wouldn't be that hard for the web app to look for a CHANGELOG file and read that in. In the end we just have to set something up with easy to use and follow conventions so that it makes the plugins consistent. Convention over configuration. <div>
<br></div><div>- Nathan<br><br><div class="gmail_quote">On Thu, Nov 10, 2011 at 6:56 PM, Alessandro Pasotti <span dir="ltr"><<a href="mailto:apasotti@gmail.com">apasotti@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2011/11/10 Sandro Santilli <<a href="mailto:strk@keybit.net">strk@keybit.net</a>>:<br>
<div class="im">> On Thu, Nov 10, 2011 at 05:55:06PM +1000, Nathan Woodrow wrote:<br>
>> Yeah. It would be easier from a developer point of view. I can just stick<br>
>> my change log in there and the web app just reads it in saving me the time<br>
>> to have to fill it out plus then when you download it you have a central<br>
>> place to look for the change log.<br>
><br>
> Mind you: a change log grow rate sounds pretty different from a<br>
> configuration directive list grow rate.<br>
> Your changelog might get huge...<br>
> How about using a different file for that ?<br>
<br>
</div>I think the idea is to only store changes from the previous version,<br>
each version is stored separately on the plugins app.<br>
<br>
BTW I'm also concerned about storing potentially huge text blobs<br>
inside an ini file.<br>
<br>
I'm not very skilled with that format, is that ok for large text blobs<br>
? I thought it was best suited for kwp.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
--<br>
Alessandro Pasotti<br>
w3: <a href="http://www.itopen.it" target="_blank">www.itopen.it</a><br>
</div></div></blockquote></div><br></div>