On Tue, Mar 14, 2017 at 12:43 PM, Roger Oberholtzer <[email protected]> wrote: > On Fri, Mar 10, 2017 at 6:04 PM, RjOllos <[email protected]> wrote: > >> Speaking of that, trac-hacks.org would greatly benefit from volunteers >> spending time to test plugins and tag the projects with the compatible Trac >> version, particularly for Trac 1.2, and opening tickets for issues found. I >> may have sent an email to the list about this some time (years?) ago. If >> anyone was willing to put some effort towards this and needed help setting >> up an environment to do the testing I could help with that, either directly >> or through a writeup of the steps involved. > > How should the tag be done? In tickets one can tell the Trac release. > But that must be for that ticket. Where is it set as a compatibility > property?
Ok. I see that it is just a tag on the wiki page. 'anyrelease' seems potentially confusing. I guess the idea is that if it is tagged 'anyrelease' then a specific release is not needed. Should the specific release tags be removed if 'anyrelease' is present? -- Roger Oberholtzer -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
