Thanks. I have just been updating along 1.0.x with zero issues, although I realize that minor version bumps really ought to be uneventful.
trac is in pkgsrc proper, and there are plugins in a 2nd-tier repo. Many of these are tracking revision numbers in svn, and probably should be updated as well. I do use mastertickets, and used to use timingandestimation and sensitivetickets. www/trac wip/trac-plugins-AuthOpenId wip/trac-plugins-FullBlog wip/trac-plugins-FullBlogNotification wip/trac-plugins-GitPlugin wip/trac-plugins-GraphViz-svn wip/trac-plugins-MasterTickets-svn wip/trac-plugins-RoadmapHours-svn wip/trac-plugins-SensitiveTickets-svn wip/trac-plugins-TimingAndEstimation-svn wip/trac-plugins-screenshots wip/trac-plugins-spamfilter-svn In the case of mastertickets, I gather that the most recent commit is what I should run, and that it is ok with 1.2. But the main wiki page doesn't say that. The others I have not looked into, but having one of "this works with 1.2", "this doesn't work with 1.2", or "nobody knows if it works with 1.2" on each plugin page would be great. I'll probably return to this in January. -- 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.
signature.asc
Description: PGP signature
