On Fri, Jan 16, 2009 at 03:14:44PM +0100, Christian Ridderstr?m wrote:
> On Fri, 16 Jan 2009, Petko Yotov wrote:
>> I'll make a longer and more precise statement in a day or two, about
>> what should be expected from me, but making it easy for translators to
>> prepare the documentation for a release is on my priority list.
> Speaking to your role as release manager, I suggest that you document how
> you want to do the process. In my experience that'll help you and us to
> do this more efficiently. It can be a quite simple documentation, just a
> list of the steps.
I already have a procedure in place and a script that automates the task of generating a new release -- including parts of the initial draft of the release announcement. I've been using it for years. So, we primarily need to document how one uses that release script. :-)
> I think it'd also be a good idea to write down what you think the
> different roles will do, as you will now have to differentiate between
> yourself as release manager, developer and user... not that easy in my
I agree that we should document the roles somewhere. If only we had a good way to organize such documentation that could be easily upda.... Oh. :-)
I suggest we start a page at