update version info and release a package?

[Leonardo Rochael Almeida]

AnnouncerPlugin has had a few fixes recently, but its setup.py still pegs the version at 0.2, while the installation instructions for it point to an svn repository that ends at 0.11.

I humbly suggest the repo be organized into trunk and tags, and proper tags be made for different versions. Specifically, I'd like there to be a 0.3 tag with the recently merged e-mail fixes and an updated version in setup.py.

Of course, the easy_install instructions at AnnouncerPlugin will then have to be updated, but at least it will be clear there is a new version available, and the resulting egg in site-packages will be named differently.

[anonymous]

not sure why you would ever want to use the older version.

[anonymous]

when announcer plugin is modified to support a newer version of trac, and backward compatibility breaks, then I will create a new release

[Robert Corsaro]

(In [7142]) trunk boiy - maybe I should stop breaking ppls shit fixes #3578

[Steffen Hoffmann]

(In [12224]) TracAnnouncer: Extend changelog with plugin history for better overview, refs #3578.

This is rather complicated due to branching without version syncronisation.

I draw the conclusion, that moving to an unambiguous version number requires overpowering 1.0-a1, so I'm pushing up to the lowest satisfying number now. announcer-1.0 will support any Trac release down to and including 0.11, if feasible at all, so the match with Trac-1.0 is rather incidential this time.