On 2015-07-04 09:18, Remy Blank wrote:
> Hello Jonas,
>
> The certificate for svn.edgewall.org has expired yesterday. Any chance
> that you could renew it?
Oh, sorry about that, I've just newned it.
It should work correctly already, but the new cert is not yet available
on the OCSP server so you m
On 2014-06-09 23:26, Ryan Ollos wrote:
> On Mon, Jun 9, 2014 at 1:31 PM, Jonas Borgström <mailto:jo...@borgstrom.se>> wrote:
>
> On 2014-06-07 10:38, RjOllos wrote:
> > I'm looking at some services that we might be able to use to
> provide CI
>
On 2014-06-07 10:38, RjOllos wrote:
> I'm looking at some services that we might be able to use to provide CI
> for the Trac project; currently evaluating drone.io which can run builds
> off the mirror on GitHub. I was wondering if someone could add me to the
> Edgewall group on GitHub so that I ca
On 07/10/2013 07:09 AM, Olemis Lang wrote:
> Hi !
>
> I'm trying to create this issue against Genshi issue tracker
*snip*
> I always receive «Submission rejected as potential spam» , so I give up .
After some investigation it turns out the spamfilterplugin version used
by the Genshi instance was
This is just a heads up that I've replaced the certificate since it was
about to expire.
/ Jonas
signature.asc
Description: OpenPGP digital signature
On 06/11/2013 12:20 AM, Christian Boos wrote:
> So I'd like to ask my fellow Trac developers what's their take on this
> and if they'd like to see rjollos becoming part of the AUTHORS!
Welcome!
/ Jonas
signature.asc
Description: OpenPGP digital signature
On 06/01/2013 11:20 AM, Jun Omae wrote:
> On Tue, May 28, 2013 at 2:48 AM, Remy Blank wrote:
>> RjOllos wrote:
>>> We've noticed that email notifications seem to have broken around the
>>> time of this maintenance:
>>> http://trac.edgewall.org/ticket/717#comment:54
That should be fixed now. The v
On 05/19/2013 09:57 PM, Jonas Borgström wrote:
Hi all,
the t.e.o server will soon be offline for some maintenance work. I
expect the server to be back online in around 1-3 hours if things go
according to plan.
t.e.o should be back online now. Let me know if anything seems broken.
Cheers
Hi all,
the t.e.o server will soon be offline for some maintenance work. I
expect the server to be back online in around 1-3 hours if things go
according to plan.
Cheers,
Jonas
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To unsubscr
On 2012-01-12 14:53 , osimons wrote:
3) Jonas, I suppose if we transferred the IP elsewhere we should also
handle the other Trac dependencies/dependents at the same time -
Genshi, Babel, Bitten in particular. It widens the scope a little, but
should still be quite manageable.
Agreed, it makes
On 2012-01-11 04:25 , Ethan Jucovy wrote:
On Sun, Jan 8, 2012 at 11:36 AM, Greg Troxel wrote:
> inbound=outbound: there is no formal CLA but there's a policy, perhaps
> formal, that states that all code contributions are made under the
> existing license.
>
> I have the impression
Hi all,
The server hosting *.edgewall.org will tomorrow Thursday be moved to
new hardware. The work will start at 12 PM CET and take around 4
hours.
The new ip adrresses are:
www|trac.edgewall.org: 78.47.205.98
svn.edgewall.org: 78.47.205.99
Cheers,
Jonas
--
You received this message because
On Tue, Sep 8, 2009 at 11:27 AM, Remy Blank wrote:
> anatoly techtonik wrote:
>> I've just got this stacktrace from t.e.o. after long delays with
>> opening pages.
>
> Yes, I have noticed, too. I have already mailed Jonas about it.
When I logged in I noticed the server load was 23 and 25 postgres
On Tue, Sep 1, 2009 at 11:15 AM, Christian Boos wrote:
>
> Emmanuel Blot wrote:
> > It seems t.e.o. is in trouble:
> >
> > eb...@oulme:~$ ping trac.edgewall.org
> > PING www.edgewall.org (88.198.140.129): 56 data bytes
> > ^C
> > --- www.edgewall.org ping statistics ---
> > 23 packets transmitted
Trac 0.11.5 Released
We're happy to announce the Trac 0.11.5 release.
You will find this release at the usual place:
http://trac.edgewall.org/wiki/TracDownload
Trac 0.11.5 contains a number of bug fixes and minor enhancements.
The following list contains only a few highligh
Trac 0.11.5rc2 (Release Candidate 2)
This is the second and hopefully final release candidate for the
upcoming 0.11.5 release.
Trac 0.11.5rc2 fixes two regressions found in rc1 and one minor
enhancement:
* Fixed workaround for zipped Genshi eggs, [8354], #7
On 7/10/09 8:52 PM, Remy Blank wrote:
> Considering this, I would be more comfortable doing a 0.11.5rc2 before
> the final release.
Agreed, when releasing a final version it's always nice to be able to
simply relabel the latest rc.
I'll put out rc2 tonight and then we'll be able to rebrand it as
On 7/1/09 11:52 AM, Christian Boos wrote:
> Hello,
>
> Thanks for having completed the rc1 release!
> Sorry I couldn't assist yesterday.
>
> A minor suggestion: the final announcement could be made more "attractive":
Yes definitely, it could use some more work.
Anyway, I managed to forget abou
Trac 0.11.5rc1 (Release Candidate 1)
This is the first and hopefully final release candidate for the
upcoming 0.11.5 release. 0.11.5 (final) is scheduled for release on
July 7.
Trac 0.11.5rc1 contains a number of bug fixes and minor enhancements.
The followin
On 6/29/09 12:14 PM, Christian Boos wrote:
> Hello,
>
> Some updates about the upcoming 0.11.5 release...
> Last week and this week-end, things have progressed well. Let's look at
> the remaining items.
>
> There's still a minor glitch in #7715 that I hope I can fix this
> evening, as well as
On 3/27/09 7:43 PM, Christian Boos wrote:
> As he kindly agreed, I'd like to propose him more "officialy" for being
> a partial committer on the sandbox/SpamFilter area.
+1, sounds like a great idea.
Michael, I'll contact you off-list with further details.
/ Jonas
--~--~-~--~~
Trac 0.11.4rc2 (Release Candidate 2)
This release candidate addresses one regression found in rc1.
Trac 0.11.4 (final) is scheduled for release on Monday, 03/30.
You will find this release at the usual place:
http://trac.edgewall.org/wiki/TracDownload
Bugs f
On 3/25/09 9:04 AM, Noah Kantrowitz wrote:
> No, not sure how it would be
>
> If you want to add a test case for this particular thing, so write one
> and submit it. We have a pretty big unit and functional testing
> infrastructure. The point is that t.e.o isn't a test site and
> shoul
On 3/25/09 12:40 AM, Remy Blank wrote:
> The following defect has just been reported:
>
> http://trac.edgewall.org/ticket/8153
>
> The symptoms are:
>
> - Mainnav entries redirected through [mainnav] with a relative .href
> don't work (most ironical example: the "New ticket" link on t.e.o).
On 3/17/09 10:11 PM, Remy Blank wrote:
> The first release candidate for Trac 0.11.4 is about to be released. To
> ensure that the final 0.11.4 release is well tested and doesn't
> introduce any regressions, we need a few people who are willing to test
> the release candidate.
I just wanted to ad
Trac 0.11.4rc1 (Release Candidate 1)
This is the first and hopefully final release candidate for the upcoming
0.11.4 release.
You will find this release at the usual place:
http://trac.edgewall.org/wiki/TracDownload
Trac 0.11.4rc1 contains a number of bug fi
On 3/17/09 7:51 PM, Christian Boos wrote:
> I think we're now (r7945) in a good shape for a rc1.
>
> For the last ticket I left opened for 0.11.4
> (http://trac.edgewall.org/ticket/8128), the patch attached there should
> work, but as I'm not able to fully test it from end to end, I think it
> nee
On 3/3/09 8:59 AM, Remy Blank wrote:
> rupert.thurner wrote:
>> would running -stable on teo be an option, like wikipedia does it with
>> mediawiki?
>
> I think that's already the case. AFAIK, Jonas is updating t.e.o
> periodically to 0.11-stable.
Yes, and I've just updated it to [7938].
Anyway,
On 3/1/09 7:19 PM, Remy Blank wrote:
> Jonas Borgström wrote:
>> Most issues seems to have been fixed in 0.11-stable already but are
>> there any other bug fixes that need to go into 0.11.4 as well?
>
> I'd like to fix the following ticket for 0.11.4:
>
>http
Hi all,
0.11.3 unfortunately contained a few regressions so we need to get
0.11.4 out pretty soon.
Most issues seems to have been fixed in 0.11-stable already but are
there any other bug fixes that need to go into 0.11.4 as well?
And to avoid similar regressions in the future we need to do so
On 2/23/09 12:32 PM, Emmanuel Blot wrote:
> Hi,
>
> It seems that the Restructured Text engine is not enabled anymore on t.e.o.
>
> While it is not a big deal for demonstration purposes (e.g.
> http://trac.edgewall.org/wiki/WikiRestructuredText), it's a real issue
> for other projects (such as Bit
On 2/14/09 8:14 AM, rupert.thur...@gmail.com wrote:
> could help out for solaris, python-2.5.
That would be great. I'm currently doing some testing with py25 on mac
and py23 and py26 on windows. So far I've found one python 2.3 issue but
besides that we seem to be in good shape.
/ Jonas
--~--
On 2/12/09 12:43 AM, Remy Blank wrote:
> 0.11.3 seems to be in good shape, with only a single open ticket
> remaining (#4416 is already fixed in 0.11-stable, but I keep it open to
> remember cleaning the merge to trunk).
>
> How about setting a tentative release date? I'm available for testing on
> On Dec 9, 12:15 am, Christian Boos wrote:
>> a...@redcondor.com wrote:
>>> the python 2.6 changelog entry:
>>> --
>>> The cgi module will now read variables from the query string of an
>>> HTTP POST request. This makes it possible to use form actions with
>>> URLs that include q
On Dec 14, 2008, at 12:16 PM, Omry Yadan wrote:
>> I'd be interested to know if you still get the crash if you enable
>> pooling on linux.
>>
> Enabling pooling seems to have resolved my situation, and I have not
> seen any crashes yet (in the last 12 hours).
> Quoting the ticket:
> "But on Linu
Remy Blank wrote:
>> I just wanted to give everyone a heads up that I've moved the linux-py25
>> build slave to the advanced-i18n branch of Genshi.
>
> Ah, that's why [7708] built ok on 2.5. I was wondering about that.
>
>> the linux-py24 slave is still using Genshi 0.5.1 for now.
>>
>> Trunk is
Hi all,
I just wanted to give everyone a heads up that I've moved the linux-py25
build slave to the advanced-i18n branch of Genshi.
the linux-py24 slave is still using Genshi 0.5.1 for now.
Trunk is still supposed to work with Genshi 0.5.1, right?
/ Jonas
--~--~-~--~~
Christian Boos wrote:
> It's been a week now, I think we should just release 0.11.2.1 as of
> r7667 (the one-liner fix) asap so that we can move on with 0.11.3
> related work on the 0.11-stable branch.
Yes sorry about that. I've been busy the last few day but I'll try to
take care of that tonigh
Christian Boos wrote:
>
> osimons wrote:
>> On Nov 11, 12:16 pm, Christian Boos <[EMAIL PROTECTED]> wrote:
>>
>>> Not tested, but I expect that setting to be:
>>>
>>> [notification]
>>> mime_encoding = none
>>>
>>
>> Correct - as always :-) So many settings, so little insight...
>>
>
> Well, act
Christian Boos wrote:
>
> Hi,
>
> As someone recently updated the Trac french translation, I thought I
> could have a look at this.
> But that reminded me that the last time I've played with the i18n stuff,
> there were still lots of open points.
>
> That was *6* months ago, and there's been no
Remy Blank wrote:
> The 0.11.2 release is missing an import for "set" in trac/util/html.py.
> Unfortunately, this prevents any wiki formatting from working on Python
> 2.3. It has been reported in:
>
> http://trac.edgewall.org/ticket/7801
>
> I have added the import in 0.11-stable in [7667]. T
Remy Blank wrote:
> Jonas Borgström wrote:
>> To avoid having this release slip even further I propose to release it
>> sometime this weekend. Both Saturday and Sunday works for me, but I need
>> help from someone with the final testing and packaging.
>
> I'm av
Tim Hatch wrote:
>
>>> I guess one workaround would be to replace that character with "..."
>>> when mime_encoding=none.
>
> Yes, and a test to check it.
Does anyone still have anything that should go into 0.11.2?
To avoid having this release slip even further I propose to release it
sometime
Emmanuel Blot wrote:
>
>> That makes the "mime_encoding=none" option look pretty useless.
>
> I have not followed the thread, but AFAIR, mime_encoding=none has been
> requested by/for people who do not want encoding at all - i.e. emit
> pure ASCII for english speakers. Some people were complain
Tim Hatch wrote:
>
>> I have been running [7648] for the last two days on two installations,
>> without any surprises. They are very low-traffic internal sites, so
>> this
>> might not mean much, but it's still an additional data point.
>
> At first glance it looks like [7648] reduced test cover
Christian Boos wrote:
> #6436 works well from my testing, but it's potentially risky (i.e. it
> might break Trac in ways I didn't foresee).
> Wider testing would be good, and as I wrote in that ticket, I'm OK to
> delay it further if needed.
> OTOH, if jonas would update to latest 0.11-stable + th
Hi,
We're a bit behind schedule so it's time to prepare our next maintenance
release 0.11.2:
http://trac.edgewall.org/query?milestone=0.11.2&status=assigned&status=n
ew&status=reopened&group=priority
There's currently 22 open tickets but only 3 marked as priority "high":
#6532 - "email addre
On Jul 22, 7:31 pm, Christian Boos <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Here's a short list of the things I think we can get done in time for
> the upcoming 0.11.1 maintenance release.
>
> First, here are the few remaining tickets I want to fix, all with
> pending patches:
> http://trac.edge
Christian Boos wrote:
> Hello,
>
> There's a patch I'd like to commit on stable before 0.11.1, but first
> I'd like to check if nobody foresees a problem with this, and also if I
> could get some testing feedback, particularly from people still
> experiencing db timeout errors.
>
> This patch sh
Hi,
What about dropping CGI support for 0.12?
It was the first Trac frontend but nowadays it's too slow for almost any
use and also one of the hardest to get working.
/ Jonas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Jeroen Ruigrok van der Werven wrote:
>
> -On [20080702 04:30], Noah Kantrowitz ([EMAIL PROTECTED]) wrote:
>>Anyone remember why the default value for default_charset is
>>'iso-8859-15' instead of 'utf8'? Given how much we hype utf8
>>everywhere else, that would seem a sane default default.
>
> N
Colin Guthrie wrote:
>
> Chris Mulligan wrote:
>> I agree with Noah. What's the problem this is really solving in the
>> real world? Why did you ever need a separate read database?
>
> Not related to this general principle but i recently had to scale up a
> project I was running (totally unrelat
Emmanuel Blot wrote:
>
> I just got a bug report about a plugin which does not work anymore due
> to the numbering scheme used in Trac:
>
> ERROR: Skipping "TracRevtreePlugin 0.5.15dev": (version
> conflict "(Trac 0.11rc2 (/usr/lib64/python2.4/site-
> packages/Trac-0.11rc2-py2.4.egg),
> Requi
John Hampton wrote:
>
> So, if you checkout the 0.11-stable branch, and install it, you get an
> egg labeled something like the following:
>
> Trac-0.11dev_r7237-py2.5.egg
>
> I realize that this is due to the setup.cfg containing:
>
> [egg_info]
> tag_build = dev
>
> Can we change this to `t
Noah Kantrowitz wrote:
>
>
> On Jun 23, 2008, at 1:13 PM, Alec Thomas wrote:
>
>>
>> 2008/6/24 Scott Bussinger <[EMAIL PROTECTED]>:
>>>
Christian has made a very useful report on the popular tickets:
http://trac.edgewall.org/report/32
>>>
>>> This _is_ an interesting report. To make i
Shun-ichi GOTO wrote:
>
> The tarball trac-0.10.5.tar.gz seems to contain some unfamiliar files
> like "._ChangeLog". I guess they are Mac OS related files.
> Are they required to distribute?
No you can safely ignore them.
They are created by my text editor textmate since I forgot to disable
Jani Tiainen wrote:
>
> Now that 0.11 is really finally out I can roll it to my work environment
> - together with SVN 1.5... And break things just before I leave for
> summer vacation :D
>
> Well not really, even as an idea it sounds more than fun for my coworkers...
>
> Now three "outstandi
Christian Boos wrote:
>> I don't have access to Windows to test this right now but can you check
>> if this "regression" is simply due to the fact that the total pool size
>> in your test is smaller with the new code. With the old pool each tracd
>> process would contain two pools (one for each en
Christian Boos wrote:
>> Yeah I think so, since it fixes a few long standing issues especially
>> Trac's bad habit of collecting a large number of databases connections
>> and never releasing them.
>> So unless someone objects I'm planning to commit this to trunk. It's a
>> bit too dangerous to ba
Noah Kantrowitz wrote:
> So apparently I was working on a patch before I packed up to move, and I
>would like it if someone else could glance at this to be sure I didn't
> miss something massive. The patch is to make sure plugins defined in any
>inherited config files at initenv (via --inh
David Abrahams wrote:
> on Sun Jun 01 2008, David Abrahams wrote:
>
>
>> on Sun Jun 01 2008, Jonas Borgström wrote:
>>
>>
>>> Anyway, I've attached my attempt at a process-wide LRU based connection
>>> pool. It's still a work in pr
David Abrahams wrote:
> on Fri May 30 2008, David Abrahams wrote:
>
>>> I have actually been thinking about making Trac use a single global db
>>> pool instead of one pool for each environment in each process.
>> Yep, that's what we need, or something very like it. Of course, each of
>> my env
krkempa wrote:
> Noah's wrote:
>> That kind of huge collection of features might
>> be good for boxing up and shipping to people that want a turnkey
>> solution, but they aren't much use in the Trac community
>
> So anyone who want to have usable Trac flavour needs to make his hand
> dirty and be
David Abrahams wrote:
> We haven't upgraded our Trac in some time, so we're still using a
> slightly older 0.11-dev, but recently we have been having regular --
> often daily -- episodes where our PostgreSQL connection starts throwing
>
>
> File
> "/usr/local/lib/python2.5/site-packages/dja
Emmanuel Blot wrote:
>
>> I think these errors are caused by temporary "normal" server
>> overloading.
>> The traffic on teo is ever increasing and the server is at peak hours
>> approaching max capacity.
>
> Ok, thanks for the feedback, I was wondering whether it could have
> been a regression
Emmanuel Blot wrote:
>
> Hi,
>
> For the last couple of days, I've noticed that Trac on t.e.o. is
> sometimes quite slow to provide a page, and this usually ends up with
> the infamous
> "Trac detected an internal error:
> TimeoutError: Unable to get database connection within 20 seconds"
> erro
Christian Boos wrote:
>
> Hi Jonas,
>
> First, I've noticed that we have now: [spam-filter] min_karma 0
> Wasn't that higher in the past, like "3"? "1" should be the minimum, I
> think (and this would have caught those stupid "haha;" comments from
> this morning...).
I think it was lowered beca
Christian Boos wrote:
>
> Hi Jonas,
>
> It seems I don't have the write permission there.
> Please add it for me and others.
It should work now. I also initialized merge tracking.
> Also, you could take this opportunity to kill the old developer-specific
> branches (cboos-dev, cmlenz-dev, etc.
Noah Kantrowitz wrote:
> Alec Thomas wrote:
>> +1 for the concept of merging this. It will make people happy.
>
> +1 from me too. I see no reason to not continue it in trunk. Progress!
>
+1 from me as well. Proper i18n support has been high on our users' wish
list for a very long time.
/ Jona
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 aff
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.
Jeroen Ruigrok van der Werven wrote:
>
> -On [20080428 10:05], Christian Boos ([EMAIL PROTECTED]) 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 duri
Emmanuel Blot wrote:
>
> I just encountered two major issues while browsing on t.e.o. within a
> single minute time frame:
>
> 1/ When I clicked on "View Ticket/Custom Query" I got a Python
> traceback (plain text, no decoration) reporting that "layout.html" was
> missing. A simple refresh made
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
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
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-de
Christian Boos wrote:
>
> Jonas Borgström wrote:
>> ... Four consecutive
>> "/report/1" requests gives the following output:
>>
>> before render(): 51888 kB
>> after render(): 209456 kB
>> before render(): 208936 kB
>> after render(
Christian Boos wrote:
> Well, I don't see why we should hold off a new intermediate release, as
> the current state is already much better than 0.11b1 memory wise (+
> other minor stuff fixed since then), so I think we should replace the
> downloadable 0.11 version by a newer one.
> I'm OK to not
Hi,
I've been trying to figure out that causing the memory usage issues I
noticed while moving t.e.o to trunk. Since this seems to be limited to
larger trac installations I created a new environment only laptop and
inserted 5000 (t.e.o has almost 7000 tickets) new tickets [1].
With this amoun
Dirk-Willem van Gulik wrote:
>
> Below is a small patch for those using x509 support - e.g. an apache
> config as below to allow
> access based on x509 certs. The reason for doing this is that
> otherwise the strings shown become
> very long and wieldy.
I haven't used this myself but isn't this
Christian Boos wrote:
>
> Jonas Borgström wrote:
>> Christian Boos wrote:
>>
>>> Jeroen Ruigrok van der Werven wrote:
>>>
>>>> -On [20080307 04:31], John Hampton ([EMAIL PROTECTED]) wrote:
>>>>
>>>>
>>>>> D
Christian Boos wrote:
>
> Jeroen Ruigrok van der Werven wrote:
>> -On [20080307 04:31], John Hampton ([EMAIL PROTECTED]) wrote:
>>
>>> Do you think it's possible to have a 0.11b2 release before PyCon?
>>>
>>
>> Jonas will be testing trunk on t.e.o. this weekend he said.
t.e.o has now been runnin
Filip Rembiałkowski wrote:
>
> Hi trac developers :)
>
> we have just wasted a day of our deploy manager time :)
>
> so I decided to let you know, that trac is broken under following
> conditions:
>
> - using postgresql 8.2 or later with configuration setting
> standard_conforming_strings = on
Jeroen Ruigrok van der Werven wrote:
>
> -On [20080109 16:56], David Abrahams ([EMAIL PROTECTED]) wrote:
>>I think we already found and submitted a patch for this problem:
>>http://trac.edgewall.org/ticket/6581
>
> It's in trunk now, r6385.
>
> Perhaps Noah and Jonas can also give this latest t
FYI t.e.o is now running 0.10 again since 0.11 apparently has some
memory usage issues. Last night the server grinded to a halt when a
bunch of trac fcgi processes each allocating more than 600MB resident
memory.
I've not yet identified which pages require this much memory but I would
not be
Hi,
I've just upgraded t.e.o to Trac 0.11 beta1. So far everything appears
to be working but please let me know if you notice anything broken by
this change.
Cheers,
Jonas
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Christian Boos wrote:
>
> Jonas Borgström wrote:
>> Christian Boos wrote:
>>
>>> Hi,
>>>
>>> Another call for doing it a 0.11-beta1 release this Monday.
>>> I propose a freeze for the beta1 on revision r6333, if jonas and cmlenz
>>&g
Christian Boos wrote:
>
> Hi,
>
> Another call for doing it a 0.11-beta1 release this Monday.
> I propose a freeze for the beta1 on revision r6333, if jonas and cmlenz
> are OK, they can set the version and tag it.
I can help with the actual release tomorrow or on Monday, but on Monday
I'm onl
Christian Boos wrote:
> Now, I'll focus mostly on the documentation, so that we will at least
> have /some/ documentation go in the beta1. That beta1 version can be
> released in a few days if everything goes well. At that point, t.e.o
> could be upgraded to that version. Then we can start to figh
Christian Boos wrote:
> Well, that would do for the default permission policy. There should be
> at least some additional cleanup done at a larger interval to clear the
> whole cache, so that it doesn't explode over time if the server stays
> alive for long periods of time.
>
> New version of the
Hi,
While porting the t.e.o theme to Trac trunk I noticed that the /roadmap
is very slow, and it takes at least 1.5-2 seconds to render that page.
Almost all of that time is apparently spent by the permission system
making sure the user isn't shown any ticket he/she isn't supposed to
see:
(r
Emmanuel Blot wrote:
>
>> Has there been thought given to adding Expires headers to our images and css
>> files in order to reduce load times of Trac installs?
>
> To reduce load times, it is probably more effective to let Apache (or
> whichever HTTP server) serve the static files (images, css,
Christian Boos wrote:
>
> Hi all,
>
> Odd Simon Simonsen has been contributing quite regularly high quality
> patches and feedback and I think he's quite at ease now with the Trac
> code base and in line with the Trac philosophy (well, whatever that
> latter thing is ;-) ), that's why I'd like t
Christian Boos wrote:
>
> Jeroen Ruigrok van der Werven wrote:
>> Folks,
>>
>> I was in the process of committing an updated notification.py in Trac trunk
>> and it unfortunately failed.
>> It seems my rights are confined to the sandbox.
>>
>> Following up on Alec's suggestion I post here to ask
Christopher Lenz wrote:
> 1) Too many changes with too much impact
Agreed. Hopefully the development policy we discussed earlier on trac-
dev in combination with more focus "release early release often" will
help us avoid similar problems in the future.
> 2) Too many API changes without much b
Hi,
Yesterday a new certificate was installed on svn.edgewall.org. So it's
safe to ignore certificate warnings, at least as long as the following
fingerprints match:
Fingerprints:
SHA1: D2 20 FB CE 5A 13 E4 1E F5 24 EA B1 14 3D FA F2 C1 69 EB 71
MD5: B2 27 D4 F9 44 D4 14 A0 74 E5 74 24 6B 65
Eli wrote:
> Seeking to improve software quality and move toward a solid 0.11 release, the
> following developer policy is proposed:
>
> 1 Anything beyond a 'trivial' bugfix requires a branch.
> 2 A branch must be reviewed and approved by another developer before merging
> to trunk. If somet
Jeroen Ruigrok van der Werven wrote:
> Hi Jonas,
>
> -On [20070624 15:05], Jonas Borgström ([EMAIL PROTECTED]) wrote:
>> I just checked out the i18n branch to add the Swedish translation of
>> Trac. I noticed that trac/locale/ directory already contains a bunch of
>&g
Hi,
I just checked out the i18n branch to add the Swedish translation of
Trac. I noticed that trac/locale/ directory already contains a bunch of
empty locale directories, all using "long" locale names ("sv_SE" instead
of just "sv" for example).
Shouldn't we be using the shorter names here?
B
Hi,
I just checked out the i18n branch to add the Swedish translation of
Trac. I noticed that trac/locale/ directory already contains a bunch of
empty locale directories, all using "long" locale names ("sv_SE" instead
of just "sv" for example).
Shouldn't we be using the shorter names here?
B
1 - 100 of 131 matches
Mail list logo
