A release manager would be responsible for deciding when to do
releases, as well as to make sure everything is up to snuff... which
would probably mean that they'd spend a lot of their time reviewing
code and docs, probably fixing some of it personally (especially
docs). I think we're pretty solid on most things, but all of the new
stuff still needs work (Selector, and the Scriptaculous stuff). I'm
tempted to do a release without those things, but it seems that most
people are using one or the other by now so that's not really an
option.
I've had a couple people express interest so far, but I'm in Seoul
right now for a conference and I'm having a hard enough time keeping
up with work stuff so I will probably get to that in a week or two
after I get back to SF.
-bob
On 11/7/07, JonR800 [EMAIL PROTECTED] wrote:
That begs the question, what's required of a release manager for MK?
On Oct 29, 4:23 pm, Bob Ippolito [EMAIL PROTECTED] wrote:
There's no need to fork the project, I would gladly hand over SVN
access to someone who wants to step up as a release manager.
-bob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
MochiKit group.
To post to this group, send email to mochikit@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/mochikit?hl=en
-~--~~~~--~~--~--~---
