Rockbox mail archive
Subject: RE: daniels blog and release..
RE: daniels blog and release..
so i must be retarded... I cant post a comment on the blog so I'm
sticking this here...
I recon we are probably at a good state to try for a release again,
looking at the tracker we have 3 open bug still marked as "Release
3.0" (fine we haven't added any, but its still an idea where we are)
and swcodec is much more stable now than it was a year ago...
the other reason to try releasing now is because with viewports, (if
we want it done properly) lots of code will probably be changed and it
will take ages to finish, which means we release now, or release in 6+
Also just had a quick glance at ReleaseTodo and almost everything
there is at a state where we would have said its ready last time.
I'm in no way volunteering to be release manager (it would fail worse
than last time if i was) but what I would suggest is say feature
freeze, go through the tracker and do another clean out of the patches
(bug fixes only) and bugs and release 14 days later with a possible
extra 7 days but absolutely no more than that.. and if its not ready
then cancel and try again in a year.
The other option is to branch off today's build (maybe revert
viewports in that branch) and call it the release and backport bug
fixes when a major one happens in trunk?
Received on 2008-01-08
Page was last modified "Jan 10 2012" The Rockbox Crew