On 7 jul, 09:10, claudio canepa <[email protected]> wrote:
> Ways out:
>
> - Some other committer is willing to tell 'I know how the others init
work,
> and there will be no problem with the news init' . You say: 'all the test
> runs'. All right , in that scenario I will trust both, pack what it is in
> trunk and release today.
>
> - I realize the first is hard due to time frame. It may be someone is
> willing to review, but need more time.
> Fair, but probably nobody wants to wait five weeks, and I won't have any
> motivation to return to this point in five weeks. So I don't do the
release,
> Cocos nominates another person to make it happen, and hopefully in some
days
> it can be out. Really at this point building package and documentation is
> easy, basically all in the release chain is updated and tested. We have a
> release, only that other person releases.
>
> - We settle for not introduce the features in discussion. No init for
Layer
> and Scene. I release today.
>
> How is the decision taken ?
> option 3 is Richard decision
> option 1 is any committer decision
> option 2 I think its for the Cocos historical leaders, Lucio or Riq.
>
> I will be perfectly well with any decision, really.
>
> To close, I will be out now , 9:00 local, return home between 16:00 and
> 17:00, can work from there to max 2:00
> I will be offline till 17, and will be no time for so much discussion
after.
> If there is an explicit decision by the time, much better.
>
> cheers
>
> --
> claudio
Ok, now it is 18:40, nothing new.
I choose 2, I will not release, someone else must be assigned.
It is all near done, pack and upload should not be hard.
I attach my working release_checklist as an orientation about what has been
done and what needs to be done.
While I will not be so much online in following days, I have no problem in
answer lightweight questions about some build aspect.
See.
--
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.
Early:
- uniformize all licence apareances to a comon old one, so that it can be bulk
updated later -> done
- Be sure all examples in test dir runs -> done july 5
- If possible, unit test in utest should all pass. -> steady, 1 utest dont
pass -> July 6
We should have freezed cocos dir at this moment, except for robust fixes.
Finishing:
- Proper updated license header, care to not target files which needs other
license header ->
(c) 2008 ... -> (c) 2008 - 2010 ...
done, July 6 - 14:02
- Update text files in the top trunk directory
- CHANGELOG (set date and version, added skeleton and Richard move
action, reorder items)
- LICENSE (updated)
- INSTALL (updated, add hint SDL linux - mac if possible)
- README
- compatibilty notes ?
- Make sure version and release date are consitent between diferent files, and
reasonable in relation with previous version (ascending order) - version
decision : 0.4rc0 , date decision 2010 07 07
- Version apareances in current trunk:
- setup.py +
- changelog +
- readme
- cocos.__init__
- docs ?
- (also cocos2d.org site)
- Date apareances:
- setup.py +
- changelog +
- google download page ?
- (cocos2d.org site)
- Update setup.py
- dependencies -> pyglet >= 1.1.4 +
- version +
- date +
( woops - bug report that html docs bad in linux
fixed, I think, in my local gendoc, doc re-built, upload, update wiki
page, follow up mail
? follow this issue -> Ivo reports ok
remember to upload fixed code
)
- Test that the package built with setup.py works
building command is
setup.py sdist
produces (in python 2.6) the dirs:
cocos2d.egg-info
dist -> contains only one file, cocos2d-0.4rc0.zip, dated $current_time
The zip contains all the oficial dirs, (ie junk dirs in the working
copy aren't included) and an extra dir cocos2d.egg-info
The doc directory *do not* includes the builted html (pdf) docs -> I
let at that, it makes sense when the
toolchain for docs works, so as the cocos docs
can
link to local pyglet docs.
pyglet
links from cocos will be broken.
cocos resources are present
test instalation from the built package:
hide cocos and pyglet in site-packages +
hide .pth references +
have in mind that instalation by 'setup.py install' can add a .pth to
new installed dir, to clean up later:
backed up easy-install.pth -> easy-install.pth.bak +
import cocos and import pyglet should fail +
unpack and try:
setup.py install >install.log
ends without error
adds dir cocos2d-0.4rc0-py2.6.egg in site-packages
adds file pyglet-1.1.4-py2.6.egg in site-packages , (690K, so, it is
the pyglet package ? not unpacked ?)
easy-install.pth includes path to the just installed cocos
no new dir pyglet* in site package (that can impact the normal doc
building ?)
import pyglet -> works
import cocos -> works. ( a bit slow ? a yes, compiling probably )
cocos resources present ? yes
run from the unpacked test directory ? yes
run random cocos app: ok
restore:
remove cocos2d-0.4rc0-py2.6.egg, remove file
pyglet-1.1.4-py2.6.egg +
restore the old easy-install.pth +
check for strange messages while importing pyglet and cocos,
they simple must be not present: ok
restore pth +
import pyglet, cocos : ok
test random cocos app: ok
july 6, 20:14 local - later I need to rebuild, something broke from
r1004 to current: r1022
?Note for next build: compare directories from the unpacked package
with a clean checkout to see if something is missing
- Last doc build, result will be used to update in google code and cocos2d.org
command line for my system (windows, spanish)
gendoc_cocos.py --inkscape_cmd="C:\Archivos de
programa\Inkscape\inkscape.exe" --clean --all >my_log.log
Last build to the moment: uploaded to the cocos dowload area
Going final build: build, check errors / warnings in the log don't show
any new; else try to fix epydoc syntax
A referece log with aceptable failures can be obtained by building over
a r987
- Update cocos2d.org site
Nothing done
- make local backup (svn ?) just in case
- add a 'news' about the release
- update the docs
- update the 'download' page
- (all this, local)
- after release in google, upload the changes
-------
