Hello Daniel, Tuesday, August 24, 2004, 5:23:03 PM, you wrote:
DQ> 1. add https://svn.apache.org/repos/asf/spamassassin/updates DQ> updates are not on same release cycle as trunk, no branching will DQ> be done, etc. DQ> 2. under "updates", mkdir 3.0.0/rules/ ... Among the good ideas from your first posting in this thread was > - updates are published for each individual release: 3.0.0, 3.0.1, etc. > - it is expected that most updates will be equivalent across a > particular set of releases using the same rule base (3.0.x will all > be linked, etc.) Do you mean, then, to link a future 3.0.1 directory to the 3.0.0 directory? I'm wondering whether it might be better to have a generic 3.0/rules/ directory, with files that apply to all 3.0.x versions there, and link those files into the 3.0.x directories. The goal is to have one place to deposit rules depending upon where they apply. And when someone develops a rule that fits 3.0.2 through 3.0.4 only, then it can be put into a 3.0.2-4/rules/ directory, and linked to the three version-specific directories. Would this be along the lines you were thinking of? A complication: Once there is a 3.0.0, 3.0.1, and 3.0.2, are we going to want to do three nightly runs? How do we automate a multitude of testing versions? Bob Menschel
