Yeah. It would be easier from a developer point of view. I can just stick my change log in there and the web app just reads it in saving me the time to have to fill it out plus then when you download it you have a central place to look for the change log.<div>
<br></div><div>- Nathan<br><br><div class="gmail_quote">On Thu, Nov 10, 2011 at 5:49 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/9 Nathan Woodrow <<a href="mailto:madmanwoo@gmail.com">madmanwoo@gmail.com</a>>:<br>
<div><div class="h5">>>>dependencies may be external python modules, other qgis python<br>
>>>plugins, maybe something more...<br>
> It would be good to also put a change set list some where, sometimes it's<br>
> nice to see what has changed between a version of a plugin. The plugin<br>
> website could read this and then that would flow down to the plugin<br>
> installer.<br>
<br>
</div></div>Hi Nathan,<br>
<br>
there is already a (not mandatory) changelog text input box available<br>
when you upload a new revision of an existing plugin in the new web<br>
app.<br>
<br>
Are you suggesting to put this piece of information in the metadata text file ?<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>