Request: please consider clarifying the project's position on Spins

Bruno Wolff III bruno at wolff.to
Fri Dec 3 17:05:47 UTC 2010


On Fri, Dec 03, 2010 at 16:27:48 +0000,
  "\"Jóhann B. Guðmundsson\"" <johannbg at gmail.com> wrote:
> 
> Do you inform/announce/remind the relevant parties in the community 
> about your release schedule at the beginning of each release cycle?

The reminders would be handled by the project manager. Poelstra (soon to
be replaced) asks each group what they need on their schedule and sends out
reminders at specified points in the schedule.

So the way this should work is that Design Team would have documentation
in their area about when they want requests by for different types f things.
The Spins SIG should take note of this, either proactively or in response
to an incident. Hopefully notable changes in the Design Team policy would
get communicated to affected groups, but Spins SIG should notice if it
doesn't. Then the Spins SIG should communicate with the project manager to
request a schedule item. In this case there would probably be about a week
before the deadline. It would also get added somewhere in the Spin Process
documentation so that people creating spins could see it.

Off course this depends on a functioning Spins SIG; it doesn't work very well
with a bunch of independent SIGs creating spins.


More information about the advisory-board mailing list