From brett at python.org  Fri Aug  3 22:45:04 2007
From: brett at python.org (Brett Cannon)
Date: Fri, 3 Aug 2007 13:45:04 -0700
Subject: [Tracker-discuss] SF export now working?
Message-ID: <bbaeab100708031345r7071e5ceo7b4942486a0047a9@mail.gmail.com>

Has anyone managed to download an export since the SF update that is
actually complete and valid XML?  I just moved and personal life is
extremely turbulent right now so I can't do this myself.

-Brett

From forsberg at efod.se  Mon Aug  6 09:12:18 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Mon, 6 Aug 2007 09:12:18 +0200
Subject: [Tracker-discuss] SF export now working?
In-Reply-To: <bbaeab100708031345r7071e5ceo7b4942486a0047a9@mail.gmail.com>
References: <bbaeab100708031345r7071e5ceo7b4942486a0047a9@mail.gmail.com>
Message-ID: <200708060912.18182.forsberg@efod.se>

fredag 03 augusti 2007 22:45 skrev Brett Cannon:
> Has anyone managed to download an export since the SF update that is
> actually complete and valid XML?  

I just made a test, and.. well, this is beginning to look like a brazilian 
soap opera or something. See my most recent comment on: 

https://sourceforge.net/tracker/index.php?func=detail&aid=1687916&group_id=1&atid=200001

Download "by proxy", that is via Martin's subscription, probably still work, 
though. Let's see if "Ross Turk" hands me a subscription, that will make the 
process smoother.

> I just moved and personal life is 
> extremely turbulent right now so I can't do this myself.

Oh, moving.. that can really mess things up!

Regards,
\EF
-- 
http://efod.se/

From martin at v.loewis.de  Mon Aug  6 09:34:43 2007
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Mon, 06 Aug 2007 09:34:43 +0200
Subject: [Tracker-discuss] SF export now working?
In-Reply-To: <200708060912.18182.forsberg@efod.se>
References: <bbaeab100708031345r7071e5ceo7b4942486a0047a9@mail.gmail.com>
	<200708060912.18182.forsberg@efod.se>
Message-ID: <46B6CF13.7090807@v.loewis.de>

> Download "by proxy", that is via Martin's subscription, probably still work, 
> though. 

Indeed it does. If we want to transition the tracker now (say, this week
or next week), we can probably well use my subscription. We just arrange
for a date and time for a switchover.

I found that the new exporter has a feature "export only items modified
since UTC time", we can probably use that to detect what changes people
make after the switchover.

Regards,
Martin


From metatracker at psf.upfronthosting.co.za  Mon Aug  6 22:14:08 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Mon, 06 Aug 2007 20:14:08 -0000
Subject: [Tracker-discuss] [issue1] Import history
Message-ID: <1186431248.42.0.985216104726.issue1@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

The importer now records the linking of msg and file items in the history of the
msg and file items - this makes it easier to find the issue a msg or file is
related to.

_____________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue1>
_____________________________________________________

From brett at python.org  Mon Aug  6 22:36:53 2007
From: brett at python.org (Brett Cannon)
Date: Mon, 6 Aug 2007 13:36:53 -0700
Subject: [Tracker-discuss] SF export now working?
In-Reply-To: <46B6CF13.7090807@v.loewis.de>
References: <bbaeab100708031345r7071e5ceo7b4942486a0047a9@mail.gmail.com>
	<200708060912.18182.forsberg@efod.se> <46B6CF13.7090807@v.loewis.de>
Message-ID: <bbaeab100708061336u6fa3dc29n9d38874d43440873@mail.gmail.com>

On 8/6/07, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> > Download "by proxy", that is via Martin's subscription, probably still work,
> > though.
>
> Indeed it does. If we want to transition the tracker now (say, this week
> or next week), we can probably well use my subscription. We just arrange
> for a date and time for a switchover.

This sounds reasonable.  If Ross Turk doesn't reply to Erik within a
reasonable time frame and this is resolved within the week (by Aug
13), we just use Martin as a proxy for the switchover and take SF out
of the scheduling picture.

I will start a separate email thread to see what is exactly left to switch.

-Brett

From brett at python.org  Mon Aug  6 22:43:06 2007
From: brett at python.org (Brett Cannon)
Date: Mon, 6 Aug 2007 13:43:06 -0700
Subject: [Tracker-discuss] What *has* to be done for the tracker switch-over?
Message-ID: <bbaeab100708061343u7f9c07bchc8bcbf623bfa6add@mail.gmail.com>

Let's see if we can't get things pulled together for a switchover no
later than the end of this month (early if possible).  With the
fallback of having Martin generate the dump, the only thing truly
holding us up is making sure all loose ends to tied up.

The meta tracker has two critical issues and three bugs open at the
moment.  None of them look huge; biggest are probably updating the
tracker docs on the wiki and fixing the redirector.

After that I would assume choosing a date and time that work for
people would be next.  I am honestly not worried about shutting the
tracker down during business hours as SF has done that to us so many
times and I care about about convenience for the people involved.

Once we have a date and time chosen I can email out an announcement.

Anyway, let's see if we can't actually get this sucker finished!

-Brett

From metatracker at psf.upfronthosting.co.za  Tue Aug  7 08:16:12 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Tue, 07 Aug 2007 06:16:12 -0000
Subject: [Tracker-discuss] [issue110] Showstopper: sf.net is generating
	invalid XML
Message-ID: <1186467371.92.0.191957042153.issue110@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

As detailed in msg638, the importer has been rewritten and seems to work.
However, I would appreciate if someone else did some testing to make sure the
data imported is correct. 

So, if somebody could visit their favorite issues and compare them to the data
in the sourceforge tracker, that would be good.

----------
assignedto:  -> forsberg
status: chatting -> testing

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue110>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Aug  7 08:26:16 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Tue, 07 Aug 2007 06:26:16 -0000
Subject: [Tracker-discuss] [issue122] Remove test users
Message-ID: <1186467975.38.0.471840782771.issue122@psf.upfronthosting.co.za>


New submission from Erik Forsberg:

There are currently three test users added to the database at initialization
time. They should be removed before we go into production mode.

----------
assignedto: forsberg
messages: 653
nosy: forsberg
priority: bug
status: chatting
title: Remove test users

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue122>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Aug  7 08:45:36 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Tue, 07 Aug 2007 06:45:36 -0000
Subject: [Tracker-discuss] [issue110] Showstopper: sf.net is generating
	invalid XML
Message-ID: <1186469135.69.0.0120225972883.issue110@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

I propose that we announce a period for public inspection, e.g. starting today,
ending a week from now (or some such), on python-dev. We will have to announce
the switchover data in advance, anyway.

Wrt. the current installation, I'm puzzled what precisely the export file was
that you installed. If I sort by id descending, the most recent issue seems to
be 1573931, created 10 months ago. In the real data, 1734346 should be present
(and I do find it in XML file).

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue110>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Aug  7 08:46:36 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Tue, 07 Aug 2007 06:46:36 -0000
Subject: [Tracker-discuss] [issue95] Tracker should include a link to meta
	tracker
Message-ID: <1186469196.12.0.547841578102.issue95@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

There's now a "Report Tracker Problem" link in the "Help" section.

----------
assignedto:  -> forsberg
nosy: +forsberg
status: unread -> resolved

______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue95>
______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Aug  7 08:58:32 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Tue, 07 Aug 2007 06:58:32 -0000
Subject: [Tracker-discuss] [issue110] Showstopper: sf.net is generating
	invalid XML
In-Reply-To: <1186469135.69.0.0120225972883.issue110@psf.upfronthosting.co.za> (Martin v. Löwis's message of "Tue, 07 Aug 2007 06:45:36 -0000")
Message-ID: <87odhjn853.fsf@uterus.efod.se>


Erik Forsberg added the comment:

"Martin v. L?wis" <metatracker at psf.upfronthosting.co.za> writes:

> I propose that we announce a period for public inspection,
> e.g. starting today, ending a week from now (or some such), on
> python-dev. We will have to announce the switchover data in advance,
> anyway.

Sounds like a good idea. 

> Wrt. the current installation, I'm puzzled what precisely the export
> file was that you installed. If I sort by id descending, the most
> recent issue seems to be 1573931, created 10 months ago. In the real
> data, 1734346 should be present (and I do find it in XML file).

It's currently doing a re-import (to get some more history into the
msg and file instances) of the xml file from 2007-07-24. If you wait
an hour or so, 1734346 probably will appear.

When this import is finished, I'm thinking about getting a newer
snapshot, mangle it through your character set thingie, and then do a
re-import to get a fresh set of test data for people to inspect. Then
we can announce the test period.

I should be able to do all this during the day. 

\EF
-- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue110>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Aug  7 20:20:23 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Tue, 07 Aug 2007 18:20:23 -0000
Subject: [Tracker-discuss] [issue92] Activate email sending
Message-ID: <1186510823.11.0.798360345768.issue92@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

I just verified that mail is sent and received both by the new-bugs-announce and
the python-bugs list.

----------
status: chatting -> resolved

______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue92>
______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Aug  8 07:44:57 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Wed, 08 Aug 2007 05:44:57 -0000
Subject: [Tracker-discuss] [issue110] Showstopper: sf.net is generating
	invalid XML
Message-ID: <1186551897.41.0.629717234935.issue110@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

Made a new import, including fixsfmojibake, yesterday evening, so now the
tracker is loaded with data from yesterday.

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue110>
_______________________________________________________

From forsberg at efod.se  Wed Aug  8 07:59:13 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Wed, 08 Aug 2007 07:59:13 +0200
Subject: [Tracker-discuss] What *has* to be done for the tracker
	switch-over?
In-Reply-To: <bbaeab100708061343u7f9c07bchc8bcbf623bfa6add@mail.gmail.com>
	(Brett Cannon's message of "Mon, 6 Aug 2007 13:43:06 -0700")
References: <bbaeab100708061343u7f9c07bchc8bcbf623bfa6add@mail.gmail.com>
Message-ID: <87vebqlg7i.fsf@uterus.efod.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Brett Cannon" <brett at python.org> writes:

> Let's see if we can't get things pulled together for a switchover no
> later than the end of this month (early if possible).  With the
> fallback of having Martin generate the dump, the only thing truly
> holding us up is making sure all loose ends to tied up.
>
> The meta tracker has two critical issues 

I closed one of them yesterday. The one remaining is:

110: Showstopper: sf.net is generating invalid XML

     - Basically done, but I would appreciate if somebody who is not
       me did check the output, i.e. what is now on bugs.python.org,
       to make sure we catch any obvious bugs in the new importer.

       A "public inspection" period as proposed by Martin is one way
       to do it.

>and three bugs open 

Actually, there are, uhm, were four of them:

 36: Rewrite sf bug redirector at python.org

     - This issue is, AFAIK, only there to remind us that this should
       be done at switchover. 

       It needs to be done by someone with access to the webserver
       serving python.org, and that someone is not me. On the other
       hand, if doing this is delayed a day or so, that should be no
       large problem (I think).

 95: Link to meta tracker. I just fixed that. 

119: Tracker Documentation

     - Should be no problem for someone on this list to fix. 

122: Remove test users

     - A reminder for me to make sure I don't forget it when we do the
       switchover.

> After that I would assume choosing a date and time that work for
> people would be next.  I am honestly not worried about shutting the
> tracker down during business hours as SF has done that to us so many
> times and I care about about convenience for the people involved.

I would prefer doing it a weekday afternoon/evening. I'm on CEST which
is GMT+2, and I'll be happiest if my part of the work is completed
before 22:00 (10 in the evening for you AM/PM people).

Downloading a new snapshot from sf (I can _finally_ do that now, after
they have given me a free subscription) seems to take about 20
minutes. Running the import takes 60-90 minutes. 

Reading http://wiki.python.org/moin/TrackerTransition, steps 1-5 are
either done or better done by someone else. Step 6 I can do.

I don't know if I have the privileges to do step 7, but I think so.

Steps 8-11 I can do as well. 

Step 12 needs to be done with someone that has access to the python
web servers. Not me. There's also the additional step of fixing the sf
bug redirector.

Step 13. Hmm.. :-).

Who will do the python.org-webserver stuff, and what timezone is this
person living in? 

Regards,
\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGuVuxrJurFAusidkRAgx1AJ9i2tzraU7hzNuHItLY9jVq6jYIagCgtJ+Y
ruoE0q1X8V01VPDJ710zjeI=
=C6ik
-----END PGP SIGNATURE-----

From martin at v.loewis.de  Wed Aug  8 09:13:38 2007
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 08 Aug 2007 09:13:38 +0200
Subject: [Tracker-discuss] What *has* to be done for the
	tracker	switch-over?
In-Reply-To: <87vebqlg7i.fsf@uterus.efod.se>
References: <bbaeab100708061343u7f9c07bchc8bcbf623bfa6add@mail.gmail.com>
	<87vebqlg7i.fsf@uterus.efod.se>
Message-ID: <46B96D22.8070709@v.loewis.de>

> Who will do the python.org-webserver stuff, and what timezone is this
> person living in? 

I can do that; I'm in the same timezone. However, it's not really
necessary to find *all* references to the sf tracker at once; if
some remain, people will tell us (I guess there are also some in
the Wiki, and so on).

As for step 7, I could also do that; one should also put warning
signs into the top of each tracker page that the tracker is unused.

Regards,
Martin

From izak at upfrontsystems.co.za  Wed Aug  8 12:21:58 2007
From: izak at upfrontsystems.co.za (Izak Burger)
Date: Wed, 08 Aug 2007 12:21:58 +0200
Subject: [Tracker-discuss] What *has* to be done for
	the	tracker	switch-over?
In-Reply-To: <46B96D22.8070709@v.loewis.de>
References: <bbaeab100708061343u7f9c07bchc8bcbf623bfa6add@mail.gmail.com>	<87vebqlg7i.fsf@uterus.efod.se>
	<46B96D22.8070709@v.loewis.de>
Message-ID: <46B99946.8060207@upfrontsystems.co.za>

I'm just thinking of something right now that might need attention.  Way 
back (http://psf.upfronthosting.co.za/roundup/meta/issue92) we set up 
status at bugs.python.org to bounce with a custom message.  The summary 
comes from this address though.

Here is the problem.  Some mail servers do call-backs, specifically, I 
know one of the bigger ISP's in this country (mweb.co.za) do this.  I am 
sure there are many more out there.  If you send mail with a return path 
of status at bugs.python.org, their mail server will connect back to you 
and verify the address.  If you bounce the message (which we do), it 
refuses to accept your mail.

We may have to change status at bugs.python.org to go to /dev/null instead.

regards,
Izak

From martin at v.loewis.de  Wed Aug  8 19:16:22 2007
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 08 Aug 2007 19:16:22 +0200
Subject: [Tracker-discuss] What *has* to be done for
	the	tracker	switch-over?
In-Reply-To: <46B99946.8060207@upfrontsystems.co.za>
References: <bbaeab100708061343u7f9c07bchc8bcbf623bfa6add@mail.gmail.com>	<87vebqlg7i.fsf@uterus.efod.se>
	<46B96D22.8070709@v.loewis.de>
	<46B99946.8060207@upfrontsystems.co.za>
Message-ID: <46B9FA66.4030102@v.loewis.de>

> We may have to change status at bugs.python.org to go to /dev/null instead.

This is a difficult change to make; all changes to the email
infrastructure are difficult to make.

Regards,
Martin

From forsberg at efod.se  Wed Aug  8 19:41:51 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Wed, 08 Aug 2007 19:41:51 +0200
Subject: [Tracker-discuss] What *has* to be done for
	the	tracker	switch-over?
In-Reply-To: <46B9FA66.4030102@v.loewis.de> (Martin v. =?iso-8859-1?Q?L=F6?=
	=?iso-8859-1?Q?wis's?= message of
	"Wed, 08 Aug 2007 19:16:22 +0200")
References: <bbaeab100708061343u7f9c07bchc8bcbf623bfa6add@mail.gmail.com>
	<87vebqlg7i.fsf@uterus.efod.se> <46B96D22.8070709@v.loewis.de>
	<46B99946.8060207@upfrontsystems.co.za> <46B9FA66.4030102@v.loewis.de>
Message-ID: <87r6mdly8w.fsf@uterus.efod.se>

"Martin v. L?wis" <martin at v.loewis.de> writes:

>> We may have to change status at bugs.python.org to go to /dev/null instead.
>
> This is a difficult change to make; all changes to the email
> infrastructure are difficult to make.

Umm.. why is that? To me, this looks like an addition to the alias
file at psf.upfronthosting.co.za, as bugs.python.org is MX for itself. 

\EF
-- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9

From brett at python.org  Wed Aug  8 20:12:26 2007
From: brett at python.org (Brett Cannon)
Date: Wed, 8 Aug 2007 11:12:26 -0700
Subject: [Tracker-discuss] What *has* to be done for the tracker
	switch-over?
In-Reply-To: <87vebqlg7i.fsf@uterus.efod.se>
References: <bbaeab100708061343u7f9c07bchc8bcbf623bfa6add@mail.gmail.com>
	<87vebqlg7i.fsf@uterus.efod.se>
Message-ID: <bbaeab100708081112j724dddb2pd1fb0c84ec8c8689@mail.gmail.com>

On 8/7/07, Erik Forsberg <forsberg at efod.se> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> "Brett Cannon" <brett at python.org> writes:
>
> > Let's see if we can't get things pulled together for a switchover no
> > later than the end of this month (early if possible).  With the
> > fallback of having Martin generate the dump, the only thing truly
> > holding us up is making sure all loose ends to tied up.
> >
> > The meta tracker has two critical issues
>
> I closed one of them yesterday. The one remaining is:
>
> 110: Showstopper: sf.net is generating invalid XML
>
>      - Basically done, but I would appreciate if somebody who is not
>        me did check the output, i.e. what is now on bugs.python.org,
>        to make sure we catch any obvious bugs in the new importer.
>
>        A "public inspection" period as proposed by Martin is one way
>        to do it.
>

I think that is best.  Just distribute the work so we get a somewhat
random sampling of checks.

> >and three bugs open
>
> Actually, there are, uhm, were four of them:
>
>  36: Rewrite sf bug redirector at python.org
>
>      - This issue is, AFAIK, only there to remind us that this should
>        be done at switchover.
>
>        It needs to be done by someone with access to the webserver
>        serving python.org, and that someone is not me. On the other
>        hand, if doing this is delayed a day or so, that should be no
>        large problem (I think).
>

I don't have the proper access for this, but Martin was kind enough to
step forward on this.

>  95: Link to meta tracker. I just fixed that.
>
> 119: Tracker Documentation
>
>      - Should be no problem for someone on this list to fix.
>

I am hoping to do this, but help would obviously be great.

> 122: Remove test users
>
>      - A reminder for me to make sure I don't forget it when we do the
>        switchover.
>
> > After that I would assume choosing a date and time that work for
> > people would be next.  I am honestly not worried about shutting the
> > tracker down during business hours as SF has done that to us so many
> > times and I care about about convenience for the people involved.
>
> I would prefer doing it a weekday afternoon/evening. I'm on CEST which
> is GMT+2, and I'll be happiest if my part of the work is completed
> before 22:00 (10 in the evening for you AM/PM people).
>
> Downloading a new snapshot from sf (I can _finally_ do that now, after
> they have given me a free subscription) seems to take about 20
> minutes. Running the import takes 60-90 minutes.
>

So it sounds like a three hour process (using a margin to cover all
the other random steps).

> Reading http://wiki.python.org/moin/TrackerTransition, steps 1-5 are
> either done or better done by someone else. Step 6 I can do.
>
> I don't know if I have the privileges to do step 7, but I think so.
>
> Steps 8-11 I can do as well.
>
> Step 12 needs to be done with someone that has access to the python
> web servers. Not me. There's also the additional step of fixing the sf
> bug redirector.
>
> Step 13. Hmm.. :-).

