[Trac-Dev] Schedule for 0.12?

0 views
Skip to first unread message

3xIlling

unread,
Jan 15, 2010, 1:44:44 AM1/15/10
to trac...@googlegroups.com
Sorry for the cross post, but since I didn't get helpfull answers on trac-users list, I'm starting a new try here.

Here is what I was asking on the other list:


I just wanted to ask for the current schedule for the 0.12 release.
I know 0.11.6 is quite new, but on http://trac.edgewall.org/roadmap 0.12 is 5 weeks late, so I was wondering if there is an updated timeplan somewhere else?

BR
Micha

Remy Blank

unread,
Jan 17, 2010, 9:02:12 AM1/17/10
to trac...@googlegroups.com
> I just wanted to ask for the current schedule for the 0.12 release.
> I know 0.11.6 is quite new, but on http://trac.edgewall.org/roadmap 0.12
> is 5 weeks late, so I was wondering if there is an updated timeplan
> somewhere else?

We have been saying for some time now that it's due "pretty soon", and
at some point we wanted to have a first beta at the end of 2009. We
obviously didn't achieve that, so I'm now quite reluctant to give a new ETA.

Let's just say that the first step will be the merge of the multirepos
branch, and a single thing is holding this up (the conversion of the
authz stuff to a IPermissionPolicy). I have been working on it this
week, and Christian will have to review it.

After that, there are a few important tickets remaining (among which two
requiring database schema changes), and finally we should be able to
have a first beta.

Sorry that I can't be more precise.

-- Remy

signature.asc

anatoly techtonik

unread,
Jan 18, 2010, 9:14:04 AM1/18/10
to trac-dev
On Sun, Jan 17, 2010 at 4:02 PM, Remy Blank <remy....@pobox.com> wrote:
>
> We have been saying for some time now that it's due "pretty soon", and
> at some point we wanted to have a first beta at the end of 2009.

Will it be possible to introduce changes in that beta API? I can't
risk by using trunk/ in my installations to test how better (or worse)
is 0.12

> After that, there are a few important tickets remaining (among which two
> requiring database schema changes), and finally we should be able to
> have a first beta.

Speaking about DB API. How about defining "abstract"
DatabaseConnection class that will aggregate methods scattered over
ConnectionWrapper implementations to define a set of methods that are
absolutely required to be implemented to port backend stuff of Trac to
new data storage platforms?

--
anatoly t.

Reply all
Reply to author
Forward
0 new messages