headers
Christian Boos | 12 Nov 20:06
Picon

[Trac-dev] 0.12 Release Schedule - updates


Hi list,

A few updates about the progresses towards a 0.12 release...

First, the good news. There's been a good deal of activity recently, 
some of the changes in the custom query and ticket interface are really 
nice, you might want to give them a try. Many small tickets have been 
fixed, others have been moved to later releases, so the path toward 
milestone completion becomes visible (we have only 31 tickets left [1]).
Also, Christopher has merged the advanced-i18n branch of Genshi into 
trunk, which means that Trac trunk is now again easy to install 
('easy_install'able, I suppose). This version is fairly solid for Trac 
usage at least, and I would welcome a 0.6 release on that basis.

The multirepos branch has also seen some progresses, but is still not 
yet ready to merge on trunk. I've started to work on the few remaining 
bits (all "authz" related), so I'm pretty confident this will happen 
this week.

The #7851 branch (with_transaction refactoring) is also progressing 
well, and it looks like we will be able to integrate that after 
multirepos merge. We can even still integrate #1106 (wiki rename) after 
that.

Other stuff that will likely happen after the multirepos merge are a few 
more db schema changes, notably #6466 (int => bigint for timestamps) and 
storing 0-padded revision numbers in the repository cache (#6654).

Now for i18n, the situation is a bit mixed: we have a fairly good
(Continue reading)

Permalink | Reply | 5 comments |
headers
Andrea Tomasini | 13 Nov 13:31
Favicon

[Trac-dev] Re: 0.12 Release Schedule - updates


On 12 Nov, 2009, at 20:06 , Christian Boos wrote:

> Hi list,
Hi Christian,

> First, the good news. There's been a good deal of activity recently, 
> some of the changes in the custom query and ticket interface are really 
> nice, you might want to give them a try. Many small tickets have been 
> fixed, others have been moved to later releases, so the path toward 
> milestone completion becomes visible (we have only 31 tickets left [1]).
> Also, Christopher has merged the advanced-i18n branch of Genshi into 
> trunk, which means that Trac trunk is now again easy to install 
> ('easy_install'able, I suppose). This version is fairly solid for Trac 
> usage at least, and I would welcome a 0.6 release on that basis.
Cool, I'll have a look if the duplication bug has been also fixed... we are still runtime-patching that...
very annoying :-(

> The multirepos branch has also seen some progresses, but is still not 
> yet ready to merge on trunk. I've started to work on the few remaining 
> bits (all "authz" related), so I'm pretty confident this will happen 
> this week.
Great, so I'll try that out

> Ah, yes, some words about 0.11.6, hm, no that will be a separate mail. 
> Let me just say that I think we'll do it soon and that a 0.11.7 release 
> will probably still be needed.
Ok, so we will have more time to adapt to 0.12, that is good news, a lot of innovation coming, requiring time
also from plugin developers...
(Continue reading)

Permalink | Reply | 4 comments |
headers
Remy Blank | 13 Nov 14:12
Picon
Favicon

[Trac-dev] Re: 0.12 Release Schedule - updates

Andrea Tomasini wrote:
> I know it might be a bit late, and out of plan, but I am looking
> right now into the Milestone object, and I would like to add an
> extension point to that as well, as there is none now. At least in
> Agilo, and other plugins do that as well, would be nice to know
> when a Milestone is renamed, so that we can react to that event.
> Is someone objecting if I had extension points similar to the
> ticket ones? (E.g.: milestone_created, milestone_changed,
> milestone_deleted) ?

This has been discussed here:

  http://trac.edgewall.org/ticket/6543

but AFAICR we haven't reached a decision there about the "generic"
notification interface.

FWIW, I'd be ok with including a specialized notification interface for
milestones, as first suggested by Erik Bray in the ticket above, in
0.12, and leave the generic interface for later.

What do others think?

-- Remy
Permalink | Reply | 3 comments |
headers
Andrea Tomasini | 13 Nov 16:45
Favicon

[Trac-dev] Re: 0.12 Release Schedule - updates


On 13 Nov, 2009, at 14:12 , Remy Blank wrote:

> Andrea Tomasini wrote:
>> I know it might be a bit late, and out of plan, but I am looking
>> right now into the Milestone object, and I would like to add an
>> extension point to that as well, as there is none now. At least in
>> Agilo, and other plugins do that as well, would be nice to know
>> when a Milestone is renamed, so that we can react to that event.
>> Is someone objecting if I had extension points similar to the
>> ticket ones? (E.g.: milestone_created, milestone_changed,
>> milestone_deleted) ?
> 
> This has been discussed here:
> 
>  http://trac.edgewall.org/ticket/6543
> 
> but AFAICR we haven't reached a decision there about the "generic"
> notification interface.
That would be good :-)

> FWIW, I'd be ok with including a specialized notification interface for
> milestones, as first suggested by Erik Bray in the ticket above, in
> 0.12, and leave the generic interface for later.
Right, I can do that, I also found a kind of "bug" that is the following:

The milestone object assumes to be created, and used in two different requests, that might not always be the case:
- In the initialization the Milestone checks the "name" parameter and stores it - or not - as a copy in _old_name
- Once I insert a new Milestone, the insert method currently doesn't update the _old_name upon success...
- You can't update successfully a milestone after creation, unless you reload it again :-(
(Continue reading)

Permalink | Reply | 2 comments |
headers
Remy Blank | 13 Nov 17:44
Picon
Favicon

[Trac-dev] Re: 0.12 Release Schedule - updates

Andrea Tomasini wrote:
> On 13 Nov, 2009, at 14:12 , Remy Blank wrote:
>> FWIW, I'd be ok with including a specialized notification interface for
>> milestones, as first suggested by Erik Bray in the ticket above, in
>> 0.12, and leave the generic interface for later.
> Right, I can do that, I also found a kind of "bug" that is the following:

There's actually already a patch attached to that ticket, that
implements the interface you want for milestones. What I'm interested to
know if other developers think this is a good idea to include that patch
in 0.12. If yes, I'll apply it.

For the other issue, please open a new ticket, they are much easier to
track than mailing list messages :-)