Celebrate!

-Brett

From brett at python.org  Wed Aug  8 20:14:26 2007
From: brett at python.org (Brett Cannon)
Date: Wed, 8 Aug 2007 11:14:26 -0700
Subject: [Tracker-discuss] What *has* to be done for the tracker
	switch-over?
In-Reply-To: <46B96D22.8070709@v.loewis.de>
References: <bbaeab100708061343u7f9c07bchc8bcbf623bfa6add@mail.gmail.com>
	<87vebqlg7i.fsf@uterus.efod.se> <46B96D22.8070709@v.loewis.de>
Message-ID: <bbaeab100708081114q11ea3831q782143fc57774555@mail.gmail.com>

On 8/8/07, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> > Who will do the python.org-webserver stuff, and what timezone is this
> > person living in?
>
> I can do that; I'm in the same timezone. However, it's not really
> necessary to find *all* references to the sf tracker at once; if
> some remain, people will tell us (I guess there are also some in
> the Wiki, and so on).
>


Great!  I will let the two of you decide on a date and time then.  I
will also make sure to be online (I am PT and so puts me at -7/-8
UTC).  Don't know what use I will be, though.  =)

-Brett

From martin at v.loewis.de  Wed Aug  8 20:28:51 2007
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 08 Aug 2007 20:28:51 +0200
Subject: [Tracker-discuss] What *has* to be done for
	the	tracker	switch-over?
In-Reply-To: <87r6mdly8w.fsf@uterus.efod.se>
References: <bbaeab100708061343u7f9c07bchc8bcbf623bfa6add@mail.gmail.com>	<87vebqlg7i.fsf@uterus.efod.se>
	<46B96D22.8070709@v.loewis.de>	<46B99946.8060207@upfrontsystems.co.za>
	<46B9FA66.4030102@v.loewis.de> <87r6mdly8w.fsf@uterus.efod.se>
Message-ID: <46BA0B63.10702@v.loewis.de>

>>> We may have to change status at bugs.python.org to go to /dev/null instead.
>> This is a difficult change to make; all changes to the email
>> infrastructure are difficult to make.
> 
> Umm.. why is that? To me, this looks like an addition to the alias
> file at psf.upfronthosting.co.za, as bugs.python.org is MX for itself. 

Ah, ok. Then all is fine. I thought this had to be done on
mail.python.org

Regards,
Martin

From brett at python.org  Wed Aug  8 22:28:12 2007
From: brett at python.org (Brett Cannon)
Date: Wed, 8 Aug 2007 13:28:12 -0700
Subject: [Tracker-discuss] Please help verify SF data dump imported into
	(future) new tracker
Message-ID: <bbaeab100708081328v70d0fc28v1c69e74e3895bd68@mail.gmail.com>

We are getting very close to moving over to the new tracker (hopefully
by the end of the month; no firm date yet, though, as we are still
planning things out)!

Part of the transition is taking a data dump provided by SourceForge
and loading it into our Roundup instance.  But we need to make some
effort to make sure SF's data dump is accurate and that our import is
good.

If you can, please go to SourceForge and choose some issue (bug,
patch, whatever), and then look up the corresponding issue at
http://bugs.python.org/ .  If there is any discrepancy, please report
it at http://psf.upfronthosting.co.za/roundup/meta (the link is also
listed at the new tracker as where to report tracker problems) or to
this email.

-Brett

P.S.: If you want to help with the transitionin other ways, you can
also help with the tracker docs at
http://wiki.python.org/moin/TrackerDocs.

From metatracker at psf.upfronthosting.co.za  Thu Aug  9 02:21:53 2007
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Thu, 09 Aug 2007 00:21:53 -0000
Subject: [Tracker-discuss] [issue123] Have issue ID search work from "search
	tracker" box
Message-ID: <1186618913.24.0.852272975879.issue123@psf.upfronthosting.co.za>


New submission from Brett C.:

It would be nice if someone entered an issue ID into the "search tracker" box it
returned the issue with the matching ID.  I know there is a "show issue" box for
that but it is not as visible as the "search tracker" box.

----------
messages: 659
nosy: brettcannon
priority: feature
status: unread
title: Have issue ID search work from "search tracker" box

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue123>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug  9 02:24:43 2007
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Thu, 09 Aug 2007 00:24:43 -0000
Subject: [Tracker-discuss] [issue124] Display file description for files
	pulled from SF
Message-ID: <1186619083.6.0.378301894908.issue124@psf.upfronthosting.co.za>


New submission from Brett C.:

The description for files from SF does not seem to be shown in the import.  This
can be important as the comments often contain what is different between two
files that are named the same.

----------
messages: 660
nosy: brettcannon
priority: bug
status: unread
title: Display file description for files pulled from SF
topic: roundup_deviation

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue124>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug  9 02:34:12 2007
From: metatracker at psf.upfronthosting.co.za (Guido van Rossum)
Date: Thu, 09 Aug 2007 00:34:12 -0000
Subject: [Tracker-discuss] [issue126] show description from imported SF
	attachments
Message-ID: <1186619651.89.0.117223089326.issue126@psf.upfronthosting.co.za>


New submission from Guido van Rossum:

SF attachments have a description, which is often useful, sometimes needed to
disambiguate.  This needs to be imported and shown in tracker UI.  (I'd also
like to be able to add a description to new attachments but that's perhaps a
feature request.)

----------
messages: 661
nosy: guido
priority: bug
status: unread
title: show description from imported SF attachments

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue126>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug  9 05:14:01 2007
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Thu, 09 Aug 2007 03:14:01 -0000
Subject: [Tracker-discuss] [issue127] not properly htmlizing links
Message-ID: <1186629241.03.0.956600865142.issue127@psf.upfronthosting.co.za>


New submission from Raghuram Devarakonda:

I looked at 1720897 which has a link (http://www.python.org/sf/1668596) in the
description. The new tracker htmlized the whole link including the period
following it. The result is that if one can not follow the link. I think
trailing "." should be ignored. Please note that I am not sure whether this can
be called a bug even though I noticed most mail readers do properly handle this
case.

----------
messages: 662
nosy: draghuram
priority: bug
status: unread
title: not properly htmlizing links

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue127>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug  9 07:27:45 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 09 Aug 2007 05:27:45 -0000
Subject: [Tracker-discuss] [issue127] not properly htmlizing links
Message-ID: <1186637265.31.0.419682361432.issue127@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

This doesn't have to be fixed before the switch, as the markup is not in the
database, but is added during rendering.

To fix it, templating.py:StringHTMLProperty.hyper_re needs to be fixed. It
currently reads

    hyper_re = re.compile(r'((?P<url>\w{3,6}://\S+)|'
                          r'(?P<email>[-+=%/\w\.]+@[\w\.\-]+)|'
                          r'(?P<item>(?P<class>[A-Za-z_]+)(\s*)(?P<id>\d+)))')

I think changing that to

    hyper_re = re.compile(r'((?P<url>\w{3,6}://\S+[\w/])|'
                          r'(?P<email>[-+=%/\w\.]+@[\w\.\-]+)|'
                          r'(?P<item>(?P<class>[A-Za-z_]+)(\s*)(?P<id>\d+)))')

should do the trick, i.e. requiring that an URL ends with a letter, digit,
underscore or slash.

----------
status: unread -> chatting

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue127>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug  9 07:39:24 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 09 Aug 2007 05:39:24 -0000
Subject: [Tracker-discuss] [issue126] show description from imported SF
	attachments
Message-ID: <1186637964.61.0.309418807842.issue126@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

If I remember our usage of priority correctly, this should be "urgent", as it
needs to be fixed before the importing.

My proposal is that the File class gets a description field rendered both in the
file view and the item view, and that the content type (type field) is not
displayed in the item display.

----------
priority: bug -> urgent
status: unread -> chatting

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue126>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug  9 07:54:14 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Thu, 09 Aug 2007 05:54:14 -0000
Subject: [Tracker-discuss] [issue124] Display file description for files
	pulled from SF
Message-ID: <1186638854.09.0.536814606819.issue124@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

Duplicate of issue126, resolving.

----------
status: unread -> resolved
topic:  -roundup_deviation

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue124>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug  9 07:54:55 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Thu, 09 Aug 2007 05:54:55 -0000
Subject: [Tracker-discuss] [issue126] show description from imported SF
	attachments
Message-ID: <1186638895.5.0.0182041567939.issue126@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

The data is present in the export, so this should be no biggie to fix.

----------
assignedto:  -> forsberg
nosy: +brettcannon, forsberg

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue126>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug  9 07:55:44 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Thu, 09 Aug 2007 05:55:44 -0000
Subject: [Tracker-discuss] [issue127] not properly htmlizing links
Message-ID: <1186638944.0.0.00461995895385.issue127@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

Lowering priority - I agree that it doesn't have to be fixed before the switch.

----------
priority: bug -> feature
topic: +roundup_deviation

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue127>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug  9 11:13:23 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Thu, 09 Aug 2007 09:13:23 -0000
Subject: [Tracker-discuss] [issue127] not properly htmlizing links
In-Reply-To: <1186637265.31.0.419682361432.issue127@psf.upfronthosting.co.za>
Message-ID: <46BADABB.6030506@gmx.net>


Georg Brandl added the comment:

Martin v. L?wis schrieb:
> Martin v. L?wis added the comment:
> 
> This doesn't have to be fixed before the switch, as the markup is not in the
> database, but is added during rendering.
> 
> To fix it, templating.py:StringHTMLProperty.hyper_re needs to be fixed. It
> currently reads
> 
>     hyper_re = re.compile(r'((?P<url>\w{3,6}://\S+)|'
>                           r'(?P<email>[-+=%/\w\.]+@[\w\.\-]+)|'
>                           r'(?P<item>(?P<class>[A-Za-z_]+)(\s*)(?P<id>\d+)))')
> 
> I think changing that to
> 
>     hyper_re = re.compile(r'((?P<url>\w{3,6}://\S+[\w/])|'
>                           r'(?P<email>[-+=%/\w\.]+@[\w\.\-]+)|'
>                           r'(?P<item>(?P<class>[A-Za-z_]+)(\s*)(?P<id>\d+)))')
> 
> should do the trick, i.e. requiring that an URL ends with a letter, digit,
> underscore or slash.

While you're at it, could you please make the last line
   r'(?P<item>(?P<class>[A-Za-z_]+|#)(\s*)(?P<id>\d+)))'

(and default "class" to "issue") to resolve #103 too?

Georg

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue127>
_______________________________________________________

From constant.beta at gmail.com  Thu Aug  9 14:33:22 2007
From: constant.beta at gmail.com (=?ISO-8859-2?Q?Micha=B3_Kwiatkowski?=)
Date: Thu, 9 Aug 2007 14:33:22 +0200
Subject: [Tracker-discuss] Unsupported configuration option
	SPAMBAYES_SPAM_CUTOFF
Message-ID: <5e8b0f6b0708090533g1cab260eje32b1a8828d07205@mail.gmail.com>

Hi,

I updated my checkout directory today and my testing python-dev
roundup instance doesn't work anymore. I get an exception listed
below. Did I miss a configuration variable? If yes where should I
define it? Or maybe this is a bug? Exception follows.

EXCEPTION AT Thu Aug  9 13:58:29 2007
Traceback (most recent call last):
  File "/usr/lib/python2.5/site-packages/roundup/scripts/roundup_server.py",
line 106, in run_cgi
    self.inner_run_cgi()
  File "/usr/lib/python2.5/site-packages/roundup/scripts/roundup_server.py",
line 266, in inner_run_cgi
    tracker.Client(tracker, self, env).main()
  File "/usr/lib/python2.5/site-packages/roundup/cgi/client.py", line
214, in main
    self.inner_main()
  File "/usr/lib/python2.5/site-packages/roundup/cgi/client.py", line
304, in inner_main
    self.serve_file(designator)
  File "/usr/lib/python2.5/site-packages/roundup/cgi/client.py", line
663, in serve_file
    classname, 'content', nodeid):
  File "/usr/lib/python2.5/site-packages/roundup/security.py", line
181, in hasPermission
    userid, itemid):
  File "/usr/lib/python2.5/site-packages/roundup/security.py", line 51, in test
    if not self.check(db, userid, itemid):
  File "/checkouts/tracker/instances/python-dev/schema.py", line 163,
in __call__
    cutoff_score = float(db.config.detectors['SPAMBAYES_SPAM_CUTOFF'])
  File "/usr/lib/python2.5/site-packages/roundup/configuration.py",
line 1039, in __getitem__
    return self._get_option(name).get()
  File "/usr/lib/python2.5/site-packages/roundup/configuration.py",
line 921, in _get_option
    raise InvalidOptionError(name)
InvalidOptionError: Unsupported configuration option: SPAMBAYES_SPAM_CUTOFF

Cheers,
mk

From forsberg at efod.se  Thu Aug  9 15:05:29 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Thu, 9 Aug 2007 15:05:29 +0200
Subject: [Tracker-discuss] Unsupported configuration option
	SPAMBAYES_SPAM_CUTOFF
In-Reply-To: <5e8b0f6b0708090533g1cab260eje32b1a8828d07205@mail.gmail.com>
References: <5e8b0f6b0708090533g1cab260eje32b1a8828d07205@mail.gmail.com>
Message-ID: <200708091505.29868.forsberg@efod.se>

torsdag 09 augusti 2007 14:33 skrev Micha? Kwiatkowski:
> Hi,
>
> I updated my checkout directory today and my testing python-dev
> roundup instance doesn't work anymore. I get an exception listed
> below. Did I miss a configuration variable? If yes where should I
> define it?

It should be defined in <tracker home>/detectors/config.ini. There is an 
example in <tracker home>/detectors/config.ini.template.

I usually do it this way to allow different configuration on different hosts 
(not keeping the real config.ini i svn).

Regards,
\EF
-- 
http://efod.se/

From constant.beta at gmail.com  Thu Aug  9 15:34:24 2007
From: constant.beta at gmail.com (=?ISO-8859-2?Q?Micha=B3_Kwiatkowski?=)
Date: Thu, 9 Aug 2007 15:34:24 +0200
Subject: [Tracker-discuss] Unsupported configuration option
	SPAMBAYES_SPAM_CUTOFF
In-Reply-To: <200708091505.29868.forsberg@efod.se>
References: <5e8b0f6b0708090533g1cab260eje32b1a8828d07205@mail.gmail.com>
	<200708091505.29868.forsberg@efod.se>
Message-ID: <5e8b0f6b0708090634h1f62ae0clb5dfc89431825b4e@mail.gmail.com>

On 8/9/07, Erik Forsberg <forsberg at efod.se> wrote:
> torsdag 09 augusti 2007 14:33 skrev Micha? Kwiatkowski:
> > I updated my checkout directory today and my testing python-dev
> > roundup instance doesn't work anymore. I get an exception listed
> > below. Did I miss a configuration variable? If yes where should I
> > define it?
>
> It should be defined in <tracker home>/detectors/config.ini. There is an
> example in <tracker home>/detectors/config.ini.template.

Indeed, I didn't notice the config.ini.template in the detectors
directory. Confusing thing is that the configuration value is stored
in lowercase, while in the exception it was in uppercase, which was
the reason I failed to grep for it. Thanks for quick reply!

Cheers,
mk

From forsberg at efod.se  Sun Aug 12 20:39:03 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Sun, 12 Aug 2007 20:39:03 +0200
Subject: [Tracker-discuss] Time for reload - expect some downtime
Message-ID: <87ps1segxk.fsf@uterus.efod.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yo!

Just to avoid confusing anyone trying to test the tracker right now -
I'm going to take it down and do a reload of the database with fresh
data, and hopefully with descriptions for files.

\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGv1PGrJurFAusidkRApbRAKCjtrvIkXT5Y8xGsewIsiQtAw37swCfUj/4
aGHaJJKd9LeF7GJ0mZLpa6s=
=YpIL
-----END PGP SIGNATURE-----

