As part of the plan to get Balloon development a bit more organised we
now have a bugzilla installed and working.
I've put in a few sample products and components and versions, but
it's not entirely obvious how we should map Balloon hardware and
software onto bugzillas products, components, and versions.
It rather assumes you are toalking about software rather than hardware
(as every 'product' can have 'hardware' and 'OS')
We could put the balloon flavours in the hardware list and have the
various software parts as products (that fits the bugzilla model quite
well but someone reporting stuff might expect to see 'Balloon3' in the
main product list they are trying to report about?)
We could have the balloons as products and the bootloader, kernel,
JTAG, rootfs as components. That's OK, but then do versions apply to
hardware versions or software versions?
Balloon hardware variants could be mapped to versions or each could be
a new product (That's annoying if there are mnay components as they
need to be entered separately for each product SFAICS). We have both
variants and versions of hardware.
We could have balloon hardware _and_ bootldr, kernel, etc as products.
That makes the versions mean something sensible, but I'm not sure what
components would correspond to.
And so on. If anyone has significant opinions on or experience of putting
hardware stuff into bugzilla then please speak up otherwise I'll just
try one of the above and see how it goes.
Bugzilla also has enormous configurability which it might make sense
to use to make things map better but that is probably a lot of work...
You can see what we have here:
http://www.balloonboard.org/cgi-bin/bugzilla
It would be useful if core developers could set up accounts there,
because otherwise I can't allocate any bugs to you :-)
Wookey
--
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel +44 (0) 1223 811679
work: http://www.aleph1.co.uk/ play: http://wookware.org/
(text/plain)