arsenal-devel team mailing list archive

[Bryce Harrington <bryce@xxxxxxxxxxxxx>]

[Btw, at the UDS session the request was that we shift to using
arsenal-user@ for all discussions (including development), since -devel
is a closed list.  So follow up to this thread should perhaps be
directed there instead.]

On Fri, May 18, 2012 at 10:21:48AM -0700, Bryce Harrington wrote:
> On Fri, May 18, 2012 at 09:56:59AM +0300, Jussi Pakkanen wrote:
> > Hi
> > 
> > I'd like to start discussion on how to get new scripts into Arsenal
> > as it is currently not totally clear. Especially since the 1.0/2.0
> > reorganisation is going on.
> > 
> > We have a script that gathers bugs for the uTouch projects, which we
> > would want to get running automatically. Currently it creates its
> > own HTML output, because its output is slightly different than
> > existing scripts.
> > 
> > Here are the questions I have:
> > 
> > - Should it go to Arsenal 1.0 or 2.0?
> > - How strictly does it need to adhere to the current architecture
> > (that has a separate formatter script)?
> > - What needs to be done to get it to run automatically?
> 
> Good questions.  We don't have solid guidelines to answer these yet, but
> we should.
> 
> Here's my thinking.
> 
> The development goal for 2.0 branch is to converge the scripts into a
> consistent architecture, but it's not there yet.  At this stage I'd see
> no problem adding more independent scripts, as long as they can be
> migrated into the new architecture in time.
> 
> The 1.0 branch goal is stability, focusing mainly on bug fixing.
> However, adding a new script that doesn't impinge on any of the existing
> code would obviously not impact stability.  But I think that script
> should pretty much be "done" - i.e. you don't expect to be working on it
> any further except for bug fixes.
> 
> Regarding adherence to the current architecture, while that is
> definitely a primary goal to achieve we're not at that point yet.  I
> don't think it'd be fair to be super strict on this point, since we've
> been pretty liberal ourselves up to this point, so long as there is
> agreement for working towards the consistent architecture goals.
> When I have something documented and some working examples we can
> tighten up the policies here.
> 
> For getting it to run automatically on cranberry, hopefully Ursula or
> Brian can answer what the process is;  I have poked around enough to
> think I know, but I'm still sort of a newb there myself.
> 
> Bryce