On Wed, 3 Oct 2012, Roberto Longobardi wrote:
My difficulties are mainly tied to the new database API and trying to support with just one codebase the 0.11, 0.12 and 1.0 releases.
Actually from my point of view that is wasted time - Simply use new features when required.
For spam-filter I constantly move to the newest version whenever I need a new feature, otherwise stick by the older one. I only develop the newest one. If there appears to be a major bug in old code and users request it, I probably would release a bug fix, but till now that was never requested.
Whoever wants to use newer version of your plugin needs to upgrade Trac. I see no harm in that. I use that mechanism for other software as well and it works well as long as the releases are stable, which is true for Trac.
Systems still running a 0.11 version probably also don't upgrade plugins at all, as upgrading plugins can be as dangerous as upgrading core (which is BTW very smooth - no real issues for me since first 0.11 version).
P.S. One of the ways to split code is to use "svn copy" into a new directory like "0.11".
Ciao -- http://www.dstoecker.eu/ (PGP key available) -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
