Hi folks,

with the impeding release of Yahoo's ATS plugins we have
to think about how to organize and most importantly how
to release plugins.

The problem most often brought up in regard to releasing plugins
bundled with the server is that it would make security fixes
caused by a single plugin a lot harder to test. As a solution
to this problem I propose to have all plugins bundled together
and release them separate from the server.

The plugins should track the server's API version and for this
purpose have the appropriate branches, analogous to our
``traffic'' repository:

├── plugins
│   ├── branches
│   │   └── 3.0.x
│   └── trunk
└── traffic
    ├── branches
    │   └── 3.0.x
    └── trunk


Feedback welcome! :)

So long,
i

--
Igor Galić

Tel: +43 (0) 664 886 22 883
Mail: i.ga...@brainsware.org
URL: http://brainsware.org/
GPG: 571B 8B8A FC97 266D BDA3  EF6F 43AD 80A4 5779 3257

Reply via email to