I'm a little confused, and can't check now. I thought this fix was to the existing plugins in the examples directory ? I'm fine moving it to the plugins repo, or to plugins in main repo once it's stable, but then we should remove the one from examples .
>> > > If it's stable in production, can we add it to the trafficserver repo? > > I'd like to keep accumulating all the useful plugins in the release package > so that there is a useful set available as soon as you install ATS ... I think that's a different topic :). What we intended for was to avoid having to do a myriad of full releases to fix plugins. Moving some very stable plugins seems fine, but we should not automatically include all and any plugin in the distributions. I'm fine merging the two repos, as long as we can easily distinguish stable (or even functional) plugins and only include those in the official packages. Perhaps with Git, we should just have an experimental branch for plugins, and merge selectively as we promote a plugin (after discussion on dev@ of course). Cheers, -- Leif