-- Remy
Permalink | Reply | 1 comment |
headers
Robert Corsaro | 13 Nov 17:50
Favicon

[Trac-dev] u


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
Andrea Tomasini | 13 Nov 17:57
Favicon

[Trac-dev] Re: 0.12 Release Schedule - updates


On 13 Nov, 2009, at 17:44 , Remy Blank wrote:

> Andrea Tomasini wrote:
>> On 13 Nov, 2009, at 14:12 , Remy Blank wrote:
>>> FWIW, I'd be ok with including a specialized notification interface for
>>> milestones, as first suggested by Erik Bray in the ticket above, in
>>> 0.12, and leave the generic interface for later.
>> Right, I can do that, I also found a kind of "bug" that is the following:
> 
> There's actually already a patch attached to that ticket, that
> implements the interface you want for milestones. What I'm interested to
> know if other developers think this is a good idea to include that patch
> in 0.12. If yes, I'll apply it.
Ah, you mean the ExtensionPoint here... ok...

> For the other issue, please open a new ticket, they are much easier to
> track than mailing list messages :-)
I was thinking this might be good enough also for 0.11.6 it is not changing anything serious, and it is an
extension, so shouldn't harm ;-)

there you go: http://trac.edgewall.org/ticket/8817

Ciao
ANdreaT
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
(Continue reading)

Permalink | Reply | 0 comments |
headers
Christian Boos | 13 Nov 23:17
Picon

[Trac-dev] Preparing Trac 0.11.6


Hello,

As a short follow-up to the mail of yesterday about the release schedule 
for 0.12, I'd like to propose that we cut a 0.11.6 release soon. There 
are many good reasons for this:
 - we're late
 - there's a bunch of good stuff in 0.11.6dev (lots of bug fixes, 
several performance improvements) [1]
 - having this behind us will make it easier to fully focus on 0.12

The only downside is that if we release 0.11.6 now, a bunch of important 
issues will be left opened. But as there's no clear action to take for 
solving those tickets, postponing the release for an indeterminate 
period of time doesn't make much sense and prevents the good stuff to be 
delivered to the users.
For example, there's the somewhat hard to reproduce #7785 issue, there 
are still performance issues that are not fully understood in some 
setups, all things that could possibly warrant a new release once they 
get fixed. That's why I've moved them  to 0.11.7 for now [2], but 
depending on the timing they will eventually be done for a 0.12.x 
release in the end (much like 0.10.6dev never got released).

So this evening I went through the remaining tickets with Remy, and we 
think we can prepare a release candidate this week-end, with the usual 
testing period of one week, next week.

Testers, get ready ;-)
Tim, wake up the build bots!
(Continue reading)

Permalink | Reply | 3 comments |
headers
W. Martin Borgert | 14 Nov 18:17
Picon
Favicon

[Trac-dev] Re: Preparing Trac 0.11.6


Quoting "Christian Boos" <cboos <at> neuf.fr>:
>  - there's a bunch of good stuff in 0.11.6dev (lots of bug fixes,

Could you please consider using the patch for #1198 in 0.11.6?
http://trac.edgewall.org/ticket/1198
It applies cleanly, and the Debian package comes by default
with this feature. It's also in 0.12, AFAIK.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev+unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
Permalink | Reply | 0 comments |
headers
rupert.thurner@gmail.com | 18 Nov 11:54
Picon
Gravatar

[Trac-dev] Re: Preparing Trac 0.11.6

On Nov 13, 11:17 pm, Christian Boos <cb...@neuf.fr> wrote:
> Hello,
>
> As a short follow-up to the mail of yesterday about the release schedule
> for 0.12, I'd like to propose that we cut a 0.11.6 release soon. There
> are many good reasons for this:
>  - we're late
>  - there's a bunch of good stuff in 0.11.6dev (lots of bug fixes,
> several performance improvements) [1]
>  - having this behind us will make it easier to fully focus on 0.12
>
> The only downside is that if we release 0.11.6 now, a bunch of important
> issues will be left opened. But as there's no clear action to take for
> solving those tickets, postponing the release for an indeterminate
> period of time doesn't make much sense and prevents the good stuff to be
> delivered to the users.

many thanks for this!!

we try to do a http://opencsw.org solaris package as well, and like
for debian, we'd apreciate if http://trac.edgewall.org/ticket/1198
gets included.

as you mentioned before performance, do you have any experience about
the gain in this release?

rupert.

--
(Continue reading)

Permalink | Reply | 1 comment |

Gmane