I intend to do, in that order: end editions listed in release_checklist
look a little at how the situation in code is. build html docs, if two much epydoc warnings cleanup a bit (it was acceptable at 987) build package. zip html docs, if Richard cheatsheet is in sync with code, include in the zip, else it can be included in a doc update, and-or be a separate upload upload to googlecode set the featured download mark download and file compare ---------- stage 2 cocos2d.org update I will post when update goole code terminates. -- claudio -- You received this message because you are subscribed to the Google Groups "cocos2d discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/cocos-discuss?hl=en.
