General_Development_Process

Mo Morsi mmorsi at redhat.com
Wed Dec 21 02:31:24 UTC 2011


On 12/20/2011 06:28 PM, Michael Orazi wrote:
> All,
>
> I recently reviewed our general development process [1] and made some minor updates. It was my best effort at trying to describe our **current** norms that the community put forward quite some time ago.  I really only made updates to remove meetings that are no longer regularly held&  to adjust the time line for the the last week of a sprint to reflect the somewhat recent adjustment to sprint demos on Tuesdays.  If there are any glaring issues, feel free to update at will!
>
> Since there have been a number of questions about bugzilla states raised on irc, I thought it would be a good time to highlight the last section on that page covers our current conventions (and crutches somewhat on the state definitions on the bugzilla instance [2]).
>
> The big note here is this is the **current** norms and I suspect that as we continue to grow and mature as a community things will get updated (and likely sooner rather than later) to help us all work easier/better/faster/smarter.
>
>
> Thanks,
> Mike
>
>
> [1] https://www.aeolusproject.org/redmine/projects/aeolus/wiki/General_Development_Process
> [2] https://bugzilla.redhat.com/page.cgi?id=fields.html#status

Good writeup and agree about keeping things flexible.

Included a little blurb about useful info to include in bug reports:

https://www.aeolusproject.org/redmine/projects/aeolus/wiki/General_Development_Process#Bugzilla-info

   -Mo



More information about the aeolus-devel mailing list