"Noah Kantrowitz" <[email protected]> writes: > Different plugin authors do things differently. For my stuffs, I only keep > one branch per Trac major version. I don't seem much value in ever > installing anything other than the most recent version of a plugin. Version > numbers are provided for human convenience mostly, though if the same plugin > is installed twice, the higher version copy will be used automatically. > Again this changes author to author, but I generally only rev mine after a > major change of somesort, so that when people ask for help I can use that to > know if they have a certain fix or need to upgrade.
Thanks. I don't see any value in old versions either; it's just that having distfiles identified by version is used by packaging systems and it seems plugin culture is different. I will see about using the svn support with a particular revision number. >> Also, after installing a plugin I got an error saying I needed to do >> trac-admin upgrade. I did and then all was well, but I didn't expect >> this from the plugin docs at http://trac.edgewall.org/wiki/TracPlugins. > > The upgrade system is an extension point like any other. In the case of > mastertickets, it needs to add a new database table. OK, that makes sense. Perhaps would be good to note this on the plugin page.
pgpz5u2Eko7U5.pgp
Description: PGP signature
