On Tuesday, March 14, 2017 at 11:17:10 PM UTC-7, Roger Oberholtzer wrote: > > On Tue, Mar 14, 2017 at 6:06 PM, RjOllos <[email protected]> wrote: > > > Yes, I think 'anyrelease' should be mutually exclusive with other > release > > tags. There were some plugins that didn't follow this rule that I > fixed-up > > just now. > > > > Generally an 'anyrelease' plugin or integration will not depend on the > Trac > > API, and is unlikely to break in a future release. > > I plan on adding the tags for the plugins I am using on 1.2. My > criterion will be that it runs for me.
That's great. Thank you. > So I will only be able to add > 1.2 (if 'anyrelease' is not already tagged). But that does not mean > that 'anyrelease' does not apply. I don't have the knowledge to > determine if there are API references in the code... > I wouldn't worry about the anyrelease tag. It's not very useful, and I think we might just remove it eventually. If you come across any plugins you are using that are tagged with anyrelease, just mention here. - Ryan -- 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.
