tentative 0.12.0 release schedule
Jeroen Ruigrok van der Werven
beta 1 : 2008-10-01
beta 2 : 2008-10-14
rc1 : 2008-11-01
rc2 : 2008-11-14 (as needed)
release: 2008-12-01
And a suggestion aside from the above:
2008-[06/07/08/09]-01 we will use for creating tech previews (which we will
update t.e.o. with) for showcasing the current state of Trac.
My main reason for being a bit 'strict' on the dates is that it would give
us early feedback of trunk's behaviour on large datasets and tackle any
blocker issues like the memory problem early on.
--
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
Knowledge is power...
Manuzhai
<asm...@in-nomine.org> wrote:
> My current suggestion:
>
> beta 1 : 2008-10-01
> beta 2 : 2008-10-14
> rc1 : 2008-11-01
> rc2 : 2008-11-14 (as needed)
> release: 2008-12-01
I think the cycle could be much shorter for than that. Instead of
aiming to fix everything bug in the tracker, get i18n and
MultipleRepositorySupport (which are supposedly both already in a
fairly usable state), merge them, fix things up (including lots of
small bugfixes, of course), and release in three months.
Cheers,
Dirkjan
Zoom.Quiet
make 2008 is 0.11 years; let usage up it some time ,so we can sure
what is realy need input 0.12;
hope 0.12 can realse begore 2009 spring ;)
> Cheers,
>
> Dirkjan
>
>
>
> >
>
--
'''过程改进乃是开始催生可促生靠谱的人的组织!
PI keeps evolving organizations which promoting people be good!
'''http://zoomquiet.org
Pls. usage OOo to replace M$ Office. http://zh.openoffice.org
Pls. usage 7-zip to replace WinRAR/WinZip. http://7-zip.org
You can get the truely Freedom 4 software.
John Hampton
While your timeline is really only about 6 months, which is reasonable
for a release, I say let's cut the 0.12 features to i18n and
MultipleRepositorySupport and release. I think keeping releases to 2,
maybe 3 "features"[1] each is a good thing to keep our release cycle down.
-John
[1] While I think focusing on two or three features should be the goal,
if someone completes a feature that isn't on the the goals, it could be
merged. Just it wouldn't be a release blocker.
Eli
> My current suggestion:
>
> beta 1 : 2008-10-01
> beta 2 : 2008-10-14
> rc1 : 2008-11-01
> rc2 : 2008-11-14 (as needed)
> release: 2008-12-01
>
> And a suggestion aside from the above:
>
> 2008-[06/07/08/09]-01 we will use for creating tech previews (which we will
> update t.e.o. with) for showcasing the current state of Trac.
>
> My main reason for being a bit 'strict' on the dates is that it would give
> us early feedback of trunk's behaviour on large datasets and tackle any
> blocker issues like the memory problem early on.
Assuming a 0.11 release at the end of the May, this is a 6 month schedule;
seems reasonable to me.
I like John's suggestion of picking 2 features for a release. I think that if
we get those 2 features in, and stable, we should start the beta-to-release
process then, even if it's early.
I'd also like to see us improve our testing; Tim has been doing a lot of work
with VM buildbots, but we could use more machines if people have one to
spare. And our test coverage leaves a great deal to be desired.
Eli
------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
retr...@gmail.com `-------------------------------------------------
Jeroen Ruigrok van der Werven
>I like John's suggestion of picking 2 features for a release. I think that if
>we get those 2 features in, and stable, we should start the beta-to-release
>process then, even if it's early.
Sure, but then I need some more eyeballs on Genshi. A major item right now
is Genshi ticket 129. Any additional help there to fix it will serve all
translations.
I am totally clueless about Genshi's internals at this point, it's on my
list though.
--
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
If Winter comes, can Spring be far behind..?