From metatracker at psf.upfronthosting.co.za  Sun Aug 12 21:06:16 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Sun, 12 Aug 2007 19:06:16 -0000
Subject: [Tracker-discuss] [issue127] not properly htmlizing links
In-Reply-To: <46BADABB.6030506@gmx.net> (Georg Brandl's message of "Thu,
	09 Aug 2007 09:13:23 -0000")
Message-ID: <87fy2oefot.fsf@uterus.efod.se>


Erik Forsberg added the comment:

Georg Brandl <metatracker at psf.upfronthosting.co.za> writes:

>> To fix it, templating.py:StringHTMLProperty.hyper_re needs to be fixed. It
>> currently reads
>> 
>>     hyper_re = re.compile(r'((?P<url>\w{3,6}://\S+)|'
>>                           r'(?P<email>[-+=%/\w\.]+@[\w\.\-]+)|'
>>                           r'(?P<item>(?P<class>[A-Za-z_]+)(\s*)(?P<id>\d+)))')
>> 
>> I think changing that to
>> 
>>     hyper_re = re.compile(r'((?P<url>\w{3,6}://\S+[\w/])|'
>>                           r'(?P<email>[-+=%/\w\.]+@[\w\.\-]+)|'
>>                           r'(?P<item>(?P<class>[A-Za-z_]+)(\s*)(?P<id>\d+)))')
>> 
>> should do the trick, i.e. requiring that an URL ends with a letter, digit,
>> underscore or slash.

Good idea. Fixed in our vendor branch of the roundup
codebase. bugs.python.org updated. 
>
> While you're at it, could you please make the last line
>    r'(?P<item>(?P<class>[A-Za-z_]+|#)(\s*)(?P<id>\d+)))'
>
> (and default "class" to "issue") to resolve #103 too?

As this is behaviour that is not neccesarily correct for all roundup
instances, it's better to solve this with an extension. This might or
might not happen today, we'll see. 

\EF
-- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9

----------
status: chatting -> resolved

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue127>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Aug 13 07:46:33 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Mon, 13 Aug 2007 05:46:33 -0000
Subject: [Tracker-discuss] [issue126] show description from imported SF
	attachments
Message-ID: <1186983991.32.0.210143750672.issue126@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

Description is now imported from sf data dump and shown instead of content type
in  issue views. It has also been added to each file's view, as well as to the
list of all files (http://bugs.python.org/file).

----------
status: chatting -> resolved

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue126>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Aug 13 07:47:45 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Mon, 13 Aug 2007 05:47:45 -0000
Subject: [Tracker-discuss] [issue103] hyperlink "#1234" references in
	comments
Message-ID: <1186984065.63.0.615095291603.issue103@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

An extension for this has been installed on bugs.python.org. Please confirm that
it works as it should.

\EF

----------
assignedto:  -> forsberg
nosy: +forsberg
status: unread -> testing

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue103>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Aug 13 08:41:42 2007
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Mon, 13 Aug 2007 06:41:42 -0000
Subject: [Tracker-discuss] [issue126] show description from imported SF
	attachments
In-Reply-To: <1186983991.32.0.210143750672.issue126@psf.upfronthosting.co.za>
Message-ID: <bbaeab100708122341l39ce54c3y35bde7fe79de84d6@mail.gmail.com>


Brett C. added the comment:

Great!

On 8/12/07, Erik Forsberg <metatracker at psf.upfronthosting.co.za> wrote:
>
> Erik Forsberg added the comment:
>
> Description is now imported from sf data dump and shown instead of content type
> in  issue views. It has also been added to each file's view, as well as to the
> list of all files (http://bugs.python.org/file).
>
> ----------
> status: chatting -> resolved
>
> _______________________________________________________
> Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue126>
> _______________________________________________________
>

----------
status: resolved -> chatting

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue126>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Aug 13 09:26:32 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Mon, 13 Aug 2007 07:26:32 -0000
Subject: [Tracker-discuss] [issue103] hyperlink "#1234" references in
	comments
In-Reply-To: <1186984065.63.0.615095291603.issue103@psf.upfronthosting.co.za>
Message-ID: <46C007A8.8050508@gmx.net>


Georg Brandl added the comment:

Erik Forsberg schrieb:
> Erik Forsberg added the comment:
> 
> An extension for this has been installed on bugs.python.org. Please confirm that
> it works as it should.

Yes, it seems to. Thanks!

Georg

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue103>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Aug 15 17:07:03 2007
From: metatracker at psf.upfronthosting.co.za (Facundo Batista)
Date: Wed, 15 Aug 2007 15:07:03 -0000
Subject: [Tracker-discuss] [issue128] Item in SF not in new tracker
Message-ID: <1187190423.78.0.0275029360095.issue128@psf.upfronthosting.co.za>


New submission from Facundo Batista:

Alerting here because of Brett's recomendation by mail: The item 1772851 is in
SF but no in the new tracker.

The rest of items assigned to me are ok, :)

----------
messages: 674
nosy: facundobatista
priority: urgent
status: unread
title: Item in SF not in new tracker

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue128>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Aug 15 21:09:36 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Wed, 15 Aug 2007 19:09:36 -0000
Subject: [Tracker-discuss] [issue128] Item in SF not in new tracker
In-Reply-To: <1187190423.78.0.0275029360095.issue128@psf.upfronthosting.co.za>
	(Facundo Batista's message of "Wed, 15 Aug 2007 15:07:03 -0000")
Message-ID: <87odh8d385.fsf@uterus.efod.se>


Erik Forsberg added the comment:

Facundo Batista <metatracker at psf.upfronthosting.co.za> writes:

> New submission from Facundo Batista:
>
> Alerting here because of Brett's recomendation by mail: The item
> 1772851 is in SF but no in the new tracker.

That's simply a matter of timing - 1772851 was opened 2007-08-13
06:48, the tracker export that is the basis for the current
bugs.python.org was made 2007-08-12. 

There will be a fresh export/import before going live with the new tracker. 

> The rest of items assigned to me are ok, :)

Thanks for taking the time to check them out!

Regards,
\EF
-- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9

----------
assignedto:  -> forsberg
nosy: +forsberg
status: unread -> resolved

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue128>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 16 22:10:33 2007
From: metatracker at psf.upfronthosting.co.za (David Linke)
Date: Thu, 16 Aug 2007 20:10:33 -0000
Subject: [Tracker-discuss] [issue129] Search does not look in messages
Message-ID: <1187295033.81.0.462446063638.issue129@psf.upfronthosting.co.za>


New submission from David Linke:

Trying to search for text that is for sure present in message shows no hits. I
tried e.g. to look for "incredibly" which is in msg32580. Currently it seems as
if only the titles are indexed. This contradicts the description in the search
template.

Regards,
David

----------
messages: 676
nosy: dlinke
priority: bug
status: unread
title: Search does not look in messages

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue129>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 17 09:01:49 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Fri, 17 Aug 2007 07:01:49 -0000
Subject: [Tracker-discuss] [issue129] Search does not look in messages
In-Reply-To: <1187295033.81.0.462446063638.issue129@psf.upfronthosting.co.za>
Message-ID: <20070817090142.7779012e@impertigo.lkpg.cendio.se>


Erik Forsberg added the comment:

On Thu, 16 Aug 2007 20:10:33 -0000
David Linke <metatracker at psf.upfronthosting.co.za> wrote:

> 
> New submission from David Linke:
> 
> Trying to search for text that is for sure present in message shows
> no hits. I tried e.g. to look for "incredibly" which is in msg32580.
> Currently it seems as if only the titles are indexed. This
> contradicts the description in the search template.

Indeed, and a reindex doesn't help either. 

I remember having similar trouble before, but I thought I had squashed
that problem. Obviously, we need to fix this before going live.

I'll look into it.

Regards,
\EF

----------
assignedto:  -> forsberg
nosy: +forsberg
priority: bug -> urgent
status: unread -> chatting

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue129>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 17 12:43:33 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Fri, 17 Aug 2007 10:43:33 -0000
Subject: [Tracker-discuss] [issue129] Search does not look in messages
In-Reply-To: <20070817090142.7779012e@impertigo.lkpg.cendio.se>
Message-ID: <46C57BD2.5080601@v.loewis.de>


Martin v. L?wis added the comment:

> Indeed, and a reindex doesn't help either. 
> 
> I remember having similar trouble before, but I thought I had squashed
> that problem. Obviously, we need to fix this before going live.

The problem seems to be in roundup. rdbms_common.FileClass.index says

  for prop, propclass in self.getprops().items():
    if prop == 'content' and propclass.indexme:

Now, msg.properties['content'].indexme is True (which is the default for
FileClass), however, FileClass.getprops() says

        Note that the content prop is indexed separately, hence no indexme.
        '''
        d = Class.getprops(self, protected=protected).copy()
        d['content'] = hyperdb.String()
        return d

As the comment says, this clears indexme, causing content not to be
indexed anymore. I'm not sure what the remark "is indexed separately"
tries to say.

One possible fix is to use

  for prop, propclass in self.properties.items():

Regards,
Martin

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue129>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 17 13:39:17 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Fri, 17 Aug 2007 11:39:17 -0000
Subject: [Tracker-discuss] [issue129] Search does not look in messages
In-Reply-To: <46C57BD2.5080601@v.loewis.de>
Message-ID: <20070817133909.00f6093d@impertigo.lkpg.cendio.se>


Erik Forsberg added the comment:

On Fri, 17 Aug 2007 10:43:33 -0000
"Martin v. L?wis" <metatracker at psf.upfronthosting.co.za> wrote:

> 
> Martin v. L?wis added the comment:
> 
> > Indeed, and a reindex doesn't help either. 
> > 
> > I remember having similar trouble before, but I thought I had
> > squashed that problem. Obviously, we need to fix this before going
> > live.
> 
> The problem seems to be in roundup. 

Yes. I would say that we probably have a regression of
http://sourceforge.net/tracker/index.php?func=detail&aid=1698136&group_id=31577&atid=402788

Something might have gone wrong during one of the upgrades of the
roundup binaries we use.

\EF

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue129>
_______________________________________________________

From forsberg at efod.se  Fri Aug 17 13:39:09 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Fri, 17 Aug 2007 13:39:09 +0200
Subject: [Tracker-discuss] [issue129] Search does not look in messages
In-Reply-To: <46C57BD2.5080601@v.loewis.de>
References: <20070817090142.7779012e@impertigo.lkpg.cendio.se>
	<46C57BD2.5080601@v.loewis.de>
Message-ID: <20070817133909.00f6093d@impertigo.lkpg.cendio.se>

On Fri, 17 Aug 2007 10:43:33 -0000
"Martin v. L?wis" <metatracker at psf.upfronthosting.co.za> wrote:

> 
> Martin v. L?wis added the comment:
> 
> > Indeed, and a reindex doesn't help either. 
> > 
> > I remember having similar trouble before, but I thought I had
> > squashed that problem. Obviously, we need to fix this before going
> > live.
> 
> The problem seems to be in roundup. 

Yes. I would say that we probably have a regression of
http://sourceforge.net/tracker/index.php?func=detail&aid=1698136&group_id=31577&atid=402788

Something might have gone wrong during one of the upgrades of the
roundup binaries we use.

\EF
		             


From martin at v.loewis.de  Fri Aug 17 15:15:18 2007
From: martin at v.loewis.de (=?ISO-8859-15?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Fri, 17 Aug 2007 15:15:18 +0200
Subject: [Tracker-discuss] Proposal: Switch to roundup on August 23
Message-ID: <46C59F66.5060201@v.loewis.de>

Since nobody else seems to be proposing a date, I will:
how about switching to the new tracker next week (Thursday)?

Regards,
Martin

From brett at python.org  Fri Aug 17 21:28:02 2007
From: brett at python.org (Brett Cannon)
Date: Fri, 17 Aug 2007 12:28:02 -0700
Subject: [Tracker-discuss] Proposal: Switch to roundup on August 23
In-Reply-To: <46C59F66.5060201@v.loewis.de>
References: <46C59F66.5060201@v.loewis.de>
Message-ID: <bbaeab100708171228h3f851912p2393ad1a2db1e90@mail.gmail.com>

On 8/17/07, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> Since nobody else seems to be proposing a date, I will:
> how about switching to the new tracker next week (Thursday)?
>

Fine by me, although if we can't come to a decision before Monday I
will want to hold off since I want to send an announcement out a least
a couple of days out so people are not totally taken by surprise.

-Brett

From pfdubois at gmail.com  Sat Aug 18 00:41:15 2007
From: pfdubois at gmail.com (Paul Dubois)
Date: Fri, 17 Aug 2007 15:41:15 -0700
Subject: [Tracker-discuss] Proposal: Switch to roundup on August 23
In-Reply-To: <46C59F66.5060201@v.loewis.de>
References: <46C59F66.5060201@v.loewis.de>
Message-ID: <f74a6c2f0708171541ycb4b622wbb8ec841cbaea4e7@mail.gmail.com>

Good by me.

On 8/17/07, "Martin v. L?wis" <martin at v.loewis.de> wrote:
>
> Since nobody else seems to be proposing a date, I will:
> how about switching to the new tracker next week (Thursday)?
>
> Regards,
> Martin
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20070817/12ea2ddf/attachment.html 

From forsberg at efod.se  Sat Aug 18 10:46:36 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Sat, 18 Aug 2007 10:46:36 +0200
Subject: [Tracker-discuss] Proposal: Switch to roundup on August 23
In-Reply-To: <bbaeab100708171228h3f851912p2393ad1a2db1e90@mail.gmail.com>
	(Brett Cannon's message of "Fri, 17 Aug 2007 12:28:02 -0700")
References: <46C59F66.5060201@v.loewis.de>
	<bbaeab100708171228h3f851912p2393ad1a2db1e90@mail.gmail.com>
Message-ID: <87d4xljklv.fsf@uterus.efod.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Brett Cannon" <brett at python.org> writes:

> On 8/17/07, "Martin v. L?wis" <martin at v.loewis.de> wrote:
>> Since nobody else seems to be proposing a date, I will:
>> how about switching to the new tracker next week (Thursday)?
>>
>
> Fine by me, although if we can't come to a decision before Monday I
> will want to hold off since I want to send an announcement out a least
> a couple of days out so people are not totally taken by surprise.

I feel the need to make sure
http://psf.upfronthosting.co.za/roundup/meta/issue129 is completely
solved before going into production. I've commited a patch and ran a
reindex on the bugs.python.org instance, but the results are not
completely satisfying. Currently doing a new re-import (locally, on my
development machine).

Hopefully, I'll be able to fix this bug before monday, but if not, we
might have to wait another week. 

\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGxrHrrJurFAusidkRAlmxAKDlNOuJskoO2xWp6128WblxMn6N3gCgvcoS
3qsTL1h2qCXY/bhJa5nPRvI=
=xg4y
-----END PGP SIGNATURE-----

From metatracker at psf.upfronthosting.co.za  Sat Aug 18 10:47:36 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Sat, 18 Aug 2007 08:47:36 -0000
Subject: [Tracker-discuss] [issue129] Search does not look in messages
Message-ID: <1187426856.48.0.857359045085.issue129@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

I think I've found the problem. Currently testing with a reimport on my
development machine.

----------
status: chatting -> testing

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue129>
_______________________________________________________

From brett at python.org  Sat Aug 18 20:33:50 2007
From: brett at python.org (Brett Cannon)
Date: Sat, 18 Aug 2007 11:33:50 -0700
Subject: [Tracker-discuss] Proposal: Switch to roundup on August 23
In-Reply-To: <87d4xljklv.fsf@uterus.efod.se>
References: <46C59F66.5060201@v.loewis.de>
	<bbaeab100708171228h3f851912p2393ad1a2db1e90@mail.gmail.com>
	<87d4xljklv.fsf@uterus.efod.se>
Message-ID: <bbaeab100708181133t518a1e33kb771172a99d513ae@mail.gmail.com>

On 8/18/07, Erik Forsberg <forsberg at efod.se> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> "Brett Cannon" <brett at python.org> writes:
>
> > On 8/17/07, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> >> Since nobody else seems to be proposing a date, I will:
> >> how about switching to the new tracker next week (Thursday)?
> >>
> >
> > Fine by me, although if we can't come to a decision before Monday I
> > will want to hold off since I want to send an announcement out a least
> > a couple of days out so people are not totally taken by surprise.
>
> I feel the need to make sure
> http://psf.upfronthosting.co.za/roundup/meta/issue129 is completely
> solved before going into production. I've commited a patch and ran a
> reindex on the bugs.python.org instance, but the results are not
> completely satisfying. Currently doing a new re-import (locally, on my
> development machine).
>
> Hopefully, I'll be able to fix this bug before monday, but if not, we
> might have to wait another week.

Fine by me and this would be a good thing to have on launch.

-Brett

From metatracker at psf.upfronthosting.co.za  Sun Aug 19 22:52:23 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Sun, 19 Aug 2007 20:52:23 -0000
Subject: [Tracker-discuss] [issue129] Search does not look in messages
In-Reply-To: <1187426856.48.0.857359045085.issue129@psf.upfronthosting.co.za>
	(Erik Forsberg's message of "Sat, 18 Aug 2007 08:47:36 -0000")
Message-ID: <871wdzjlig.fsf@uterus.efod.se>


Erik Forsberg added the comment:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Erik Forsberg <metatracker at psf.upfronthosting.co.za> writes:

> I think I've found the problem. Currently testing with a reimport on my
> development machine.

Problem seems to be a combination of two things:

1) A bug in roundup (which I was sure I had fixed both in CVS and on
   the installation on psf) that caused msg/file contents not to be
   indexed at all.

2) Something fishy in the use of the xapian full-text indexer. Running
   the RDBMS-based indexer seems to work much better. 

We were using the xapian-based indexer, but I'm now switching to the
RDBMS-based one. I don't think this will give us any trouble. 

Currently doing a new import on bugs.python.org to make sure the
problem is gone.

\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGyK1XrJurFAusidkRAql0AJ9B7nAd71X7xm+yYPwI43azOYmKGQCfSzRd
uhPfFloP8JTcFt6wUY5lchs=
=JapU
-----END PGP SIGNATURE-----

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue129>
_______________________________________________________

From forsberg at efod.se  Sun Aug 19 22:54:12 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Sun, 19 Aug 2007 22:54:12 +0200
Subject: [Tracker-discuss] Proposal: Switch to roundup on August 23
In-Reply-To: <bbaeab100708181133t518a1e33kb771172a99d513ae@mail.gmail.com>
	(Brett Cannon's message of "Sat, 18 Aug 2007 11:33:50 -0700")
References: <46C59F66.5060201@v.loewis.de>
	<bbaeab100708171228h3f851912p2393ad1a2db1e90@mail.gmail.com>
	<87d4xljklv.fsf@uterus.efod.se>
	<bbaeab100708181133t518a1e33kb771172a99d513ae@mail.gmail.com>
Message-ID: <87ps1ji6tn.fsf@uterus.efod.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Brett Cannon" <brett at python.org> writes:

>> Hopefully, I'll be able to fix this bug before monday, but if not, we
>> might have to wait another week.
>
> Fine by me and this would be a good thing to have on launch.

I think I've squashed the bug, but I won't know for sure until a new
re-import is done. I'll know by tomorrow morning (CEST).

The re-import will also give me a more recent estimation of how long
time the import takes - it seems to have increased lately for some reason. 

Regards,
\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGyK3zrJurFAusidkRAoMVAKDJcIIbEl+mTfP6vd3Bc3T9xWKGdACgoj1O
LXmG7czyb/LcDxLymn8HOi4=
=znS6
-----END PGP SIGNATURE-----

From brett at python.org  Mon Aug 20 02:13:34 2007
From: brett at python.org (Brett Cannon)
Date: Sun, 19 Aug 2007 17:13:34 -0700
Subject: [Tracker-discuss] [issue129] Search does not look in messages
In-Reply-To: <871wdzjlig.fsf@uterus.efod.se>
References: <1187426856.48.0.857359045085.issue129@psf.upfronthosting.co.za>
	<871wdzjlig.fsf@uterus.efod.se>
Message-ID: <bbaeab100708191713t56e08194macec40874cda1bd@mail.gmail.com>

On 8/19/07, Erik Forsberg <metatracker at psf.upfronthosting.co.za> wrote:
>
> Erik Forsberg added the comment:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Erik Forsberg <metatracker at psf.upfronthosting.co.za> writes:
>
> > I think I've found the problem. Currently testing with a reimport on my
> > development machine.
>
> Problem seems to be a combination of two things:
>
> 1) A bug in roundup (which I was sure I had fixed both in CVS and on
>    the installation on psf) that caused msg/file contents not to be
>    indexed at all.
>
> 2) Something fishy in the use of the xapian full-text indexer. Running
>    the RDBMS-based indexer seems to work much better.
>
> We were using the xapian-based indexer, but I'm now switching to the
> RDBMS-based one. I don't think this will give us any trouble.
>
> Currently doing a new import on bugs.python.org to make sure the
> problem is gone.

Thanks for the update, Erik.  If it is working before I go to bed
tonight (midnight PT, which is UTC-7) I have no issue going through
with the transition on Thursday.  Otherwise we can re-assess to see if
we want to continue moving forward or not.

-Brett

From metatracker at psf.upfronthosting.co.za  Mon Aug 20 02:13:41 2007
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Mon, 20 Aug 2007 00:13:41 -0000
Subject: [Tracker-discuss] [issue129] Search does not look in messages
In-Reply-To: <871wdzjlig.fsf@uterus.efod.se>
Message-ID: <bbaeab100708191713t56e08194macec40874cda1bd@mail.gmail.com>


Brett C. added the comment:

On 8/19/07, Erik Forsberg <metatracker at psf.upfronthosting.co.za> wrote:
>
> Erik Forsberg added the comment:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Erik Forsberg <metatracker at psf.upfronthosting.co.za> writes:
>
> > I think I've found the problem. Currently testing with a reimport on my
> > development machine.
>
> Problem seems to be a combination of two things:
>
> 1) A bug in roundup (which I was sure I had fixed both in CVS and on
>    the installation on psf) that caused msg/file contents not to be
>    indexed at all.
>
> 2) Something fishy in the use of the xapian full-text indexer. Running
>    the RDBMS-based indexer seems to work much better.
>
> We were using the xapian-based indexer, but I'm now switching to the
> RDBMS-based one. I don't think this will give us any trouble.
>
> Currently doing a new import on bugs.python.org to make sure the
> problem is gone.

Thanks for the update, Erik.  If it is working before I go to bed
tonight (midnight PT, which is UTC-7) I have no issue going through
with the transition on Thursday.  Otherwise we can re-assess to see if
we want to continue moving forward or not.

-Brett

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue129>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Aug 20 07:02:43 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Mon, 20 Aug 2007 05:02:43 -0000
Subject: [Tracker-discuss] [issue129] Search does not look in messages
Message-ID: <1187586163.59.0.153516483017.issue129@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

After re-import with bug fix + use of RDBMS indexer, searching for 'incredibly'
now returns five issues instead of two, including the one that msg676 complains
about.

----------
status: testing -> resolved

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue129>
_______________________________________________________

From brett at python.org  Mon Aug 20 09:51:41 2007
From: brett at python.org (Brett Cannon)
Date: Mon, 20 Aug 2007 00:51:41 -0700
Subject: [Tracker-discuss] Planning to switch to new tracker on August 23rd
Message-ID: <bbaeab100708200051kadbe485h2cdc3176b157d8a4@mail.gmail.com>

Having squashed the final issues, we are now ready to switch over to
the new tracker!  The plan is to do it on the 23rd.  But before I
announce to the community I wanted to make sure there was not some
specific objection by python-dev or python-3000.  If there is please
let me know by midday Monday so that we can postpone to next week if
needed.

-Brett

From metatracker at psf.upfronthosting.co.za  Mon Aug 20 07:27:31 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Mon, 20 Aug 2007 05:27:31 -0000
Subject: [Tracker-discuss] [issue128] Item in SF not in new tracker
In-Reply-To: <87odh8d385.fsf@uterus.efod.se> (Erik Forsberg's message of "Wed,
	15 Aug 2007 19:09:36 -0000")
Message-ID: <87ejhyixmo.fsf@uterus.efod.se>


Erik Forsberg added the comment:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Erik Forsberg <metatracker at psf.upfronthosting.co.za> writes:

> Erik Forsberg added the comment:
>
> Facundo Batista <metatracker at psf.upfronthosting.co.za> writes:
>
>> New submission from Facundo Batista:
>>
>> Alerting here because of Brett's recomendation by mail: The item
>> 1772851 is in SF but no in the new tracker.
>
> That's simply a matter of timing - 1772851 was opened 2007-08-13
> 06:48, the tracker export that is the basis for the current
> bugs.python.org was made 2007-08-12. 

As I did a new re-import (based on fresh export) to fix a problem with
the fulltext search, I can now confirm that this was indeed only a
matter of timing.

http://bugs.python.org/issue1772851 now contains your missing issue.

Regards,
\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGySY/rJurFAusidkRAlUnAJ0XwQNhFmj/4A59XTMyRQr/SF/qhwCeMxBA
Xa53wgZWTod2mhsSdt8GJYg=
=qTfI
-----END PGP SIGNATURE-----

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue128>
_______________________________________________________

From forsberg at efod.se  Mon Aug 20 07:25:46 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Mon, 20 Aug 2007 07:25:46 +0200
Subject: [Tracker-discuss] [issue129] Search does not look in messages
In-Reply-To: <bbaeab100708191713t56e08194macec40874cda1bd@mail.gmail.com>
	(Brett Cannon's message of "Sun, 19 Aug 2007 17:13:34 -0700")
References: <1187426856.48.0.857359045085.issue129@psf.upfronthosting.co.za>
	<871wdzjlig.fsf@uterus.efod.se>
	<bbaeab100708191713t56e08194macec40874cda1bd@mail.gmail.com>
Message-ID: <87ir7aixph.fsf@uterus.efod.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Brett Cannon" <brett at python.org> writes:

>> Currently doing a new import on bugs.python.org to make sure the
>> problem is gone.
>
> Thanks for the update, Erik.  If it is working before I go to bed
> tonight (midnight PT, which is UTC-7) 

I think it was working before you going to bed, but unfortunately,
since _I_ had gone to bed, you couldn't see that from the outside :-),
especially since I implemented and tested issue80 as well (making it
easy to display a 503 Unavailable while doing maintenance working)

> with the transition on Thursday.  Otherwise we can re-assess to see if
> we want to continue moving forward or not.

- From my "department", going live on Thursday is now a "Go!"

\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGySXarJurFAusidkRAi/7AKDeMdV2iclAtfqwCbyiPXzpgdWG5ACg5Qm8
x9mxDF5IkxgMEtoWV7PED5M=
=pBBa
-----END PGP SIGNATURE-----

From metatracker at psf.upfronthosting.co.za  Mon Aug 20 07:47:30 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Mon, 20 Aug 2007 05:47:30 -0000
Subject: [Tracker-discuss] [issue110] Showstopper: sf.net is generating
	invalid XML
Message-ID: <1187588850.67.0.613631309934.issue110@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

I think we can close this one now.

----------
status: testing -> resolved

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue110>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Aug 20 07:46:52 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Mon, 20 Aug 2007 05:46:52 -0000
Subject: [Tracker-discuss] [issue80] Make it easy to display "down for
	maintenance" page,
	prerrably with a http status code that tells searchengines not
	toreindex page (503?)
Message-ID: <1187588811.77.0.962888286561.issue80@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

There's now some configuration file lines in the site configuration for apache2
that can be uncommented to show a document served by the asis module, that tells
the visitor to come back later (with error code 503).

----------
assignedto:  -> forsberg
status: chatting -> resolved

______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue80>
______________________________________________________

From brett at python.org  Mon Aug 20 22:37:58 2007
From: brett at python.org (Brett Cannon)
Date: Mon, 20 Aug 2007 13:37:58 -0700
Subject: [Tracker-discuss] Moving Python's tracker to Roundup on Aug 23rd
Message-ID: <bbaeab100708201337y603c90ecj518eaebbf26ce5a1@mail.gmail.com>

On August 23rd Python will be moving off of SourceForge and over to
our own issue tracker run on Roundup (http://bugs.python.org/).

During the transition there will be a time where the SourceForge
tracker is no longer being used but that the new tracker has not been
brought up yet.  We expect this gap to be for a few hours.  But to
minimize issues, please try to avoid using either SourceForge or the
new issue tracker on Aug 23rd if you can.


-Brett Cannon
Chairman, PSF Infrastructure committee

From brett at python.org  Mon Aug 20 23:32:31 2007
From: brett at python.org (Brett Cannon)
Date: Mon, 20 Aug 2007 14:32:31 -0700
Subject: [Tracker-discuss] What time to do the transition?
Message-ID: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>

So the date is set for Aug 23, but what time, UTC, do we want to do
this?  As I have said I am UTC-7, but since I am going to be on more
for moral support than actual technical help my time zone should not
be a consideration (although Paul is, I think, in my time zone).

-Brett

From pfdubois at gmail.com  Mon Aug 20 23:42:15 2007
From: pfdubois at gmail.com (Paul Dubois)
Date: Mon, 20 Aug 2007 14:42:15 -0700
Subject: [Tracker-discuss] What time to do the transition?
In-Reply-To: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>
References: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>
Message-ID: <f74a6c2f0708201442i6206dack9dfa37d24ae6236e@mail.gmail.com>

I will actually be at Google Mountain View that day so I can answer
questions for the 'important' people. Time doesn't matter at Google, I hear.
(:->

I think we owe Erik a big round of applause in particular.

On 8/20/07, Brett Cannon <brett at python.org> wrote:
>
> So the date is set for Aug 23, but what time, UTC, do we want to do
> this?  As I have said I am UTC-7, but since I am going to be on more
> for moral support than actual technical help my time zone should not
> be a consideration (although Paul is, I think, in my time zone).
>
> -Brett
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20070820/d1758200/attachment.htm 

From brett at python.org  Mon Aug 20 23:50:55 2007
From: brett at python.org (Brett Cannon)
Date: Mon, 20 Aug 2007 14:50:55 -0700
Subject: [Tracker-discuss] What time to do the transition?
In-Reply-To: <f74a6c2f0708201442i6206dack9dfa37d24ae6236e@mail.gmail.com>
References: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>
	<f74a6c2f0708201442i6206dack9dfa37d24ae6236e@mail.gmail.com>
Message-ID: <bbaeab100708201450q60a645c5y756964a311d3bb26@mail.gmail.com>

On 8/20/07, Paul Dubois <pfdubois at gmail.com> wrote:
> I will actually be at Google Mountain View that day so I can answer
> questions for the 'important' people. Time doesn't matter at Google, I hear.
> (:->

Nope, not with the free food always being available.  =)

>
> I think we owe Erik a big round of applause in particular.
>

Definitely!  If I wasn't a university student in another country I
would buy him dinner or something (along with you and Martin, and the
guys from Upfront, etc.

I do plan to send an announcement once the transition is done and I
will properly thank everyone publicly.

-Brett

>
> On 8/20/07, Brett Cannon <brett at python.org> wrote:
> >
> > So the date is set for Aug 23, but what time, UTC, do we want to do
> > this?  As I have said I am UTC-7, but since I am going to be on more
> > for moral support than actual technical help my time zone should not
> > be a consideration (although Paul is, I think, in my time zone).
> >
> > -Brett
> > _______________________________________________
> > Tracker-discuss mailing list
> > Tracker-discuss at python.org
> > http://mail.python.org/mailman/listinfo/tracker-discuss
> >
>
>

From skip at pobox.com  Tue Aug 21 02:45:18 2007
From: skip at pobox.com (skip at pobox.com)
Date: Mon, 20 Aug 2007 19:45:18 -0500
Subject: [Tracker-discuss] What time to do the transition?
In-Reply-To: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>
References: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>
Message-ID: <18122.13726.89311.546225@montanaro.dyndns.org>


    Brett> So the date is set for Aug 23, but what time, UTC, do we want to
    Brett> do this?  As I have said I am UTC-7, but since I am going to be
    Brett> on more for moral support than actual technical help my time zone
    Brett> should not be a consideration (although Paul is, I think, in my
    Brett> time zone).

It's unlikely you'll need any help from me, but in case it matters I'll be
at the Google Sprint from 11:30 to about 16:00 CDT (UTC-5) if you need
anything.

Coordinate via irc on #python-dev?

Skip


From brett at python.org  Tue Aug 21 03:21:03 2007
From: brett at python.org (Brett Cannon)
Date: Mon, 20 Aug 2007 18:21:03 -0700
Subject: [Tracker-discuss] What time to do the transition?
In-Reply-To: <18122.13726.89311.546225@montanaro.dyndns.org>
References: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>
	<18122.13726.89311.546225@montanaro.dyndns.org>
Message-ID: <bbaeab100708201821h3609c0ftcefd020eb5cb919b@mail.gmail.com>

On 8/20/07, skip at pobox.com <skip at pobox.com> wrote:
>
>     Brett> So the date is set for Aug 23, but what time, UTC, do we want to
>     Brett> do this?  As I have said I am UTC-7, but since I am going to be
>     Brett> on more for moral support than actual technical help my time zone
>     Brett> should not be a consideration (although Paul is, I think, in my
>     Brett> time zone).
>
> It's unlikely you'll need any help from me, but in case it matters I'll be
> at the Google Sprint from 11:30 to about 16:00 CDT (UTC-5) if you need
> anything.
>

Thanks for the offer, Skip!  Since Martin and Erik are running this
show, though, and both of them are in Europe I doubt it will happen
when it is convenient for us.  =)

> Coordinate via irc on #python-dev?

I figured IRC or Google Talk; either works for me.

-Brett

From forsberg at efod.se  Tue Aug 21 07:59:17 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Tue, 21 Aug 2007 07:59:17 +0200
Subject: [Tracker-discuss] What time to do the transition?
In-Reply-To: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>
	(Brett Cannon's message of "Mon, 20 Aug 2007 14:32:31 -0700")
References: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>
Message-ID: <873aydfmx6.fsf@uterus.efod.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Brett Cannon" <brett at python.org> writes:

> So the date is set for Aug 23, but what time, UTC, do we want to do
> this?  

My idea was to begin somewhere around 15:00 CEST, which is "Thursday,
August 23, 2007 at 13:00:00 UTC", if that's OK with Martin?

Coordination via IRC (#python-dev on FreeNode) is OK with me. 

Hmm.. on the matter of doing the transition - are we sure that the
export functionality on sf doesn't break when we disable the sf.net
trackers? Perhaps it would be better not to do anything (except
perhaps a warning text) about the tracker until we've done the export,
and possibly also the import as the files attached to the sf tracker
must be downloaded during import (not all of them, just new ones).

Perhaps I'm just worrying to much? :)

\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGyn81rJurFAusidkRAmGYAJ9RFMvtwHx/vykaMrmpHm2avB1GhQCdFeVA
R08mkecP4r15PMp6jkNKunk=
=4FX6
-----END PGP SIGNATURE-----

From martin at v.loewis.de  Tue Aug 21 08:39:56 2007
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Tue, 21 Aug 2007 08:39:56 +0200
Subject: [Tracker-discuss] What time to do the transition?
In-Reply-To: <873aydfmx6.fsf@uterus.efod.se>
References: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>
	<873aydfmx6.fsf@uterus.efod.se>
Message-ID: <46CA88BC.80908@v.loewis.de>

> Hmm.. on the matter of doing the transition - are we sure that the
> export functionality on sf doesn't break when we disable the sf.net
> trackers? Perhaps it would be better not to do anything (except
> perhaps a warning text) about the tracker until we've done the export,
> and possibly also the import as the files attached to the sf tracker
> must be downloaded during import (not all of them, just new ones).
> 
> Perhaps I'm just worrying to much? :)

I just tried it in a different project, and indeed, SF will remove
the hidden trackers from the export :-(

There is a third state of a tracker, "Visible to project members only".
In that state, data still get exported.

I've updated the instructions, and also put some links to the three
admin pages into the wiki.

Regards,
Martin

From martin at v.loewis.de  Tue Aug 21 08:41:04 2007
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Tue, 21 Aug 2007 08:41:04 +0200
Subject: [Tracker-discuss] What time to do the transition?
In-Reply-To: <873aydfmx6.fsf@uterus.efod.se>
References: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>
	<873aydfmx6.fsf@uterus.efod.se>
Message-ID: <46CA8900.8020205@v.loewis.de>

> My idea was to begin somewhere around 15:00 CEST, which is "Thursday,
> August 23, 2007 at 13:00:00 UTC", if that's OK with Martin?

Would work fine for me. I'll do it at work then, hoping that we can
complete way before 19:00 CEST (I can stay longer at work if needed).

Regards,
Martin

From forsberg at efod.se  Tue Aug 21 09:02:27 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Tue, 21 Aug 2007 09:02:27 +0200
Subject: [Tracker-discuss] What time to do the transition?
In-Reply-To: <46CA88BC.80908@v.loewis.de>
References: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>
	<873aydfmx6.fsf@uterus.efod.se> <46CA88BC.80908@v.loewis.de>
Message-ID: <20070821090227.1dd67c6b@impertigo.lkpg.cendio.se>

On Tue, 21 Aug 2007 08:39:56 +0200
"Martin v. L?wis" <martin at v.loewis.de> wrote:

> > Hmm.. on the matter of doing the transition - are we sure that the
> > export functionality on sf doesn't break when we disable the sf.net
> > trackers? Perhaps it would be better not to do anything (except
> > perhaps a warning text) about the tracker until we've done the
> > export, and possibly also the import as the files attached to the
> > sf tracker must be downloaded during import (not all of them, just
> > new ones).
> > 
> > Perhaps I'm just worrying to much? :)
> 
> I just tried it in a different project, and indeed, SF will remove
> the hidden trackers from the export :-(
> 
> There is a third state of a tracker, "Visible to project members
> only". In that state, data still get exported.

Hmm.. are the attached files still available for download by anonymous
users, or do you need to be logged in to do that? 

Perhaps we should go with a simpler approach:

1) Put BIG RED WARNING on top of each tracker page.

2) Do export + import.

3) Check if there's been any important modifications after the export,
and warn the people that made these modifications that they need to be
recommited to the new tracker (because they failed to see the warning)

\EF
-- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9

From martin at v.loewis.de  Tue Aug 21 09:36:04 2007
From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=)
Date: Tue, 21 Aug 2007 09:36:04 +0200
Subject: [Tracker-discuss] What time to do the transition?
In-Reply-To: <20070821090227.1dd67c6b@impertigo.lkpg.cendio.se>
References: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>	<873aydfmx6.fsf@uterus.efod.se>
	<46CA88BC.80908@v.loewis.de>
	<20070821090227.1dd67c6b@impertigo.lkpg.cendio.se>
Message-ID: <46CA95E4.5090201@v.loewis.de>

> Hmm.. are the attached files still available for download by anonymous
> users, or do you need to be logged in to do that? 

You are right - you need to be logged as a project member when the
tracker is restricted.

It seems SF has changed their policy: if you hide the tracker,
it's really inaccessible - not merely hidden (except for project
admins, to whom it is just hidden). That's good - so we *can*
effectively disable the old tracker.

> Perhaps we should go with a simpler approach:
> 
> 1) Put BIG RED WARNING on top of each tracker page.
> 
> 2) Do export + import.
> 
> 3) Check if there's been any important modifications after the export,
> and warn the people that made these modifications that they need to be
> recommited to the new tracker (because they failed to see the warning)
> 

Sounds good.

Regards,
Martin


From forsberg at efod.se  Tue Aug 21 19:42:21 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Tue, 21 Aug 2007 19:42:21 +0200
Subject: [Tracker-discuss] What time to do the transition?
In-Reply-To: <46CA95E4.5090201@v.loewis.de> (Martin v. =?iso-8859-1?Q?L=F6?=
	=?iso-8859-1?Q?wis's?= message of
	"Tue, 21 Aug 2007 09:36:04 +0200")
References: <bbaeab100708201432l190b40dbo62be88aa0ae64d70@mail.gmail.com>
	<873aydfmx6.fsf@uterus.efod.se> <46CA88BC.80908@v.loewis.de>
	<20070821090227.1dd67c6b@impertigo.lkpg.cendio.se>
	<46CA95E4.5090201@v.loewis.de>
Message-ID: <87hcmseqde.fsf@uterus.efod.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Martin v. L?wis" <martin at v.loewis.de> writes:

>> Hmm.. are the attached files still available for download by anonymous
>> users, or do you need to be logged in to do that? 
>
> You are right - you need to be logged as a project member when the
> tracker is restricted.
>
> It seems SF has changed their policy: if you hide the tracker,
> it's really inaccessible - not merely hidden (except for project
> admins, to whom it is just hidden). That's good - so we *can*
> effectively disable the old tracker.
>
>> Perhaps we should go with a simpler approach:
>> 
>> 1) Put BIG RED WARNING on top of each tracker page.
>> 
>> 2) Do export + import.
>> 
>> 3) Check if there's been any important modifications after the export,
>> and warn the people that made these modifications that they need to be
>> recommited to the new tracker (because they failed to see the warning)
>> 
>
> Sounds good.

Then let's go with this approach.

As you've provided the links where you can administrate the warning
texts, I think I'll be able to do that as well. So, I'll do steps
6-12, and let you do step 13.

That should leave you with less things to do from work. I would
appreciate if you keep an eye on the IRC channel, if I need to discuss
some problem.

As I said, I'm expecting to start somewhere around 15:00 CEST. The
export+import will probably be done somewhere around 18:00 CEST. 

Regards,
\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGyyP8rJurFAusidkRAvVHAKCPIYEF2NYv7RXei0V/cSgr5vaxLACfVLJP
jyiCi9KJ3devz0oW7MriHI4=
=9Lcs
-----END PGP SIGNATURE-----

From martin at v.loewis.de  Tue Aug 21 19:18:37 2007
From: martin at v.loewis.de (=?ISO-8859-15?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Tue, 21 Aug 2007 19:18:37 +0200
Subject: [Tracker-discuss] Switch announced on www.python.org
Message-ID: <46CB1E6D.8070401@v.loewis.de>

I put a notice of the upcoming switch on www.python.org

Regards,
Martin

From brett at python.org  Tue Aug 21 20:28:24 2007
From: brett at python.org (Brett Cannon)
Date: Tue, 21 Aug 2007 11:28:24 -0700
Subject: [Tracker-discuss] Switch announced on www.python.org
In-Reply-To: <46CB1E6D.8070401@v.loewis.de>
References: <46CB1E6D.8070401@v.loewis.de>
Message-ID: <bbaeab100708211128g441da340mcb1ee4cb71a37022@mail.gmail.com>

On 8/21/07, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> I put a notice of the upcoming switch on www.python.org

Good idea, Martin!  Thanks for doing that.

-Brett

From martin at v.loewis.de  Wed Aug 22 00:07:08 2007
From: martin at v.loewis.de (=?ISO-8859-15?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 22 Aug 2007 00:07:08 +0200
Subject: [Tracker-discuss] Speeding up indexer_rdbms
Message-ID: <46CB620C.3000101@v.loewis.de>

I found that the creation of two additional postgres indices, namely

create index words_textid_idx on __words(_textid);
create index textids_class_itemid_prop_idx on __textids (_class,
_itemid, _prop);

speeds up the indexing quite a bit, on change (search speed itself is
not affected). The biggest visible speedup is on "roundup-admin
reindex", which needs to delete all words for a given textid before
readding them, but it also helps on import and creation of new messages,
where it first checks whether the new (class,item,prop) triple is
really new, or a modification of an existing one. As a consequence,
these operations go down from O(N**2) (in the number of properties
to be added/reindexed) to O(N logN).

With these indexes, I can import the SF tracker on my machine in 40
minutes (assuming all files have been downloaded).

Regards,
Martin

From forsberg at efod.se  Wed Aug 22 08:01:51 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Wed, 22 Aug 2007 08:01:51 +0200
Subject: [Tracker-discuss] Speeding up indexer_rdbms
In-Reply-To: <46CB620C.3000101@v.loewis.de> (Martin v. =?iso-8859-1?Q?L=F6?=
	=?iso-8859-1?Q?wis's?= message of
	"Wed, 22 Aug 2007 00:07:08 +0200")
References: <46CB620C.3000101@v.loewis.de>
Message-ID: <87tzqsaz00.fsf@uterus.efod.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Martin v. L?wis" <martin at v.loewis.de> writes:

> I found that the creation of two additional postgres indices, namely
>
> create index words_textid_idx on __words(_textid);
> create index textids_class_itemid_prop_idx on __textids (_class,
> _itemid, _prop);

Interesting. This was discussed a month ago on roundup-devel. See
http://permalink.gmane.org/gmane.comp.bug-tracking.roundup.devel/4609

So, it's in roundup CVS, but not in the version we run. The latter can
of course be fixed before doing the final import. I'll take a look.

Regards,
\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGy9FPrJurFAusidkRAjaIAJ9RwULIZDR3ZKVePpgyLgqglF9SdgCeNy8s
09Te+G1MBJdkrR/jB/tohsw=
=XHWO
-----END PGP SIGNATURE-----

From indy90 at gmail.com  Wed Aug 22 15:28:24 2007
From: indy90 at gmail.com (Indy)
Date: Wed, 22 Aug 2007 16:28:24 +0300
Subject: [Tracker-discuss] Roundup Developer Account
Message-ID: <725281c20708220628j618b62fal554072b2b3079241@mail.gmail.com>

Greetings.

My name is Aristotelis Mikropoulos and I come from Greece. I am
writing you to let you know that I would like to have a Developer
account, under Python Roundup. I use Python for 6 years, and I love
it. I have submitted some patches at the old Python Issue Tracker (at
SourceForge), as well as some bug reports.
I would appreciate it a lot, if you could upgrade my account to Developer's.
My Python Roundup username is "Indy". Thanks a lot, in advance.

Yours sincerely,
Aristotelis Mikropoulos

-- 
Programs must be written for people to read, and only incidentally for
machines to execute.

From metatracker at psf.upfronthosting.co.za  Wed Aug 22 15:32:43 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Wed, 22 Aug 2007 13:32:43 -0000
Subject: [Tracker-discuss] [issue130] Submitter cannot withdraw issue
Message-ID: <1187789563.65.0.610907108426.issue130@psf.upfronthosting.co.za>


New submission from Martin v. L?wis:

It seems currently impossible for a submitter to withdraw a report that was made
incorrectly. OTOH, the developer Intro suggests that this is possible (and it
was on SF).

----------
messages: 687
nosy: loewis
priority: bug
status: unread
title: Submitter cannot withdraw issue

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue130>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Aug 22 18:17:18 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Wed, 22 Aug 2007 16:17:18 -0000
Subject: [Tracker-discuss] [issue130] Submitter cannot withdraw issue
In-Reply-To: <1187789563.65.0.610907108426.issue130@psf.upfronthosting.co.za> (Martin v. Löwis's message of "Wed, 22 Aug 2007 13:32:43 -0000")
Message-ID: <87ps1fbl2r.fsf@uterus.efod.se>


Erik Forsberg added the comment:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Martin v. L?wis" <metatracker at psf.upfronthosting.co.za> writes:

> New submission from Martin v. L?wis:
>
> It seems currently impossible for a submitter to withdraw a report
> that was made incorrectly. OTOH, the developer Intro suggests that
> this is possible (and it was on SF).
>
> ----------
> messages: 687
> nosy: loewis
> priority: bug

Hmm.. "bug" - does this mean you think this is important enough to
require a fix before transition? 

\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGzGGLrJurFAusidkRAtTEAKC3HcJeo0Mj1okeTaXzVpTvFNTFVgCfRFvm
+OcVuf7lVGtc2+fgf6mjf7c=
=WW/u
-----END PGP SIGNATURE-----

----------
status: unread -> chatting

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue130>
_______________________________________________________

From brett at python.org  Wed Aug 22 18:55:38 2007
From: brett at python.org (Brett Cannon)
Date: Wed, 22 Aug 2007 09:55:38 -0700
Subject: [Tracker-discuss] Roundup Developer Account
In-Reply-To: <725281c20708220628j618b62fal554072b2b3079241@mail.gmail.com>
References: <725281c20708220628j618b62fal554072b2b3079241@mail.gmail.com>
Message-ID: <bbaeab100708220955o419f035fg5447cbbfe104d754@mail.gmail.com>

On 8/22/07, Indy <indy90 at gmail.com> wrote:
> Greetings.
>
> My name is Aristotelis Mikropoulos and I come from Greece. I am
> writing you to let you know that I would like to have a Developer
> account, under Python Roundup. I use Python for 6 years, and I love
> it. I have submitted some patches at the old Python Issue Tracker (at
> SourceForge), as well as some bug reports.
> I would appreciate it a lot, if you could upgrade my account to Developer's.
> My Python Roundup username is "Indy". Thanks a lot, in advance.

First off, thanks for having helped Python in the past and wanting to
continue to help, Aristotelis!  Unfortunately, I made a mistake when I
wrote the new tracker docs and should have said that to get Developer
privileges python-dev needs to have given clearance for the new
abilities.  Then you can email here and your account can be upgraded.

Sorry about the confusion.

-Brett

From metatracker at psf.upfronthosting.co.za  Wed Aug 22 20:09:48 2007
From: metatracker at psf.upfronthosting.co.za (Paul Dubois)
Date: Wed, 22 Aug 2007 18:09:48 -0000
Subject: [Tracker-discuss] [issue130] Submitter cannot withdraw issue
In-Reply-To: <1187789563.65.0.610907108426.issue130@psf.upfronthosting.co.za>
Message-ID: <f74a6c2f0708221109l6ab30806i84df6cedde2c4cf7@mail.gmail.com>


Paul Dubois added the comment:

The Roundup way to 'withdraw' would be to close the issue. If we have made
it so that the user does not have this priv that would be the problem. It
takes an admin to 'retire' an issue and that isn't really something we want
to do normally.

On 8/22/07, Martin v. L?wis <metatracker at psf.upfronthosting.co.za> wrote:
>
>
> New submission from Martin v. L?wis:
>
> It seems currently impossible for a submitter to withdraw a report that
> was made
> incorrectly. OTOH, the developer Intro suggests that this is possible (and
> it
> was on SF).
>
> ----------
> messages: 687
> nosy: loewis
> priority: bug
> status: unread
> title: Submitter cannot withdraw issue
>
> _______________________________________________________
> Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue130>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue130>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20070822/765b5114/attachment.htm 

From pfdubois at gmail.com  Wed Aug 22 20:09:43 2007
From: pfdubois at gmail.com (Paul Dubois)
Date: Wed, 22 Aug 2007 11:09:43 -0700
Subject: [Tracker-discuss] [issue130] Submitter cannot withdraw issue
In-Reply-To: <1187789563.65.0.610907108426.issue130@psf.upfronthosting.co.za>
References: <1187789563.65.0.610907108426.issue130@psf.upfronthosting.co.za>
Message-ID: <f74a6c2f0708221109l6ab30806i84df6cedde2c4cf7@mail.gmail.com>

The Roundup way to 'withdraw' would be to close the issue. If we have made
it so that the user does not have this priv that would be the problem. It
takes an admin to 'retire' an issue and that isn't really something we want
to do normally.

On 8/22/07, Martin v. L?wis <metatracker at psf.upfronthosting.co.za> wrote:
>
>
> New submission from Martin v. L?wis:
>
> It seems currently impossible for a submitter to withdraw a report that
> was made
> incorrectly. OTOH, the developer Intro suggests that this is possible (and
> it
> was on SF).
>
> ----------
> messages: 687
> nosy: loewis
> priority: bug
> status: unread
> title: Submitter cannot withdraw issue
>
> _______________________________________________________
> Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue130>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20070822/765b5114/attachment-0001.htm 

From metatracker at psf.upfronthosting.co.za  Wed Aug 22 20:58:28 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Wed, 22 Aug 2007 18:58:28 -0000
Subject: [Tracker-discuss] [issue130] Submitter cannot withdraw issue
In-Reply-To: <87ps1fbl2r.fsf@uterus.efod.se>
Message-ID: <46CC8751.4050700@v.loewis.de>


Martin v. L?wis added the comment:

> Hmm.. "bug" - does this mean you think this is important enough to
> require a fix before transition? 

I keep forgetting what our usage of priority is - I thought "urgent"
means to act before the transition ("critical" would be "right away").
It's definitely not just a new feature that I propose, or a wish.
I would expect that more bugs get reported even after the transition,
and that some of them will properly called "bugs" rather than being
merely wishes or new features.

Dealing with it after the transition is fine.

Regards,
Martin

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue130>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Aug 22 21:01:13 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Wed, 22 Aug 2007 19:01:13 -0000
Subject: [Tracker-discuss] [issue130] Submitter cannot withdraw issue
In-Reply-To: <f74a6c2f0708221109l6ab30806i84df6cedde2c4cf7@mail.gmail.com>
Message-ID: <46CC87F7.1030002@v.loewis.de>


Martin v. L?wis added the comment:

> The Roundup way to 'withdraw' would be to close the issue. If we have made
> it so that the user does not have this priv that would be the problem. It
> takes an admin to 'retire' an issue and that isn't really something we want
> to do normally.

While the demo tracker is still life, see for yourself - use the "user"
account, try to create an issue and then close it, or try to close
issue1000 or issue1001 (created by the "user" account). There is, at
least, no UI to close the issue (the status is uneditable as "open").

Regards,
Martin

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue130>
_______________________________________________________

From martin at v.loewis.de  Wed Aug 22 22:25:51 2007
From: martin at v.loewis.de (=?ISO-8859-15?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 22 Aug 2007 22:25:51 +0200
Subject: [Tracker-discuss] Which email notifications
Message-ID: <46CC9BCF.9010201@v.loewis.de>

Paul,

Can you please summarize (again) the exact conditions under which email
is sent, and to what email addresses?

I'd like to update the web pages tomorrow, so I'd like some definite
reference.

I noticed that we currently have a list patches at python.org to which
new patch submissions are sent, IIUC, it won't be possible to provide
that service anymore, right?

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Thu Aug 23 15:27:35 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Thu, 23 Aug 2007 13:27:35 -0000
Subject: [Tracker-discuss] [issue131] Apply postgresql patch for better
	performance
Message-ID: <1187875654.99.0.684610916777.issue131@psf.upfronthosting.co.za>


New submission from Erik Forsberg:

Apply patch found both by mvl and Ralf Schlatterbeck:

http://permalink.gmane.org/gmane.comp.bug-tracking.roundup.devel/4609

This makes the import go much faster.

----------
assignedto: forsberg
messages: 692
nosy: forsberg
priority: urgent
status: unread
title: Apply postgresql patch for better performance
topic: roundup_deviation

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue131>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 23 15:32:11 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Thu, 23 Aug 2007 13:32:11 -0000
Subject: [Tracker-discuss] [issue131] Apply postgresql patch for better
	performance
Message-ID: <1187875931.32.0.416341686871.issue131@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

Done.

----------
status: unread -> resolved

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue131>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 23 15:36:04 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Thu, 23 Aug 2007 13:36:04 -0000
Subject: [Tracker-discuss] [issue122] Remove test users
Message-ID: <1187876164.73.0.658197828496.issue122@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

Done. Tracker reinitialized.

----------
status: chatting -> resolved

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue122>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 23 16:12:36 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 23 Aug 2007 14:12:36 -0000
Subject: [Tracker-discuss] [issue36] Rewrite sf bug redirector at python.org
Message-ID: <1187878355.0.0.694687339169.issue36@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

I have now changed the script on dinsdale in /data/cgi-bin/sf

----------
status: chatting -> resolved

______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue36>
______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 23 19:14:11 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Thu, 23 Aug 2007 17:14:11 -0000
Subject: [Tracker-discuss] [issue132] Enable blocker/dependency detector
Message-ID: <1187889251.39.0.628325064137.issue132@psf.upfronthosting.co.za>


New submission from Erik Forsberg:

Just after going into production, Georg Brandl tried to set an issue to
'Pending' - 'Wont fix'. This was not permitted by detectors/statusauditor.py.

I "solved" this by disabling all code except the code that sets the status of
new issues to 'open'. 

The detector also seems to do things like "remove issues from the list of
dependencies", which might not be something that we want. Blocking resolve of
issues that depend on issues that are not closed might be of interest, but
personally, I don't think the dependencies should be removed from the list.
Reading the code quickly, this seems to be what's supposed to happen.

We need to discuss what kind of rules should be enforced when it comes to
dependencies and status combinations.

----------
messages: 696
nosy: forsberg
priority: bug
status: unread
title: Enable blocker/dependency detector

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue132>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 23 19:19:57 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Thu, 23 Aug 2007 17:19:57 -0000
Subject: [Tracker-discuss] [issue133] show real name of comment authors
Message-ID: <1187889597.93.0.68125344639.issue133@psf.upfronthosting.co.za>


New submission from Georg Brandl:

It would be nice to display the real names of comment authors together with
their tracker names. SF did that, so there are comments that say "I agree with
Michael" but you can't see who Michael is :)

----------
messages: 697
nosy: gbrandl
priority: feature
status: unread
title: show real name of comment authors

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue133>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 23 19:50:04 2007
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Thu, 23 Aug 2007 17:50:04 -0000
Subject: [Tracker-discuss] [issue133] show real name of comment authors
Message-ID: <1187891404.08.0.624826083633.issue133@psf.upfronthosting.co.za>


Brett C. added the comment:

Another part to this, at least for official developers, is to change usernames
to match svn account names.

----------
status: unread -> chatting

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue133>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 23 20:16:40 2007
From: metatracker at psf.upfronthosting.co.za (Eric Huss)
Date: Thu, 23 Aug 2007 18:16:40 -0000
Subject: [Tracker-discuss] [issue134] Exception viewing closed issue
Message-ID: <1187893000.91.0.555834863275.issue134@psf.upfronthosting.co.za>


New submission from Eric Huss:

An issue on the Python tracker was recently closed.  Afterwards, trying to view
the issue caused a traceback to be displayed.  The URL was
http://bugs.python.org/issue1744398.  Erik Forsberg took a quick look at it and
made a workaround, but suggested that I file a bug to track the issue.  I do not
know what the underlying problem is.  The error was:


exceptions.AttributeError: 'int' object has no attribute 'split'

Debugging information follows

   1. A problem occurred in your template "issue.item.html".

Full traceback:

Traceback (most recent call last):
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/client.py",
line 770, in renderContext
    result = pt.render(self, None, None, **args)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/templating.py",
line 323, in render
    getEngine().getContext(c), output, tal=1, strictinsert=0)()
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 192, in __call__
    self.interpret(self.program)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 236, in interpret
    handlers[opcode](self, args)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 666, in do_useMacro
    self.interpret(macro)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 236, in interpret
    handlers[opcode](self, args)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 411, in
do_optTag_tal
    self.do_optTag(stuff)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 396, in do_optTag
    return self.no_tag(start, program)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 391, in no_tag
    self.interpret(program)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 236, in interpret
    handlers[opcode](self, args)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 689, in
do_defineSlot
    self.interpret(slot)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 236, in interpret
    handlers[opcode](self, args)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 632, in do_condition
    self.interpret(block)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 236, in interpret
    handlers[opcode](self, args)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 632, in do_condition
    self.interpret(block)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 236, in interpret
    handlers[opcode](self, args)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 632, in do_condition
    self.interpret(block)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 236, in interpret
    handlers[opcode](self, args)
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/TAL/TALInterpreter.py",
line 607, in do_loop_tal
    while iterator.next():
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/PageTemplates/TALES.py",
line 77, in next
    if ZTUtils.Iterator.next(self):
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/ZTUtils/Iterator.py",
line 46, in next
    if not (hasattr(self, '_next') or self._prep_next(self)):
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/ZTUtils/Iterator.py",
line 173, in prep_next
    it._next = it.seq.next()
  File
"/home/roundup/roundup-production//lib/python2.4/site-packages/roundup/cgi/templating.py",
line 797, in __getitem__
    items = item.split('.', 1)
AttributeError: 'int' object has no attribute 'split'

----------
messages: 699
nosy: ehuss
priority: bug
status: unread
title: Exception viewing closed issue

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue134>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 23 20:25:27 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Thu, 23 Aug 2007 18:25:27 -0000
Subject: [Tracker-discuss] [issue134] Exception viewing issue with
	superseder - should superseder be Link or Multilink
In-Reply-To: <1187893000.91.0.555834863275.issue134@psf.upfronthosting.co.za>
	(Eric Huss's message of "Thu, 23 Aug 2007 18:16:40 -0000")
Message-ID: <87bqcy9kh7.fsf@uterus.efod.se>


Erik Forsberg added the comment:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Eric Huss <metatracker at psf.upfronthosting.co.za> writes:

> I do not
> know what the underlying problem is.  

I know :-).

In our schema, 'superseder' on issue is a Link, not a Multilink as in
the default schema. This made the page template code confused, which
caused the traceback. 

In non-roundup-guru speak, this means that you can only have _one_
superseder for an issue, not several.

If this is what we want, then my temporary fix (checked in and
implemented at bugs.python.org) is OK. 

If we do want a superseder to a be a Multilink, we need to change the
schema. And the latter needs to be done after asking some roundup
?bergurus if that can be done safely.

\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGzdEUrJurFAusidkRAlvxAJsFcvu/bEbAAF0rBhryfC4OZagwbwCeMAjI
FximlzgqdXuQ5T/r+0aXKRQ=
=ZIaS
-----END PGP SIGNATURE-----

----------
status: unread -> chatting
title: Exception viewing closed issue -> Exception viewing issue with superseder - should superseder be Link or Multilink

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue134>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 23 20:31:57 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Thu, 23 Aug 2007 18:31:57 -0000
Subject: [Tracker-discuss] =?utf-8?q?=5Bissue134=5D_Exception_viewing_issu?=
	=?utf-8?q?e_with=09superseder_-_should_superseder_be_Link_or_Multi?=
	=?utf-8?q?link?=
In-Reply-To: <87bqcy9kh7.fsf@uterus.efod.se>
Message-ID: <46CDD2A3.2030106@gmx.net>


Georg Brandl added the comment:

Erik Forsberg schrieb:

> If we do want a superseder to a be a Multilink, we need to change the
> schema. And the latter needs to be done after asking some roundup
> ?bergurus if that can be done safely.

I think a Multilink is not necessary. You seldomly need a superseder
anyway, and I can only imagine the other direction (two issues superseded
by the same third issue).

Georg

----------
title: Exception viewing issue with superseder - should superseder be Link or Multilink? -> Exception viewing issue with	superseder - should superseder be Link or Multilink

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue134>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 23 21:03:43 2007
From: metatracker at psf.upfronthosting.co.za (Collin Winter)
Date: Thu, 23 Aug 2007 19:03:43 -0000
Subject: [Tracker-discuss] [issue135] Not obvious that the main search is
	limited to 'open' bugs
Message-ID: <1187895823.04.0.660965880801.issue135@psf.upfronthosting.co.za>


New submission from Collin Winter:

Please add some text to the main search results page (the one reached by typing
into the "search tracker" box at the upper-right) indicating that that facility
does not search "closed" bugs. Thanks.

----------
messages: 702
nosy: collinwinter
priority: bug
status: unread
title: Not obvious that the main search is limited to 'open' bugs

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue135>
_______________________________________________________

From martin at v.loewis.de  Thu Aug 23 21:21:06 2007
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Thu, 23 Aug 2007 21:21:06 +0200
Subject: [Tracker-discuss] [issue133] show real name of comment authors
In-Reply-To: <1187891404.08.0.624826083633.issue133@psf.upfronthosting.co.za>
References: <1187891404.08.0.624826083633.issue133@psf.upfronthosting.co.za>
Message-ID: <46CDDE22.6080800@v.loewis.de>

> Another part to this, at least for official developers, is to change usernames
> to match svn account names.

I think that could be an admin task. Users who want to change their
login names should file a bug report with the meta tracker.

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Thu Aug 23 21:21:08 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 23 Aug 2007 19:21:08 -0000
Subject: [Tracker-discuss] [issue133] show real name of comment authors
In-Reply-To: <1187891404.08.0.624826083633.issue133@psf.upfronthosting.co.za>
Message-ID: <46CDDE22.6080800@v.loewis.de>


Martin v. L?wis added the comment:

> Another part to this, at least for official developers, is to change usernames
> to match svn account names.

I think that could be an admin task. Users who want to change their
login names should file a bug report with the meta tracker.

Regards,
Martin

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue133>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 23 21:29:42 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Thu, 23 Aug 2007 19:29:42 -0000
Subject: [Tracker-discuss] [issue133] show real name of comment authors
In-Reply-To: <46CDDE22.6080800@v.loewis.de> (Martin v. Löwis's message of "Thu, 23 Aug 2007 19:21:08 -0000")
Message-ID: <87ps1e82xr.fsf@uterus.efod.se>


Erik Forsberg added the comment:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Martin v. L?wis" <metatracker at psf.upfronthosting.co.za> writes:

> Martin v. L?wis added the comment:
>
>> Another part to this, at least for official developers, is to change usernames
>> to match svn account names.
>
> I think that could be an admin task. Users who want to change their
> login names should file a bug report with the meta tracker.

Not neccesarily - roundup allows you to change your own username.

\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGzeAgrJurFAusidkRAq9CAJ9cDIOZgBeM3DY0aV5V9wj432TpjgCgw5vc
Q25J3zZuZ0lgeST/qYnrd5w=
=1BZ2
-----END PGP SIGNATURE-----

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue133>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 24 01:12:59 2007
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Thu, 23 Aug 2007 23:12:59 -0000
Subject: [Tracker-discuss] [issue136] Have default page group by priority
Message-ID: <1187910779.47.0.23313608748.issue136@psf.upfronthosting.co.za>


New submission from Brett C.:

Right now, when you visit bugs.python.org, the open issues are grouped by
severity.  It would probably be more useful to group by priority as it is more
important to get issues dealt with that are a top priority rather than ones that
happen to be severe but not an immediate issue.

----------
messages: 705
nosy: brettcannon
priority: feature
status: unread
title: Have default page group by priority

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue136>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 24 07:12:11 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Fri, 24 Aug 2007 05:12:11 -0000
Subject: [Tracker-discuss] [issue137] No option for Python 3
Message-ID: <1187932331.22.0.909695067807.issue137@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

Fixed. 

Marking as "Done - Could be better", as there's no obvious way to do it (you
have to know the URL).

Regards,
\EF

----------
assignedto:  -> forsberg
nosy: +forsberg, guido
status: unread -> done-cbb

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue137>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 24 14:27:27 2007
From: metatracker at psf.upfronthosting.co.za (Raghuram Devarakonda)
Date: Fri, 24 Aug 2007 12:27:27 -0000
Subject: [Tracker-discuss] [issue138] rename"Get SourceForge item"
Message-ID: <1187958447.53.0.342837594558.issue138@psf.upfronthosting.co.za>


New submission from Raghuram Devarakonda:

http://www.python.org/dev/ still shows "Get SourceForge item"  box. It needs to
be removed or perhaps renamed as it does take one to the roundup tracker.

----------
messages: 708
nosy: draghuram
priority: feature
status: unread
title: rename"Get SourceForge item"

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue138>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 24 21:48:55 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Fri, 24 Aug 2007 19:48:55 -0000
Subject: [Tracker-discuss] [issue136] Have default page group by priority
Message-ID: <1187984935.42.0.408745700708.issue136@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

Fixed, including search results from pre-defined queries as well as the search box.

----------
assignedto:  -> forsberg
nosy: +forsberg
status: unread -> resolved

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue136>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Aug 25 00:22:55 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Fri, 24 Aug 2007 22:22:55 -0000
Subject: [Tracker-discuss] [issue138] rename"Get SourceForge item"
Message-ID: <1187994175.26.0.215883350143.issue138@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Thanks for the report. This is now fixed.

----------
status: unread -> resolved

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue138>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sat Aug 25 20:29:54 2007
From: metatracker at psf.upfronthosting.co.za (Paul Dubois)
Date: Sat, 25 Aug 2007 18:29:54 -0000
Subject: [Tracker-discuss] [issue119] Tracker Documentation
Message-ID: <1188066594.04.0.434411170256.issue119@psf.upfronthosting.co.za>


Paul Dubois added the comment:

Note from the Py3K sprint: Anna Ravenscroft is updating the bugs.rst file in the
Py3K source tree (under Doc) to match the document currently in the moin. In the
end we should decide where we want to maintain the thing.

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue119>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Aug 26 00:42:41 2007
From: metatracker at psf.upfronthosting.co.za (Gregory P. Smith)
Date: Sat, 25 Aug 2007 22:42:41 -0000
Subject: [Tracker-discuss] [issue139] timezone support missing from
	bugs.python.org roundup
Message-ID: <1188081761.59.0.793649664985.issue139@psf.upfronthosting.co.za>


New submission from Gregory P. Smith:

Roundup has *proper* timezone support instead of the crappy "offset from UTC"
which can't support daylight savings time or fractional time zones.  Please
update roundup to use it.  The roundup 1.2.0 changelog says it added it from
this sourceforge patch.

http://sourceforge.net/tracker/index.php?func=detail&aid=1465296&group_id=31577&atid=402790

It looks like you need to install the pytz module.

----------
messages: 712
nosy: greg
priority: bug
status: unread
title: timezone support missing from bugs.python.org roundup

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue139>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Sun Aug 26 19:11:24 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Sun, 26 Aug 2007 17:11:24 -0000
Subject: [Tracker-discuss] [issue139] timezone support missing from
	bugs.python.org roundup
Message-ID: <1188148284.72.0.0110190201916.issue139@psf.upfronthosting.co.za>


Erik Forsberg added the comment:

python-tz installed. Roundup instance enhanced slightly - not only is it using
the symbolic time zone names, it also presents the user with a select dropdown,
so that users don't have to know the exact phrase for their timezone.

----------
assignedto:  -> forsberg
nosy: +forsberg
status: unread -> resolved

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue139>
_______________________________________________________

From skip at pobox.com  Mon Aug 27 20:57:47 2007
From: skip at pobox.com (skip at pobox.com)
Date: Mon, 27 Aug 2007 13:57:47 -0500
Subject: [Tracker-discuss] Is our Roundup instance applicable to other
	organizations?
Message-ID: <18131.7851.376109.495539@montanaro.dyndns.org>


The XEmacs folks currently have no issue tracker and are starting to think
about installing something.  I mentioned on the xemacs-beta mailing list
over the weekend that you all have gone through a substantial period of
customization to make it sing and dance to our tune.  Would it be
appropriate as-is for other organizations' use?  Other than skin/theme
issues is there much that's truly Python-specific about the Python issue
tracker?  If some changes were necessary would it be out of the question for
a subset of the XEmacs folks to gain commit access to our Subversion
repository and just operate on a branch?  Or is there be a better way for
them to start from what we are now using and avoid much of the effort that
folks like Erik, Martin and others have expended to get the Python issue
tracker to its current usable state?

Thx,

Skip


From brett at python.org  Mon Aug 27 21:27:58 2007
From: brett at python.org (Brett Cannon)
Date: Mon, 27 Aug 2007 12:27:58 -0700
Subject: [Tracker-discuss] Is our Roundup instance applicable to other
	organizations?
In-Reply-To: <18131.7851.376109.495539@montanaro.dyndns.org>
References: <18131.7851.376109.495539@montanaro.dyndns.org>
Message-ID: <bbaeab100708271227j7e36747fhcbee393316dabaae@mail.gmail.com>

On 8/27/07, skip at pobox.com <skip at pobox.com> wrote:
>
> The XEmacs folks currently have no issue tracker and are starting to think
> about installing something.  I mentioned on the xemacs-beta mailing list
> over the weekend that you all have gone through a substantial period of
> customization to make it sing and dance to our tune.  Would it be
> appropriate as-is for other organizations' use?  Other than skin/theme
> issues is there much that's truly Python-specific about the Python issue
> tracker?  If some changes were necessary would it be out of the question for
> a subset of the XEmacs folks to gain commit access to our Subversion
> repository and just operate on a branch?  Or is there be a better way for
> them to start from what we are now using and avoid much of the effort that
> folks like Erik, Martin and others have expended to get the Python issue
> tracker to its current usable state?

Obviously Erik and Martin can give more thorough answers, but most of
the work has been just to add fields we wanted and get the look we
desired.  I don't think our changes are that heavy.

And if you and the XEmacs folks want to talk to us about the issue
tracker shoot-up that is fine.

-Brett

From forsberg at efod.se  Mon Aug 27 22:06:37 2007
From: forsberg at efod.se (Erik Forsberg)
Date: Mon, 27 Aug 2007 22:06:37 +0200
Subject: [Tracker-discuss] Is our Roundup instance applicable to other
	organizations?
In-Reply-To: <18131.7851.376109.495539@montanaro.dyndns.org> (skip@pobox.com's
	message of "Mon, 27 Aug 2007 13:57:47 -0500")
References: <18131.7851.376109.495539@montanaro.dyndns.org>
Message-ID: <87tzqk68tu.fsf@uterus.efod.se>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

skip at pobox.com writes:

> The XEmacs folks currently have no issue tracker and are starting to think
> about installing something.  I mentioned on the xemacs-beta mailing list
> over the weekend that you all have gone through a substantial period of
> customization to make it sing and dance to our tune.  Would it be
> appropriate as-is for other organizations' use?  

Almost.

>Other than skin/theme issues is there much that's truly
>Python-specific about the Python issue tracker?

No. Here's a small list of things that need attention:

1) The initial data loaded into the tracker when the instance is
   initalized is very python-specific, but also easy to change - it's
   all in initial_date.py in the tracker home directory.

   This data is used only once (at tracker init), so keeping it under
   version control might not be neccesary.

2) Obviously, the stylesheets need to be changed. This is all done by
   editing files in the html/ directory - page.html and some of the
   help-related files need change.

3) We're currently running bugs.python.org off a slightly modified
   roundup so some of the feature we have won't work on an official
   release of roundup. As soon as I get the time, I'll start getting
   the changes into the stock roundup.

Except for the above, I think the instance we've created should be a
very good candidate for a public bug tracker for an open source
project. Some fields may be missing for some use cases - for example,
there's no 'milestone' field, but as the tracker is built on roundup,
an extra field is very easy to add.

> If some changes were necessary would it be out of the question for
> a subset of the XEmacs folks to gain commit access to our Subversion
> repository and just operate on a branch?

Someone else will have to answer that question. 

> Or is there be a better way for them to start from what we are now
> using and avoid much of the effort that folks like Erik, Martin and
> others have expended to get the Python issue tracker to its current
> usable state?

I'm thinking that maybe the instance we've created should be
"de-pythonized" and placed into the roundup CVS repo. as a template
for others to use. 

\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFG0y7NrJurFAusidkRAr/AAJ0cY8R9F5FhPvcwjHOf+A3VofN+JACg28C5
dEezjw+xhGQtsDL5XIzBhW8=
=mgVJ
-----END PGP SIGNATURE-----

From metatracker at psf.upfronthosting.co.za  Mon Aug 27 22:39:46 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Mon, 27 Aug 2007 20:39:46 -0000
Subject: [Tracker-discuss] [issue140] add keyword info in emails
Message-ID: <1188247186.16.0.785113568402.issue140@psf.upfronthosting.co.za>


New submission from Georg Brandl:

It'd be nice if the subject of notification emails included keywords, e.g. like

[issue12345] [patch,py3k] title of bug

----------
messages: 714
nosy: gbrandl
priority: feature
status: unread
title: add keyword info in emails

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue140>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Aug 27 22:42:14 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Mon, 27 Aug 2007 20:42:14 -0000
Subject: [Tracker-discuss] [issue16] Automatic issue expiration
Message-ID: <1188247334.31.0.0562629477501.issue16@psf.upfronthosting.co.za>


Georg Brandl added the comment:

Is this now implemented? There is a "pending" status, but is the item closed
automatically after a period of time?

______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue16>
______________________________________________________

From metatracker at psf.upfronthosting.co.za  Mon Aug 27 22:43:28 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Mon, 27 Aug 2007 20:43:28 -0000
Subject: [Tracker-discuss] [issue85] prevent comment duplication
Message-ID: <1188247408.97.0.133316272859.issue85@psf.upfronthosting.co.za>


Georg Brandl added the comment:

It seems that Roundup already includes a mechanism to prevent duplicate
submissions, so I'll mark this as resolved.

----------
status: unread -> resolved

______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue85>
______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Aug 28 04:58:54 2007
From: metatracker at psf.upfronthosting.co.za (Paul Dubois)
Date: Tue, 28 Aug 2007 02:58:54 -0000
Subject: [Tracker-discuss] [issue140] add keyword info in emails
In-Reply-To: <1188247186.16.0.785113568402.issue140@psf.upfronthosting.co.za>
Message-ID: <f74a6c2f0708271958h2ad2d295q8d2d63e2c957e069@mail.gmail.com>


Paul Dubois added the comment:

Well, you can't do it that way, because that would mess up the email
submission subject-line cracker. Also when a person replies to an email they
might want to change something using the mechanism that puts things in [ ]
at the end, e.g.

[issue12345] title of bug [status=pending]

Also note that if the set of keywords has *changed* you will see it at the
bottom of the email.

On 8/27/07, Georg Brandl <metatracker at psf.upfronthosting.co.za> wrote:
>
>
> New submission from Georg Brandl:
>
> It'd be nice if the subject of notification emails included keywords, e.g.
> like
>
> [issue12345] [patch,py3k] title of bug
>
> ----------
> messages: 714
> nosy: gbrandl
> priority: feature
> status: unread
> title: add keyword info in emails
>
> _______________________________________________________
> Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue140>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

----------
status: unread -> chatting

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue140>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20070828/10a541fb/attachment.htm 

From metatracker at psf.upfronthosting.co.za  Tue Aug 28 07:21:13 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Tue, 28 Aug 2007 05:21:13 -0000
Subject: [Tracker-discuss] [issue16] Automatic issue expiration
In-Reply-To: <1188247334.31.0.0562629477501.issue16@psf.upfronthosting.co.za>
	(Georg Brandl's message of "Mon, 27 Aug 2007 20:42:14 -0000")
Message-ID: <87ps185j5q.fsf@uterus.efod.se>


Erik Forsberg added the comment:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Georg Brandl <metatracker at psf.upfronthosting.co.za> writes:

> Georg Brandl added the comment:
>
> Is this now implemented? 

No.

>There is a "pending" status, but is the item closed automatically
>after a period of time?

No.

\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFG07DBrJurFAusidkRAqyBAKDCbVDElJdLJoigKJElsn6HCmaMGwCfRUI7
7oBf6WgNN6GLvUwpasMY7es=
=F9h9
-----END PGP SIGNATURE-----

______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue16>
______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Aug 28 10:18:44 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Tue, 28 Aug 2007 08:18:44 -0000
Subject: [Tracker-discuss] [issue140] add keyword info in emails
In-Reply-To: <f74a6c2f0708271958h2ad2d295q8d2d63e2c957e069@mail.gmail.com>
Message-ID: <46D3DA68.6010508@gmx.net>


Georg Brandl added the comment:

Paul Dubois schrieb:
> Paul Dubois added the comment:
> 
> Well, you can't do it that way, because that would mess up the email
> submission subject-line cracker. Also when a person replies to an email they
> might want to change something using the mechanism that puts things in [ ]
> at the end, e.g.
> 
> [issue12345] title of bug [status=pending]

The brackets were only a proposal; I'd be fine with any way that "patch" or
"py3k" shows up in the subject line.

> Also note that if the set of keywords has *changed* you will see it at the
> bottom of the email.

Yes, I know that, but it won't help the cursory glance over new items.

Georg

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue140>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Tue Aug 28 16:42:34 2007
From: metatracker at psf.upfronthosting.co.za (Paul Dubois)
Date: Tue, 28 Aug 2007 14:42:34 -0000
Subject: [Tracker-discuss] [issue140] add keyword info in emails
In-Reply-To: <46D3DA68.6010508@gmx.net>
Message-ID: <f74a6c2f0708280742x75e0ca8dn1be6295c3e57edc0@mail.gmail.com>


Paul Dubois added the comment:

I understand what you are asking for. Since people reply to emails it turns
out that they can change the title of the issue by changing the subject (the
part after the [issuennnn] part and before the optional trailing
[something=value, ...] part. So putting something in the subject line is
fraught with difficulty in that the parser of the incoming email subject
line will have to 'undo' whatever we do to the outgoing part. That's always
a problem because whatever you choose becomes something users can't put in a
title. We'd have to be awfully careful.

On 8/28/07, Georg Brandl <metatracker at psf.upfronthosting.co.za> wrote:
>
>
> Georg Brandl added the comment:
>
> Paul Dubois schrieb:
> > Paul Dubois added the comment:
> >
> > Well, you can't do it that way, because that would mess up the email
> > submission subject-line cracker. Also when a person replies to an email
> they
> > might want to change something using the mechanism that puts things in [
> ]
> > at the end, e.g.
> >
> > [issue12345] title of bug [status=pending]
>
> The brackets were only a proposal; I'd be fine with any way that "patch"
> or
> "py3k" shows up in the subject line.
>
> > Also note that if the set of keywords has *changed* you will see it at
> the
> > bottom of the email.
>
> Yes, I know that, but it won't help the cursory glance over new items.
>
> Georg
>
> _______________________________________________________
> Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue140>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue140>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20070828/d17b6ee9/attachment.htm 

From martin at v.loewis.de  Tue Aug 28 17:21:03 2007
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Tue, 28 Aug 2007 17:21:03 +0200
Subject: [Tracker-discuss] Is our Roundup instance applicable to other
 organizations?
In-Reply-To: <18131.7851.376109.495539@montanaro.dyndns.org>
References: <18131.7851.376109.495539@montanaro.dyndns.org>
Message-ID: <46D43D5F.2030204@v.loewis.de>

> The XEmacs folks currently have no issue tracker and are starting to think
> about installing something.  I mentioned on the xemacs-beta mailing list
> over the weekend that you all have gone through a substantial period of
> customization to make it sing and dance to our tune.  Would it be
> appropriate as-is for other organizations' use?

I think I disagree with Erik's analysis that this tracker instance is
very reusable - not more so than the "classic" template that ships
with Roundup. In particular, the schema was heavily influenced by
the SF schema - so if you migrate from SF, using the bugs.python.org
schema might be a good idea. Otherwise, I cannot see it as better or
worse than the classic schema.

OTOH, various detectors and extensions are useful for other
installations as well; people are free to copy them as they
please (although I formally can't speak from a licensing point
of view for many of these).

> If some changes were necessary would it be out of the question for
> a subset of the XEmacs folks to gain commit access to our Subversion
> repository and just operate on a branch?

That would be possible. However, I recommend that whoever wants to
work on this just looks at what is there at first, if they then find
that they want to use it, and want to commit their instance in
the python.org repository, we could arrange for that (but I can't
see why they wouldn't want to store it in their own SCM).

> Or is there be a better way for
> them to start from what we are now using and avoid much of the effort that
> folks like Erik, Martin and others have expended to get the Python issue
> tracker to its current usable state?

It's fairly easy to set up roundup from scratch, using the classic
template. Unless there is a good reason not to do that, this is what
I would recommend. It works really well.

Regards,
Martin

From metatracker at psf.upfronthosting.co.za  Wed Aug 29 18:54:25 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Wed, 29 Aug 2007 16:54:25 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
Message-ID: <1188406465.46.0.0648895398009.issue141@psf.upfronthosting.co.za>


New submission from Martin v. L?wis:

When somebody is assigned an issue, they should be sent an email message about
the issue, and be added to the nosy list (or, alternatively, a copy of each nosy
message should be sent to the assignee)

----------
messages: 721
nosy: loewis
priority: bug
status: unread
title: Should send email on assignment

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Aug 29 18:55:40 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Wed, 29 Aug 2007 16:55:40 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
Message-ID: <1188406540.43.0.888923934825.issue141@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Thinking about this, I find it fairly urgent, or else people won't learn that
they are assigned things right now. If somebody disagrees, feel free to
downgrade the priority again.

----------
priority: bug -> urgent
status: unread -> chatting

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Aug 29 19:10:59 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Wed, 29 Aug 2007 17:10:59 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
In-Reply-To: <1188406540.43.0.888923934825.issue141@psf.upfronthosting.co.za>
Message-ID: <46D5A8A7.20103@python.org>


Georg Brandl added the comment:

Martin v. L?wis schrieb:
> Martin v. L?wis added the comment:
> 
> Thinking about this, I find it fairly urgent, or else people won't learn that
> they are assigned things right now. If somebody disagrees, feel free to
> downgrade the priority again.

I agree with you about the priority.

Georg

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________

From skip at pobox.com  Wed Aug 29 22:03:10 2007
From: skip at pobox.com (skip at pobox.com)
Date: Wed, 29 Aug 2007 15:03:10 -0500
Subject: [Tracker-discuss] [issue141] Should send email on assignment
In-Reply-To: <1188406540.43.0.888923934825.issue141@psf.upfronthosting.co.za>
References: <1188406540.43.0.888923934825.issue141@psf.upfronthosting.co.za>
Message-ID: <18133.53502.50499.830268@montanaro.dyndns.org>


    Martin> Thinking about this, I find it fairly urgent, or else people
    Martin> won't learn that they are assigned things right now. If somebody
    Martin> disagrees, feel free to downgrade the priority again.

Me too.  I made one or two assignments last night during a run through some
ancient tickets.  Is it a suitable workaround to make sure the person being
assigned the issue is on the nosy list?

Skip

From metatracker at psf.upfronthosting.co.za  Wed Aug 29 22:03:15 2007
From: metatracker at psf.upfronthosting.co.za (Skip Montanaro)
Date: Wed, 29 Aug 2007 20:03:15 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
In-Reply-To: <1188406540.43.0.888923934825.issue141@psf.upfronthosting.co.za>
Message-ID: <18133.53502.50499.830268@montanaro.dyndns.org>


Skip Montanaro added the comment:

Martin> Thinking about this, I find it fairly urgent, or else people
    Martin> won't learn that they are assigned things right now. If somebody
    Martin> disagrees, feel free to downgrade the priority again.

Me too.  I made one or two assignments last night during a run through some
ancient tickets.  Is it a suitable workaround to make sure the person being
assigned the issue is on the nosy list?

Skip

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Aug 29 22:09:46 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Wed, 29 Aug 2007 20:09:46 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
In-Reply-To: <18133.53502.50499.830268@montanaro.dyndns.org>
Message-ID: <46D5D286.40701@v.loewis.de>


Martin v. L?wis added the comment:

> Me too.  I made one or two assignments last night during a run through some
> ancient tickets.  Is it a suitable workaround to make sure the person being
> assigned the issue is on the nosy list?

That's not sufficient - you also have to add a message, as the nosy list
will only be considered the next time a message is sent (which isn't
when only some data fields are changed).

Regards,
Martin

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Wed Aug 29 22:33:25 2007
From: metatracker at psf.upfronthosting.co.za (Paul Dubois)
Date: Wed, 29 Aug 2007 20:33:25 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
In-Reply-To: <46D5D286.40701@v.loewis.de>
Message-ID: <f74a6c2f0708291333x700bd2d3lc19a77bd7d12acf5@mail.gmail.com>


Paul Dubois added the comment:

work around is:

Set assignment field
Add assignee to nosy list
Make message "Assigning this issue to Mr. Foo"
Submit

On 8/29/07, Martin v. L?wis <metatracker at psf.upfronthosting.co.za> wrote:
>
>
> Martin v. L?wis added the comment:
>
> > Me too.  I made one or two assignments last night during a run through
> some
> > ancient tickets.  Is it a suitable workaround to make sure the person
> being
> > assigned the issue is on the nosy list?
>
> That's not sufficient - you also have to add a message, as the nosy list
> will only be considered the next time a message is sent (which isn't
> when only some data fields are changed).
>
> Regards,
> Martin
>
> _______________________________________________________
> Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue141>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20070829/40412fe8/attachment.htm 

From pfdubois at gmail.com  Wed Aug 29 22:33:22 2007
From: pfdubois at gmail.com (Paul Dubois)
Date: Wed, 29 Aug 2007 13:33:22 -0700
Subject: [Tracker-discuss] [issue141] Should send email on assignment
In-Reply-To: <46D5D286.40701@v.loewis.de>
References: <18133.53502.50499.830268@montanaro.dyndns.org>
	<46D5D286.40701@v.loewis.de>
Message-ID: <f74a6c2f0708291333x700bd2d3lc19a77bd7d12acf5@mail.gmail.com>

work around is:

Set assignment field
Add assignee to nosy list
Make message "Assigning this issue to Mr. Foo"
Submit

On 8/29/07, Martin v. L?wis <metatracker at psf.upfronthosting.co.za> wrote:
>
>
> Martin v. L?wis added the comment:
>
> > Me too.  I made one or two assignments last night during a run through
> some
> > ancient tickets.  Is it a suitable workaround to make sure the person
> being
> > assigned the issue is on the nosy list?
>
> That's not sufficient - you also have to add a message, as the nosy list
> will only be considered the next time a message is sent (which isn't
> when only some data fields are changed).
>
> Regards,
> Martin
>
> _______________________________________________________
> Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue141>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20070829/40412fe8/attachment-0001.htm 

From metatracker at psf.upfronthosting.co.za  Thu Aug 30 10:29:14 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Thu, 30 Aug 2007 08:29:14 -0000
Subject: [Tracker-discuss] [issue142] Add a new component "Documentation
	tools (Sphinx)"
Message-ID: <1188462554.91.0.322603285165.issue142@psf.upfronthosting.co.za>


New submission from Georg Brandl:

Would be nice, to track bugs separately from documentation content issues.

----------
messages: 727
nosy: gbrandl
priority: wish
status: unread
title: Add a new component "Documentation tools (Sphinx)"

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue142>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 30 10:44:48 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 30 Aug 2007 08:44:48 -0000
Subject: [Tracker-discuss] [issue142] Add a new component "Documentation
	tools (Sphinx)"
Message-ID: <1188463488.08.0.941959385153.issue142@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

Done. To add a new component, go to /component, and add a line starting with X.

----------
assignedto:  -> loewis
nosy: +loewis
status: unread -> resolved

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue142>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 30 10:51:08 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Thu, 30 Aug 2007 08:51:08 -0000
Subject: [Tracker-discuss] [issue142] Add a new component "Documentation
	tools (Sphinx)"
In-Reply-To: <1188463488.08.0.941959385153.issue142@psf.upfronthosting.co.za>
Message-ID: <46D68501.702@gmx.net>


Georg Brandl added the comment:

Martin v. L?wis schrieb:
> Martin v. L?wis added the comment:
> 
> Done. To add a new component, go to /component, and add a line starting with X.

Nice, thanks! I'll remember that.

----------
status: resolved -> chatting

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue142>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 30 11:33:04 2007
From: metatracker at psf.upfronthosting.co.za (Marc-Andre Lemburg)
Date: Thu, 30 Aug 2007 09:33:04 -0000
Subject: [Tracker-discuss] [issue143] Tracker emails should list the
	classification
Message-ID: <1188466384.76.0.105240943615.issue143@psf.upfronthosting.co.za>


New submission from Marc-Andre Lemburg:

The SF tracker used to list the classification of the issues in the emails
making it possible to have an MUA filter them accordingly. This is no longer
possible with the new tracker.

----------
messages: 730
nosy: lemburg
priority: feature
status: unread
title: Tracker emails should list the classification

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue143>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 30 11:44:46 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 30 Aug 2007 09:44:46 -0000
Subject: [Tracker-discuss] [issue143] Tracker emails should list the
	classification
Message-ID: <1188467086.09.0.00252277299538.issue143@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

If possible, I suggest to add them into email header fields, e.g.
X-roundup-Components. Putting them into the body (as SF did) seems redundant
noise to me.

----------
status: unread -> chatting

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue143>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 30 11:58:26 2007
From: metatracker at psf.upfronthosting.co.za (Marc-Andre Lemburg)
Date: Thu, 30 Aug 2007 09:58:26 -0000
Subject: [Tracker-discuss] [issue143] Tracker emails should list the
	classification
Message-ID: <1188467906.87.0.897240472317.issue143@psf.upfronthosting.co.za>


Marc-Andre Lemburg added the comment:

Good idea. That would make filtering even easier.

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue143>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 30 19:53:43 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Thu, 30 Aug 2007 17:53:43 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
In-Reply-To: <1188406465.46.0.0648895398009.issue141@psf.upfronthosting.co.za> (Martin v. Löwis's message of "Wed, 29 Aug 2007 16:54:25 -0000")
Message-ID: <87d4x46h9b.fsf@uterus.efod.se>


Erik Forsberg added the comment:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Martin v. L?wis" <metatracker at psf.upfronthosting.co.za> writes:

> New submission from Martin v. L?wis:
>
> When somebody is assigned an issue, they should be sent an email
> message about the issue, and be added to the nosy list (or,
> alternatively, a copy of each nosy message should be sent to the
> assignee)

This problem puzzled me at first, because adding of the assignee to
the nosy list is standard behaviour in any roundup tracker that
originates from the 'classic' tracker template.

It turns out that when the Schema was designed, the field that is
normally named 'assignedto' was renamed into 'assignee', but the
detector (nosyreaction.py) was not changed accordingly. 

This has now been fixed, so the assignee is now automatically added to
the nosy list. This does however not solve the whole problem - the
assignee will still not get any mail about his/her new issue unless
there is also a comment.

My proposed solution to this is to modify the busybody detector to
make it send mail to the nosy list whenever there's a change, even if
it's only a property change without message.

Comments on that? 

\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFG1wQfrJurFAusidkRAnRmAKCIh1pA+LFgkhBhGbIoXJin55TrJgCfWrAO
ZntXy0fv4yPF9ckON5E/Ne0=
=XgNG
-----END PGP SIGNATURE-----

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 30 21:43:48 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 30 Aug 2007 19:43:48 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
In-Reply-To: <87d4x46h9b.fsf@uterus.efod.se>
Message-ID: <46D71DF2.1060602@v.loewis.de>


Martin v. L?wis added the comment:

> My proposed solution to this is to modify the busybody detector to
> make it send mail to the nosy list whenever there's a change, even if
> it's only a property change without message.
> 
> Comments on that? 

IIRC, that's what SF did, so it's worth a try. If people complain, it
might be useful to add a "make silent change" feature, although I'm
uncertain on how that could be implemented.

In any case, people are used to getting large amounts of email from
bug tracking, so I'm in favor of that change.

Regards,
Martin

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 30 21:51:05 2007
From: metatracker at psf.upfronthosting.co.za (Paul Dubois)
Date: Thu, 30 Aug 2007 19:51:05 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
In-Reply-To: <87d4x46h9b.fsf@uterus.efod.se>
Message-ID: <f74a6c2f0708301250h2f6446a3kd2985603b5d5d2d2@mail.gmail.com>


Paul Dubois added the comment:

On 8/30/07, Erik Forsberg <metatracker at psf.upfronthosting.co.za> wrote:
>
>
>
>
> My proposed solution to this is to modify the busybody detector to
> make it send mail to the nosy list whenever there's a change, even if
> it's only a property change without message.
>
> Comments on that?
>
> \EF
> - --
> Erik Forsberg                 http://efod.se

We did go through this discussion before; my experience was that such a
> change is undesirable, causing too much mail for trivial administrative
> changes. With your fix the assignee will get mail unless you do not enter
> some comment like 'Assigning to foo.', as in standard roundup. We also have
> the 'busybody' reactor that does send mail on every change to a mailing
> list. (Recall you had to fool with it so it would make a sensible message
> when no text had been supplied.) Can we just try it as-is for a while? The
> number of people who 'assign' issues to people other than themselves must
> not be very large and as long as they are aware of the need to enter a short
> message all will be well.

_______________________________________________________
> Meta Tracker <metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue141>
> _______________________________________________________
> _______________________________________________
> Tracker-discuss mailing list
> Tracker-discuss at python.org
> http://mail.python.org/mailman/listinfo/tracker-discuss
>

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/tracker-discuss/attachments/20070830/5534b9fe/attachment.htm 

From metatracker at psf.upfronthosting.co.za  Thu Aug 30 22:13:48 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Thu, 30 Aug 2007 20:13:48 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
In-Reply-To: <f74a6c2f0708301250h2f6446a3kd2985603b5d5d2d2@mail.gmail.com>
Message-ID: <46D724FA.6000708@v.loewis.de>


Martin v. L?wis added the comment:

>     Can we just try it as-is for a while? The number of
>     people who 'assign' issues to people other than themselves must not
>     be very large and as long as they are aware of the need to enter a
>     short message all will be well. 

Ok. However, we then need to communicate that very clearly to all users.
I can send a message to python-dev.

Regards,
Martin

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Thu Aug 30 22:49:19 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Thu, 30 Aug 2007 20:49:19 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
In-Reply-To: <f74a6c2f0708301250h2f6446a3kd2985603b5d5d2d2@mail.gmail.com>
Message-ID: <46D72D53.1080505@python.org>


Georg Brandl added the comment:

Paul Dubois schrieb:

> We did go through this discussion before; my experience was that
> such a change is undesirable, causing too much mail for trivial
> administrative changes. With your fix the assignee will get mail
> unless you do not enter some comment like 'Assigning to foo.', as in
> standard roundup. We also have the 'busybody' reactor that does send
> mail on every change to a mailing list. (Recall you had to fool with
> it so it would make a sensible message when no text had been
> supplied.) Can we just try it as-is for a while? The number of
> people who 'assign' issues to people other than themselves must not
> be very large and as long as they are aware of the need to enter a
> short message all will be well. 

Even though I'm aware of that, I'll still be annoyed about it every time
I type in a pointless "Assigning to foo" in the change note field.

Georg

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 31 01:17:08 2007
From: metatracker at psf.upfronthosting.co.za (Guido van Rossum)
Date: Thu, 30 Aug 2007 23:17:08 -0000
Subject: [Tracker-discuss] [issue144] email with one out of three patches is
	confusing
Message-ID: <1188515828.87.0.955745320995.issue144@psf.upfronthosting.co.za>


New submission from Guido van Rossum:

I just wasted some time when someone uploaded three patches to the tracker, but
only added a comment to the first one. This is reasonable. But because the
tracker only lets you upload one file, and suppresses mail when no message is
added, I only received an email with an attachment of the first file.

IMO we either shouldn't be sending attachments out (which would have forced me
to go to the tracker so I'd seen that there were three patches) or we should add
some JS to allow uploading multiple files in one request (like gmail does with
attachments).

----------
messages: 738
nosy: guido
priority: bug
status: unread
title: email with one out of three patches is confusing

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue144>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 31 07:59:17 2007
From: metatracker at psf.upfronthosting.co.za (Erik Forsberg)
Date: Fri, 31 Aug 2007 05:59:17 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
In-Reply-To: <f74a6c2f0708301250h2f6446a3kd2985603b5d5d2d2@mail.gmail.com>
	(Paul Dubois's message of "Thu, 30 Aug 2007 19:51:05 -0000")
Message-ID: <87ejhk453l.fsf@uterus.efod.se>


Erik Forsberg added the comment:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Dubois <metatracker at psf.upfronthosting.co.za> writes:

>> My proposed solution to this is to modify the busybody detector to
>> make it send mail to the nosy list whenever there's a change, even if
>> it's only a property change without message.
>>
>> Comments on that?
>>
>> \EF
>> - --
>> Erik Forsberg                 http://efod.se
>
> We did go through this discussion before; my experience was that such a
>> change is undesirable, causing too much mail for trivial administrative
>> changes. 

Your position on this matter is well known ;-).

Personally, I believe that people in common expect a mail for every
change. I definitely prefer it that way. If I have "subscribed" (added
myself to the nosy) for an issue, I definitely want to know things
like "Ah, someone got assigned to it - that's good, that means someone
cares" or "Aha, bug also present in Python version X.Y". 

That's the way most other public issue trackers I know of behave.

Regards,
\EF
- -- 
Erik Forsberg                 http://efod.se
GPG/PGP Key: 1024D/0BAC89D9
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFG164urJurFAusidkRAjK2AKCSQluX3usQhtbw0BGtVXlKwmoVKACeISUB
Pb/vnrcKreUHJDfMn1FH1Co=
=cqXK
-----END PGP SIGNATURE-----

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 31 08:05:36 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Fri, 31 Aug 2007 06:05:36 -0000
Subject: [Tracker-discuss] =?utf-8?q?=5Bissue144=5D_email_with_one_out_of_?=
	=?utf-8?q?three_patches_is=09confusing?=
In-Reply-To: <1188515828.87.0.955745320995.issue144@psf.upfronthosting.co.za>
Message-ID: <46D7AFAD.9010909@v.loewis.de>


Martin v. L?wis added the comment:

> IMO we either shouldn't be sending attachments out (which would have forced me
> to go to the tracker so I'd seen that there were three patches) or we should add
> some JS to allow uploading multiple files in one request (like gmail does with
> attachments).

Alternatively, would it work if one email message had been sent per
additional attachment?

----------
status: unread -> chatting
title: email with one out of three patches is confusing -> email with one out of three patches is	confusing

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue144>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 31 08:23:21 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Fri, 31 Aug 2007 06:23:21 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
In-Reply-To: <87ejhk453l.fsf@uterus.efod.se>
Message-ID: <46D7B3DD.2090509@python.org>


Georg Brandl added the comment:

Erik Forsberg schrieb:

> Personally, I believe that people in common expect a mail for every
> change. I definitely prefer it that way. If I have "subscribed" (added
> myself to the nosy) for an issue, I definitely want to know things
> like "Ah, someone got assigned to it - that's good, that means someone
> cares" or "Aha, bug also present in Python version X.Y". 

Indeed. Also, I'd have expected that in this matter, the preference of the
main *users* of the tracker outweighs the preference of the *admins*.

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 31 09:58:28 2007
From: metatracker at psf.upfronthosting.co.za (David Linke)
Date: Fri, 31 Aug 2007 07:58:28 -0000
Subject: [Tracker-discuss] [issue141] Should send email on assignment
Message-ID: <1188547108.49.0.398404802233.issue141@psf.upfronthosting.co.za>


David Linke added the comment:

Here is some reactor code for the original idea to inform about assignment:

def notifywhenassignedto(db, cl, nodeid, oldvalues):
    '''Send mail to user who is newly assigned to an issue
    '''
    assigned_user = cl.get(nodeid,'assignedto')
    if oldvalues.has_key('assignedto'):
        old_assigned_user = oldvalues['assignedto']
    else:
        old_assigned_user = -1
    if assigned_user == db.getuid(): return # don't react on assign to self
    if assigned_user and assigned_user != old_assigned_user:
        try:
            address = [db.user.get(assigned_user,'address')]
        except KeyError, message:
            raise roundupdb.DetectorError, message
        change_note = ('\nThe issue linked below has been assigned to you!%s' %
                       cl.generateChangeNote(nodeid, oldvalues))
        # send mail
        try:
            msgid = None
            cl.send_message(nodeid, msgid, change_note, address)
            logging.getLogger('detector').info('notifywhenassignedto:'
                          ' Sent email for issue %s to %s' % (nodeid, address))
        except roundupdb.MessageSendError, message:
            raise roundupdb.DetectorError, message

def init(db):
    db.issue.react('set', notifywhenassignedto)

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue141>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 31 15:00:31 2007
From: metatracker at psf.upfronthosting.co.za (Skip Montanaro)
Date: Fri, 31 Aug 2007 13:00:31 -0000
Subject: [Tracker-discuss] [issue145] List my "nosy" issues
Message-ID: <18136.4329.673258.815974@montanaro.dyndns.org>


New submission from Skip Montanaro:

It would be nice if there was some way I could list the issues where I'm on
the nosy list.  As I've been working my way through old tickets I've
occasionally added myself to the nosy list ("hmmm...  That's kind of
interesting.  I'll keep an eye on that.")  I didn't see any way to do this
using the search form.

Skip

----------
messages: 743
nosy: montanaro
status: unread
title: List my "nosy" issues

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue145>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 31 15:18:37 2007
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v._L=C3=B6wis?=)
Date: Fri, 31 Aug 2007 13:18:37 -0000
Subject: [Tracker-discuss] [issue145] List my "nosy" issues
Message-ID: <1188566317.26.0.893436822458.issue145@psf.upfronthosting.co.za>


Martin v. L?wis added the comment:

You are right that it's not in the search form. As a quick work-around, 
you can use the URL below

http://bugs.python.org/issue?nosy=skip.montanaro&%40columns=title,id,activity,assignee&%40sort=-activity&status=1&%40action=search

If you want to save this query, select

http://bugs.python.org/issue?@queryname=Nosy&nosy=skip.montanaro&@columns=title,id,activity,assignee&@sort=-activity&status=1&@action=search

----------
priority:  -> feature
status: unread -> chatting

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue145>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 31 15:20:04 2007
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Fri, 31 Aug 2007 13:20:04 -0000
Subject: [Tracker-discuss] [issue145] List my "nosy" issues
In-Reply-To: <18136.4329.673258.815974@montanaro.dyndns.org>
Message-ID: <46D8157F.5030400@python.org>


Georg Brandl added the comment:

Skip Montanaro schrieb:
> New submission from Skip Montanaro:
> 
> It would be nice if there was some way I could list the issues where I'm on
> the nosy list.  As I've been working my way through old tickets I've
> occasionally added myself to the nosy list ("hmmm...  That's kind of
> interesting.  I'll keep an eye on that.")  I didn't see any way to do this
> using the search form.

As a workaround, you can use a query like
http://bugs.python.org/issue?@action=search&nosy=skip.montanaro&status=open&status=pending&@columns=id,activity,title,creator,assignee

(adapt the @columns parameter to your liking)

(you should also be able to save it to your sidebar by appending a
@queryname=foo parameter).

Georg

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue145>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 31 15:27:11 2007
From: metatracker at psf.upfronthosting.co.za (Guido van Rossum)
Date: Fri, 31 Aug 2007 13:27:11 -0000
Subject: [Tracker-discuss] =?utf-8?q?=5Bissue144=5D_email_with_one_out_of_?=
	=?utf-8?q?three_patches_is=09confusing?=
Message-ID: <1188566831.47.0.608711098341.issue144@psf.upfronthosting.co.za>


Guido van Rossum added the comment:

Yes, that would work too, and is probably easiest.

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue144>
_______________________________________________________

From metatracker at psf.upfronthosting.co.za  Fri Aug 31 16:12:21 2007
From: metatracker at psf.upfronthosting.co.za (Skip Montanaro)
Date: Fri, 31 Aug 2007 14:12:21 -0000
Subject: [Tracker-discuss] [issue145] List my "nosy" issues
In-Reply-To: <46D8157F.5030400@python.org>
Message-ID: <18136.8641.448169.753441@montanaro.dyndns.org>


Skip Montanaro added the comment:

Georg & Martin,

Thanks for the tips.  Those work fine.

Skip

_______________________________________________________
Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue145>
_______________________________________________________