gmane.comp.version-control.subversion.trac.devel

[Trac-dev] t.e.o updated to latest trunk


Hi,

Just a heads up that I updated t.e.o to Trac 0.11dev-r6870 and Genshi 
0.5dev-r845.

/ Jonas

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

headers

Christian Boos | 22 Apr 14:32

[Trac-dev] Re: t.e.o updated to latest trunk


Jonas Borgström wrote:
> Hi,
>
> Just a heads up that I updated t.e.o to Trac 0.11dev-r6870 and Genshi 
> 0.5dev-r845.
>   

Is it any better memory-wise?
I still plan to have a look at the .csv issue with reports, but that's 
about it for #6614.

After the #216 integration, I think we can prepare a 0.11rc1 (end of 
this week?), and release 0.11 itself once Genshi 0.5 is out (any news on 
that?)

-- Christian

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

headers

Jeroen Ruigrok van der Werven | 22 Apr 20:09

[Trac-dev] Re: t.e.o updated to latest trunk


-On [20080422 14:32], Christian Boos (cboos <at> neuf.fr) wrote:
>After the #216 integration, I think we can prepare a 0.11rc1 (end of 
>this week?), and release 0.11 itself once Genshi 0.5 is out (any news on 
>that?)

I have to wait until cmlenz is back from his 3 week holiday to roll up 0.5
including Windows eggs and the likes. That's ~2.5 weeks from now. So I hope
to have Genshi 0.5 out half May or the week after that.
Think we can release Trac 0.11 at the end of May?

--

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
Any road leads to the end of the world...

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

headers

Christian Boos | 22 Apr 20:48

[Trac-dev] Re: t.e.o updated to latest trunk

Jeroen Ruigrok van der Werven wrote:
> -On [20080422 14:32], Christian Boos (cboos <at> neuf.fr) wrote:
>   
>> After the #216 integration, I think we can prepare a 0.11rc1 (end of 
>> this week?), and release 0.11 itself once Genshi 0.5 is out (any news on 
>> that?)
>>     
>
> I have to wait until cmlenz is back from his 3 week holiday to roll up 0.5
> including Windows eggs and the likes. That's ~2.5 weeks from now. So I hope
> to have Genshi 0.5 out half May or the week after that.
> Think we can release Trac 0.11 at the end of May?
>   

I think we can get a 0.11rc1 quite soon, then I'd said we can branch 
0.11-stable and later we'll release 0.11 from that.
We've been in feature freeze on trunk for long enough now and the 
feature branches begin to pile up, so I'd like to move forward and get 
them on trunk before more serious work for 0.12 begins.

For next week, I'll write a more detailed proposal about what we should 
do for 0.12, both for Trac itself and for the way we develop it.

