On 29/01/2010 6:03 AM, Justin Mason wrote: > On Fri, Jan 29, 2010 at 03:21, Daryl C. W. O'Shea >> We were publishing automated sa-update updates for 3.3.0 (which was >> until we released 3.3.0 the trunk updates). This isn't good since we're >> not quite ready to automatically publish updates for stable releases. > > I was under the impression this was the plan for 3.3.x.
I thought we were going to assign scores to the rules before we distributed them. > We do rule dev, mass-checks and ruleqa using trunk, then publish the > updates to the 3.3.x sa-update channel. > > - appropriately linted; anything that fails lint will not be published > > - "if can(...)" will be used to protect trunk-only new features > > - easier than setting up a parallel ruleqa infrastructure & mass-checks There's no need to setup a parallel instance. We'll generate scores just after the weekly net mass-check and generate an update with those automatically. > If we instead move all that stuff to 3.4.0 (ie trunk), we'll be in > exactly the same situation as 3.2.x was -- ie. rule updates only cut > in response to tickets, which will effectively mean 1 update every ~3 > months. Nah. Weekly to start, more often after that's proven. > If it's not ready, in my opinion we need to get this running again as > a priority for 3.3.x. That's my plan for the weekend. Daryl