OTOH, there's a huge pile of outstanding issues waiting in the 0.11.1 
area (most prominent one being #3563), so we can find plenty things to 
do on branches/0.11-stable, while waiting for end of May...

-- Christian

(Continue reading)

headers

Jeroen Ruigrok van der Werven | 23 Apr 11:35

[Trac-dev] Re: t.e.o updated to latest trunk


-On [20080422 20:48], Christian Boos (cboos <at> neuf.fr) wrote:
>I think we can get a 0.11rc1 quite soon, then I'd said we can branch 
>0.11-stable and later we'll release 0.11 from that.

Sounds fine by me. +1.

>For next week, I'll write a more detailed proposal about what we should 
>do for 0.12, both for Trac itself and for the way we develop it.

Sounds interesting, looking forward to it.

>OTOH, there's a huge pile of outstanding issues waiting in the 0.11.1 
>area (most prominent one being #3563), so we can find plenty things to 
>do on branches/0.11-stable, while waiting for end of May...

Right now the unittests for Python 2.3 fail for Trac. Part is due to
subprocess being imported, which is non-existent for 2.3.

--

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
But the time has come when all good things shall pass...

--~--~---------~--~----~------------~-------~--~----~
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)

headers

Christian Boos | 23 Apr 12:20

[Trac-dev] Re: t.e.o updated to latest trunk


Jeroen Ruigrok van der Werven wrote:
> -On [20080422 20:48], Christian Boos (cboos <at> neuf.fr) wrote:
>   
>> I think we can get a 0.11rc1 quite soon, then I'd said we can branch 
>> 0.11-stable and later we'll release 0.11 from that.
>>     
>
> Sounds fine by me. +1.
>
>   
>> For next week, I'll write a more detailed proposal about what we should 
>> do for 0.12, both for Trac itself and for the way we develop it.
>>     
>
> Sounds interesting, looking forward to it.
>   

See Trac-users of this morning, for hints 

>   
>> OTOH, there's a huge pile of outstanding issues waiting in the 0.11.1 
>> area (most prominent one being #3563), so we can find plenty things to 
>> do on branches/0.11-stable, while waiting for end of May...
>>     
>
> Right now the unittests for Python 2.3 fail for Trac. Part is due to
> subprocess being imported, which is non-existent for 2.3.
>

(Continue reading)

headers

Jeroen Ruigrok van der Werven | 23 Apr 13:45

[Trac-dev] Re: t.e.o updated to latest trunk


-On [20080423 12:20], Christian Boos (cboos <at> neuf.fr) wrote:
>On a related note, I wonder if we should continue support for 2.3, with so
>many newer Python releases out there (2.4 and 2.5 available for years, 2.6
>coming soon, and 3.0 on the distant horizon).

Genshi 0.5 will support 2.3, as such 0.11 should also do so. With 0.12 I
expect us to release when 2.6 has been released and 2.3 can be dropped. I
remember Christopher saying 2.3 support for Genshi will go after Genshi 0.5
has been released.

--

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
Knowledge speaks, but wisdom listens...

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

headers

David Abrahams | 24 Apr 15:34

[Trac-dev] Re: t.e.o updated to latest trunk


on Wed Apr 23 2008, Christian Boos <cboos-AT-neuf.fr> wrote:

> Jeroen Ruigrok van der Werven wrote:
>> -On [20080422 20:48], Christian Boos (cboos <at> neuf.fr) wrote:
>>   
>>> I think we can get a 0.11rc1 quite soon, then I'd said we can branch 
>>> 0.11-stable and later we'll release 0.11 from that.
>>>     
>>
>> Sounds fine by me. +1.
>>
>>   
>>> For next week, I'll write a more detailed proposal about what we should 
>>> do for 0.12, both for Trac itself and for the way we develop it.
>>>     
>>
>> Sounds interesting, looking forward to it.
>>   
>
> See Trac-users of this morning, for hints 

Hi Christian,

I don't see any threads beginning around that time from you.  Do you
have a more specific pointer?

Thanks,

--

--

(Continue reading)

headers

Christian Boos | 24 Apr 19:11

[Trac-dev] Re: t.e.o updated to latest trunk


David Abrahams wrote:
> on Wed Apr 23 2008, Christian Boos <cboos-AT-neuf.fr> wrote:
>
>   
>> Jeroen Ruigrok van der Werven wrote:
>>     
>>> ...
>>>> For next week, I'll write a more detailed proposal about what we should 
>>>> do for 0.12, both for Trac itself and for the way we develop it.
>>>>     
>>>>         
>>> Sounds interesting, looking forward to it.
>>>   
>>>       
>> See Trac-users of this morning, for hints 
>>     
>
> Hi Christian,
>
> I don't see any threads beginning around that time from you.  Do you
> have a more specific pointer?
>   

See http://groups.google.com/group/trac-users/msg/eed510f50f82c109

-- Christian

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.

(Continue reading)

headers

Christian Boos | 23 Apr 09:04

[Trac-dev] Re: t.e.o updated to latest trunk


Jonas Borgström wrote:
> Hi,
>
> Just a heads up that I updated t.e.o to Trac 0.11dev-r6870 and Genshi 
>   

It seems you didn't update the htdocs:
http://www.edgewall.org/chrome/common11/js/diff.js corresponds to the 
version before the fixed one (r6853).

-- Christian

> 0.5dev-r845.
>
> / Jonas
>
> >
>
>   

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

headers

Jonas Borgström | 23 Apr 21:06

[Trac-dev] Re: t.e.o updated to latest trunk


Christian Boos wrote:
> 
> Jonas Borgström wrote:
>> Hi,
>>
>> Just a heads up that I updated t.e.o to Trac 0.11dev-r6870 and Genshi
>>
> 
> It seems you didn't update the htdocs:
> http://www.edgewall.org/chrome/common11/js/diff.js corresponds to the
> version before the fixed one (r6853).

Are you sure it isn't some kind of browser cache issue?

$ curl http://www.edgewall.org/chrome/common11/js/diff.js | md5
d881ecc9a057c9f8a969c3978e879567
$ curl http://svn.edgewall.org/repos/trac/trunk/trac/htdocs/js/diff.js | 
md5
d881ecc9a057c9f8a969c3978e879567

This morning I removed a trac restart script from the t.e.o crontab and 
so far the memory usage seems to be fairly stable without it, but I'll 
continue monitoring it:

http://www.edgewall.org/rrd/mem-day.png

Regarding having a rc1 release in the next couple of days I'm also +1. A 
release this Sunday would work best for me personally. But if anyone 
need some more time to finish something that should go into rc1 we can

(Continue reading)

headers

Jeroen Ruigrok van der Werven | 23 Apr 22:37

[Trac-dev] Re: t.e.o updated to latest trunk


-On [20080423 21:06], Jonas Borgström (jonas <at> edgewall.com) wrote:
>Regarding having a rc1 release in the next couple of days I'm also +1. A 
>release this Sunday would work best for me personally.

I'm ok with it too.

Only thing I cannot do right now is get a Genshi 0.5 rc1 out of the door
without cmlenz around.

--

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
I dream of gardens in the desert sand...

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

headers

Eli | 24 Apr 04:15

[Trac-dev] Re: t.e.o updated to latest trunk

On Wednesday 23 April 2008 03:37:14 pm Jeroen Ruigrok van der Werven wrote:
> -On [20080423 21:06], Jonas Borgström (jonas <at> edgewall.com) wrote:
> >Regarding having a rc1 release in the next couple of days I'm also +1. A
> >release this Sunday would work best for me personally.
>
> I'm ok with it too.
>
> Only thing I cannot do right now is get a Genshi 0.5 rc1 out of the door
> without cmlenz around.

I haven't had time to work on http://trac.edgewall.org/ticket/6879 .   I think 
it's going to be a significant issue for some, and I'm afraid it's going to 
be a bit of work to fix correctly.  I also think we do need to change it, 
rather than leave it as-is as cboos suggested; the users expect it to behave 
in the same basic way as it did in 0.10, and I think they're right.

Whether this is something that blocks an rc1 or not is left open for 
discussion.

Eli
------------------. "If it ain't broke now,
Eli Carter         \                  it will be soon." -- crypto-gram
retracile <at> gmail.com `-------------------------------------------------

--~--~---------~--~----~------------~-------~--~----~
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)

headers

Christian Boos | 24 Apr 11:53

[Trac-dev] Re: t.e.o updated to latest trunk


Jonas Borgström wrote:
> Christian Boos wrote:
>   
>> Jonas Borgström wrote:
>>     
>>> Hi,
>>>
>>> Just a heads up that I updated t.e.o to Trac 0.11dev-r6870 and Genshi
>>>
>>>       
>> It seems you didn't update the htdocs:
>> http://www.edgewall.org/chrome/common11/js/diff.js corresponds to the
>> version before the fixed one (r6853).
>>     
>
> Are you sure it isn't some kind of browser cache issue?
> ...
>   

Indeed, it was a cache issue in Firefox - I thought I did a force 
reload, but probably didn't. I'm not sure why this explicit reload is 
needed at all (Firefox bug? server setup?).

> This morning I removed a trac restart script from the t.e.o crontab and 
> so far the memory usage seems to be fairly stable without it, but I'll 
> continue monitoring it:
>
> http://www.edgewall.org/rrd/mem-day.png
>

(Continue reading)

headers

Jonas Borgström | 24 Apr 13:26

[Trac-dev] Re: t.e.o updated to latest trunk

Christian Boos wrote:
> Indeed, it was a cache issue in Firefox - I thought I did a force
> reload, but probably didn't. I'm not sure why this explicit reload is
> needed at all (Firefox bug? server setup?).

Probably a browser issue since the server doesn't send any Expires 
headers at all, just normal Last-Modified and Etag headers. Are you 
perhaps behind some kind of (transparent) http proxy?

>> This morning I removed a trac restart script from the t.e.o crontab and
>> so far the memory usage seems to be fairly stable without it, but I'll
>> continue monitoring it:
>>
>> http://www.edgewall.org/rrd/mem-day.png
> 
> Interesting, so what exactly happened near 6:20 AM this morning?
> (I guess that what happened at 09:40 AM was a server restart  ).

Yeah, it took a while to figure out what happend at 6:25 but then I 
realized that that's the exact time the daily crontab jobs are started.
The spike in memory allocation was caused by logrotate restarting 
lighttpd in a way that didn't manage to kill all running fastcgi 
processes before starting a new set of processes. This should be fixed 
now so tomorrow at the same time we should see a drop in memory usage 
instead of an increase.

/ Jonas

--~--~---------~--~----~------------~-------~--~----~

(Continue reading)

headers

Christian Boos | 28 Apr 10:05

[Trac-dev] Re: t.e.o updated to latest trunk

Christian Boos wrote:
> Jonas Borgström wrote:
>   
> ...
>> Regarding having a rc1 release in the next couple of days I'm also +1. A 
>> release this Sunday would work best for me personally. But if anyone 
>> need some more time to finish something that should go into rc1 we can 
>> always pick another date.
>>   
>>     
>
> Sunday will be good for me too. ...

Jonas, I'm really sorry, I couldn't find the time this week-end to even 
show up on #trac or send a mail.
What about doing the last bunch of changes beginning of this week, test 
it during the second part of the week, and if all goes well, release 
next week? (again, if time permits...)

Besides, I wonder if we shouldn't take the opportunity of this 0.11rc1 
release to also make a 0.10.5 release (with mostly the current status of 
0.10.5dev) and officially "freeze" the 0.10.x branch. There are a couple 
of important bug fixes in 0.10.5 (1), so that leaving 0.10.4 as the last 
stable release for that development line doesn't feel optimal. Could 
people running 0.10.5dev comment about the stability?

The only thing that should probably be added to 0.10.5dev is the 
backport of r6240 (2), so that base_url would behave uniformly in 
0.10.4, 0.10.5 and 0.11, with the base_url_for_redirect option present

(Continue reading)

headers

Jeroen Ruigrok van der Werven | 28 Apr 11:03

[Trac-dev] Re: t.e.o updated to latest trunk


-On [20080428 10:05], Christian Boos (cboos <at> neuf.fr) wrote:
>Jonas, I'm really sorry, I couldn't find the time this week-end to even 
>show up on #trac or send a mail.
>What about doing the last bunch of changes beginning of this week, test 
>it during the second part of the week, and if all goes well, release 
>next week? (again, if time permits...)

Noah was quite against putting out a rc without a deploy target in it for
the *gi-bin and htdocs stuff.

--

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
My name is Legion: for we are many...

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

headers

Jonas Borgström | 28 Apr 13:54

[Trac-dev] Re: t.e.o updated to latest trunk


Jeroen Ruigrok van der Werven wrote:
> 
> -On [20080428 10:05], Christian Boos (cboos <at> neuf.fr) wrote:
>>Jonas, I'm really sorry, I couldn't find the time this week-end to even
>>show up on #trac or send a mail.
>>What about doing the last bunch of changes beginning of this week, test
>>it during the second part of the week, and if all goes well, release
>>next week? (again, if time permits...)

No problem Christian, there was still the "script deploy" thing that 
needed to be addressed first. But now with that in place I can see a rc1 
release tomorrow unless there are more release blockers I don't know 
about.
/ Jonas

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

headers

Christian Boos | 28 Apr 20:29

[Trac-dev] Re: t.e.o updated to latest trunk

Jonas Borgström wrote:
> Jeroen Ruigrok van der Werven wrote:
>   
>> -On [20080428 10:05], Christian Boos (cboos <at> neuf.fr) wrote:
>>     
>>> Jonas, I'm really sorry, I couldn't find the time this week-end to even
>>> show up on #trac or send a mail.
>>> What about doing the last bunch of changes beginning of this week, test
>>> it during the second part of the week, and if all goes well, release
>>> next week? (again, if time permits...)
>>>       
>
> No problem Christian, there was still the "script deploy" thing that 
> needed to be addressed first. But now with that in place I can see a rc1 
> release tomorrow unless there are more release blockers I don't know 
> about.
>   

Thanks!
Well, I don't have blockers, strictly speaking, but as the changes I 
would like to make for rc1 (merge of the #216 branch,  next_rev 
optimization, ...) present as always the risk of introducing some new 
issues, so I'd prefer that we let a few days pass on t.e.o once it's 
running (successfully) at the latest revision.

I've committed a bunch of those this evening, and perhaps a few more 
tomorrow (#3563, #7105).

-- Christian

(Continue reading)

headers

Jonas Borgström | 29 Apr 15:57

[Trac-dev] Re: t.e.o updated to latest trunk


Christian Boos wrote:
> Thanks!
> Well, I don't have blockers, strictly speaking, but as the changes I
> would like to make for rc1 (merge of the #216 branch,  next_rev
> optimization, ...) present as always the risk of introducing some new
> issues, so I'd prefer that we let a few days pass on t.e.o once it's
> running (successfully) at the latest revision.
> 
> I've committed a bunch of those this evening, and perhaps a few more
> tomorrow (#3563, #7105).

t.e.o has been running r6904 since last night and was just updated to 
r6906.

Anyone planning to commit any more non-trivial code changes or can we 
freeze trunk now and try to release rc1 later today?

/ Jonas

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

headers

Christian Boos | 29 Apr 17:31

[Trac-dev] Re: t.e.o updated to latest trunk


Jonas Borgström wrote:
> Christian Boos wrote:
>   
>> Thanks!
>> Well, I don't have blockers, strictly speaking, but as the changes I
>> would like to make for rc1 (merge of the #216 branch,  next_rev
>> optimization, ...) present as always the risk of introducing some new
>> issues, so I'd prefer that we let a few days pass on t.e.o once it's
>> running (successfully) at the latest revision.
>>
>> I've committed a bunch of those this evening, and perhaps a few more
>> tomorrow (#3563, #7105).
>>     
>
> t.e.o has been running r6904 since last night and was just updated to 
> r6906.
>
> Anyone planning to commit any more non-trivial code changes or can we 
> freeze trunk now and try to release rc1 later today?
>   

I just committed fixes for #7105 and #7168.
Now, I see that you're eager to release, so I'll stop here 

Please also have a look at fixing #3674 locally on t.e.o, by applying 
the fix described in http://trac.edgewall.org/ticket/3674#comment:21

-- Christian

(Continue reading)

headers

Jonas Borgström | 29 Apr 19:27

[Trac-dev] Re: t.e.o updated to latest trunk


Christian Boos wrote:
> I just committed fixes for #7105 and #7168.
> Now, I see that you're eager to release, so I'll stop here 

Of course it would be nice to get rc1 out the door. We can always 
postpone some minor bug-fixes until rc2 or 0.11final at we need to 
include all tickets which affects the api into rc1. And there is still 
#6879 which Eli is working on which I forgot.

> Please also have a look at fixing #3674 locally on t.e.o, by applying
> the fix described in http://trac.edgewall.org/ticket/3674#comment:21

I'll have a look at it.

/ Jonas

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

headers

Eli | 30 Apr 03:37

[Trac-dev] Re: t.e.o updated to latest trunk


On Tuesday 29 April 2008 12:27:34 pm Jonas Borgström wrote:
> Christian Boos wrote:
> > I just committed fixes for #7105 and #7168.
> > Now, I see that you're eager to release, so I'll stop here 
>
> Of course it would be nice to get rc1 out the door. We can always
> postpone some minor bug-fixes until rc2 or 0.11final at we need to
> include all tickets which affects the api into rc1. And there is still
> #6879 which Eli is working on which I forgot.

Sorry to be the one holding up the release. :(

I committed a minimal fix for #6879 in r6919.  It does open up another issue, 
which I filed as #7176.  But I think that issue is lower priority... it's a 
custom-workfow-action-plugin + user-interface gotcha.  It is something that 
needs to be fixed, but it's going to take a bit of work, and I don't think 
it's a release blocker.

Eli
------------------. "If it ain't broke now,
Eli Carter         \                  it will be soon." -- crypto-gram
retracile <at> gmail.com `-------------------------------------------------

--~--~---------~--~----~------------~-------~--~----~
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)

headers

Jeroen Ruigrok van der Werven | 29 Apr 18:38

[Trac-dev] Re: t.e.o updated to latest trunk


-On [20080429 15:58], Jonas Borgström (jonas <at> edgewall.com) wrote:
>Anyone planning to commit any more non-trivial code changes or can we 
>freeze trunk now and try to release rc1 later today?

I'm clear. Let me sync to trunk now for my branches as well.

--

-- 
Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/ | GPG: 2EAC625B
Weep for the lives your wishes never lead...

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

headers

osimons | 29 Apr 22:01

[Trac-dev] Re: t.e.o updated to latest trunk


On Apr 29, 3:57 pm, Jonas Borgström <jo...@edgewall.com> wrote:

> Anyone planning to commit any more non-trivial code changes or can we
> freeze trunk now and try to release rc1 later today?

I was done a couple of weeks ago with what I had marked as important
on my to-do list for 0.11, so I'm ready whenever others feel ready.

:::simon

https://www.coderesort.com
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

headers

Noah Kantrowitz | 28 Apr 19:15

[Trac-dev] Re: t.e.o updated to latest trunk


On Apr 28, 2008, at 5:03 AM, Jeroen Ruigrok van der Werven wrote:
>
> -On [20080428 10:05], Christian Boos (cboos <at> neuf.fr) wrote:
>> Jonas, I'm really sorry, I couldn't find the time this week-end to  
>> even
>> show up on #trac or send a mail.
>> What about doing the last bunch of changes beginning of this week,  
>> test
>> it during the second part of the week, and if all goes well, release
>> next week? (again, if time permits...)
>
> Noah was quite against putting out a rc without a deploy target in  
> it for
> the *gi-bin and htdocs stuff.

Its done, trac-admin ... deploy.

--Noah

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---