From techtonik at gmail.com  Mon Oct 18 10:28:16 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Mon, 18 Oct 2010 11:28:16 +0300
Subject: [Tracker-discuss] offline 10-10-18
Message-ID: <AANLkTimf4DCnkc3r560NpfRhe+oB+pZtkXXRFUPGVZfH@mail.gmail.com>

http://bugs.python.org/issue9138
can't connect

is there a monitor to track status?
--
anatoly t.

From martin at v.loewis.de  Mon Oct 18 11:04:15 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Mon, 18 Oct 2010 11:04:15 +0200
Subject: [Tracker-discuss] [pydotorg-www] offline 10-10-18
In-Reply-To: <AANLkTimf4DCnkc3r560NpfRhe+oB+pZtkXXRFUPGVZfH@mail.gmail.com>
References: <AANLkTimf4DCnkc3r560NpfRhe+oB+pZtkXXRFUPGVZfH@mail.gmail.com>
Message-ID: <4CBC0D8F.5040208@v.loewis.de>

I have contacted Upfront.

Regards,
Martin


From martin at v.loewis.de  Mon Oct 18 11:23:38 2010
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Mon, 18 Oct 2010 11:23:38 +0200
Subject: [Tracker-discuss] [pydotorg-www] offline 10-10-18
In-Reply-To: <AANLkTimf4DCnkc3r560NpfRhe+oB+pZtkXXRFUPGVZfH@mail.gmail.com>
References: <AANLkTimf4DCnkc3r560NpfRhe+oB+pZtkXXRFUPGVZfH@mail.gmail.com>
Message-ID: <4CBC121A.8020501@v.loewis.de>

It's up again, after a restart.

Martin


From techtonik at gmail.com  Mon Oct 18 23:29:44 2010
From: techtonik at gmail.com (anatoly techtonik)
Date: Tue, 19 Oct 2010 00:29:44 +0300
Subject: [Tracker-discuss] [pydotorg-www] offline 10-10-18
In-Reply-To: <4CBC121A.8020501@v.loewis.de>
References: <AANLkTimf4DCnkc3r560NpfRhe+oB+pZtkXXRFUPGVZfH@mail.gmail.com>
	<4CBC121A.8020501@v.loewis.de>
Message-ID: <AANLkTi=F1S7G=RAxMFg6FsZDfF8f6oRYB7ATWeqCTONy@mail.gmail.com>

Thanks.
But I am still curious about what happened and how many hours tracker was down.
Is there a monitor to mail here if anything went offline?

Don't you find it strange that I am the only one who reported the
outage and I am not really active in Python development (this probably
the first time I opened tracker page in last 10 days)?

It is also interesting:
 * If the instability is repeatable
 * If it can be caused by security problem with Roundup
 * If we should offer more prominent way to report outages
--
anatoly t.



On Mon, Oct 18, 2010 at 12:23 PM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> It's up again, after a restart.
>
> Martin
>
>

From stephen at xemacs.org  Tue Oct 19 08:56:33 2010
From: stephen at xemacs.org (Stephen J. Turnbull)
Date: Tue, 19 Oct 2010 15:56:33 +0900
Subject: [Tracker-discuss] [pydotorg-www] offline 10-10-18
In-Reply-To: <AANLkTi=F1S7G=RAxMFg6FsZDfF8f6oRYB7ATWeqCTONy@mail.gmail.com>
References: <AANLkTimf4DCnkc3r560NpfRhe+oB+pZtkXXRFUPGVZfH@mail.gmail.com>
	<4CBC121A.8020501@v.loewis.de>
	<AANLkTi=F1S7G=RAxMFg6FsZDfF8f6oRYB7ATWeqCTONy@mail.gmail.com>
Message-ID: <878w1un00u.fsf@uwakimon.sk.tsukuba.ac.jp>

anatoly techtonik writes:

 > Don't you find it strange that I am the only one who reported the
 > outage and I am not really active in Python development (this probably
 > the first time I opened tracker page in last 10 days)?

Not strange at all.  Random things like that do happen.

Also, I don't know about you, but my network has been quite unreliable
across regions, oh, once or twice a month.  Sometimes it fails on the
U.S., sometimes it fails on Europe, sometimes on south or east Asia
(and all too often the whole thing goes down locally; thank heaven the
public Internet is more reliable than my university's intranet!)  If
others are experiencing the same, they may just wait 12-24 hours
before reporting a problem.

It's good that you report, but it's not that surprising that you were
the first.  And you may or may not be the only reporter; I would guess
that private reports to me (or an admin-specific alias) outnumber
public reports to lists by 2:1 for the trackers I administer.

From georg at python.org  Tue Oct 19 09:20:17 2010
From: georg at python.org (Georg Brandl)
Date: Tue, 19 Oct 2010 09:20:17 +0200
Subject: [Tracker-discuss] [pydotorg-www] offline 10-10-18
In-Reply-To: <AANLkTi=F1S7G=RAxMFg6FsZDfF8f6oRYB7ATWeqCTONy@mail.gmail.com>
References: <AANLkTimf4DCnkc3r560NpfRhe+oB+pZtkXXRFUPGVZfH@mail.gmail.com>	<4CBC121A.8020501@v.loewis.de>
	<AANLkTi=F1S7G=RAxMFg6FsZDfF8f6oRYB7ATWeqCTONy@mail.gmail.com>
Message-ID: <4CBD46B1.3040502@python.org>

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

Am 18.10.2010 23:29, schrieb anatoly techtonik:
> Thanks.
> But I am still curious about what happened and how many hours tracker was down.
> Is there a monitor to mail here if anything went offline?
> 
> Don't you find it strange that I am the only one who reported the
> outage and I am not really active in Python development (this probably
> the first time I opened tracker page in last 10 days)?

Be assured, the tracker was not down for 10 days.  When I notice that some
service is unavailable, I usually wait for a few hours before reporting it;
by that time you had already notified this list.

Georg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)

iEYEARECAAYFAky9RrEACgkQN9GcIYhpnLBmCgCeNkxo73iRLPwvexLUK/Tnl4H4
7dwAnRn8E5u5J3vYyRM8PGbRr2YnvYd1
=u6ti
-----END PGP SIGNATURE-----

From izak at upfrontsystems.co.za  Tue Oct 19 09:30:11 2010
From: izak at upfrontsystems.co.za (Izak Burger)
Date: Tue, 19 Oct 2010 09:30:11 +0200
Subject: [Tracker-discuss] [pydotorg-www] offline 10-10-18
In-Reply-To: <AANLkTi=F1S7G=RAxMFg6FsZDfF8f6oRYB7ATWeqCTONy@mail.gmail.com>
References: <AANLkTimf4DCnkc3r560NpfRhe+oB+pZtkXXRFUPGVZfH@mail.gmail.com>	<4CBC121A.8020501@v.loewis.de>
	<AANLkTi=F1S7G=RAxMFg6FsZDfF8f6oRYB7ATWeqCTONy@mail.gmail.com>
Message-ID: <4CBD4903.4010704@upfrontsystems.co.za>

On 18/10/2010 23:29, anatoly techtonik wrote:
> Thanks.
> But I am still curious about what happened and how many hours tracker was down.
> Is there a monitor to mail here if anything went offline?

We have nagios monitoring on that machine. The only problem is, nagios 
runs on nina, and nina is the host to the psf virtual host. So sometimes 
they go down at the same time, although it usually goes for months 
without any problems at all.

Also, it sometimes goes down at night, and I will only notice the next 
morning.

But... we need to do something about that machine anyway. We need to 
upgrade it, which basically means we need to get a new one, migrate it, 
change the ip address, etc etc. Its on my todo list, but I need to do 
the costing again and discuss it with Roch?.

I can answer the first of your questions immediately. The instability is 
not repeatable. The only real thing I did find is that there appears to 
be issues with the ext3 file system driver, that will occasionally cause 
a corrupted journal and cause segfaults or it will report a full file 
system when it isn't. I therefore dropped the journal, as it is in fact 
more stable on ext2. To make matters worse, the same thing happened on 
my laptop just a few days ago, with a fairly new kernel, so it seems 
there is an as yet unreported bug in ext3. But I'm just speculating.

regards,
Izak

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 03:45:16 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 29 Oct 2010 01:45:16 +0000
Subject: [Tracker-discuss] [issue335] "out of date" resolution on open issue
In-Reply-To: <1272111342.82.0.249947227102.issue335@psf.upfronthosting.co.za>
Message-ID: <1288316716.97.0.195550959661.issue335@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

The Python bug is closed now.  Unless you can rephrase ?fix tracker? into something more precise, I suggest this issue be closed.

----------
nosy: +eric.araujo, loewis
status: unread -> resolved

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 03:47:01 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 29 Oct 2010 01:47:01 +0000
Subject: [Tracker-discuss] [issue278] 1.4.8 fixes for other PSF trackers
In-Reply-To: <1240793302.05.0.121079776163.issue278@psf.upfronthosting.co.za>
Message-ID: <1288316821.09.0.137180343412.issue278@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Is this still relevant?

----------
nosy: +eric.araujo, loewis
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 04:02:49 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 29 Oct 2010 02:02:49 +0000
Subject: [Tracker-discuss] [issue340] Add 'website' component to report
	www.python.org issues
In-Reply-To: <1275479930.06.0.353171360103.issue340@psf.upfronthosting.co.za>
Message-ID: <1288317769.24.0.789773609707.issue340@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

The rule of thumb is that the bug tracker collect reports for things that are shipped in a CPython distribution.  There is a documentation component not because there is docs.python.org but because there is a Doc directory in source distributions.  Mailing lists are used for website bugs and improvements, as Ezio reminded.  Suggest closing this.

----------
nosy: +eric.araujo

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 05:28:38 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 29 Oct 2010 03:28:38 +0000
Subject: [Tracker-discuss] [issue339] Colors for quoted text
In-Reply-To: <1274389686.18.0.834229227802.issue339@psf.upfronthosting.co.za>
Message-ID: <1288322918.74.0.730930698692.issue339@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Sure, good idea.  Do you know if there is software out there doing that?

----------
nosy: +eric.araujo
title: Colored sintax for quoted text -> Colors for quoted text

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 05:45:25 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 29 Oct 2010 03:45:25 +0000
Subject: [Tracker-discuss] [issue20] Add in SVN plugin?
Message-ID: <1288323925.16.0.521935493597.issue20@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

This is now outdated.

----------
nosy: +eric.araujo

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 06:07:27 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 29 Oct 2010 04:07:27 +0000
Subject: [Tracker-discuss] [issue156] Have a Core Bug Chaser Create a Bug
	Reporting Screencast
In-Reply-To: <1189687665.63.0.143239718478.issue156@psf.upfronthosting.co.za>
Message-ID: <1288325247.89.0.931409612899.issue156@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Will this be a part of your PSF-sponsored job?  I prefer text over video personally but understand screencasts are en vogue, so.

----------
nosy: +brett.cannon, eric.araujo

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 06:16:39 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 29 Oct 2010 04:16:39 +0000
Subject: [Tracker-discuss] [issue347] Reassign all doc issues from
	georg.brandl to docs@python
In-Reply-To: <1279654772.31.0.343558345169.issue347@psf.upfronthosting.co.za>
Message-ID: <1288325799.82.0.36299281731.issue347@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

There are 49 reports still assigned to Georg instead of docs at python.

----------
nosy: +eric.araujo, loewis
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 06:17:51 2010
From: metatracker at psf.upfronthosting.co.za (Brett C.)
Date: Fri, 29 Oct 2010 04:17:51 +0000
Subject: [Tracker-discuss] [issue156] Have a Core Bug Chaser Create a Bug
	Reporting Screencast
In-Reply-To: <1189687665.63.0.143239718478.issue156@psf.upfronthosting.co.za>
Message-ID: <1288325871.54.0.908936311106.issue156@psf.upfronthosting.co.za>


Brett C. <brett at python.org> added the comment:

Wasn't planning on it, but it could be a possibility if people really show an interest and it is decided to be worth my time.

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 06:18:35 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 29 Oct 2010 04:18:35 +0000
Subject: [Tracker-discuss] [issue120] Allow users to report msg/file
	instances as misclassified
In-Reply-To: <87sl79vn7r.fsf@uterus.efod.se>
Message-ID: <1288325915.93.0.518004139045.issue120@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

David, I hope you won?t mind me adding you to nosy.  What should we do with this problem?  When a message gets misclassified as spam, what is the user to do?

----------
nosy: +eric.araujo, r.david.murray

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 06:27:38 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 29 Oct 2010 04:27:38 +0000
Subject: [Tracker-discuss] [issue355] Rietveld integration non-working
In-Reply-To: <1288326458.29.0.270667905573.issue355@psf.upfronthosting.co.za>
Message-ID: <1288326458.29.0.270667905573.issue355@psf.upfronthosting.co.za>


New submission from ?ric Araujo <merwok at netwok.org>:

On http://bugs.python.org/issue6715, I tried editing the branch info to make a review link happen, but it did not.  Alexander reported the same problem with http://bugs.python.org/issue5109 but now there is a link.  How was it fixed?

----------
messages: 1818
nosy: belopolsky, eric.araujo, loewis, pitrou
priority: bug
status: unread
title: Rietveld integration non-working

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 06:28:28 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Fri, 29 Oct 2010 04:28:28 +0000
Subject: [Tracker-discuss] [issue323] email is not obfuscated in the msg
In-Reply-To: <1267435647.66.0.658210680138.issue323@psf.upfronthosting.co.za>
Message-ID: <1288326508.54.0.509039768853.issue323@psf.upfronthosting.co.za>


?ric Araujo <merwok at netwok.org> added the comment:

Agree with Daniel.

----------
nosy: +eric.araujo

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 06:55:37 2010
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Fri, 29 Oct 2010 04:55:37 +0000
Subject: [Tracker-discuss] [issue20] Add in SVN plugin?
Message-ID: <1288328137.62.0.302138220445.issue20@psf.upfronthosting.co.za>


Georg Brandl <g.brandl at gmx.net> added the comment:

Then it would be best to close it :)

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

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 08:16:04 2010
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 29 Oct 2010 06:16:04 +0000
Subject: [Tracker-discuss] [issue20] Add in SVN plugin?
Message-ID: <1288332964.84.0.684932026545.issue20@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

What does it mean "outdated"? If it is already implemented, then a proper fix would be to supply a link to appropriate chapter in developer's documentation.

If the bug is outdated, because of switch to Mercurial, then this doesn't fix the original request to modify issues through commit messages.

----------
nosy: +techtonik
status: resolved -> chatting

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 08:35:05 2010
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 29 Oct 2010 06:35:05 +0000
Subject: [Tracker-discuss] [issue323] email is not obfuscated in the msg
In-Reply-To: <1267435647.66.0.658210680138.issue323@psf.upfronthosting.co.za>
Message-ID: <1288334105.29.0.800416264193.issue323@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

3. Process on display: obscure for anonymous and display for logged in users.

List is not a concern - it has its own obscuring rules.

----------
nosy: +techtonik

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 08:38:06 2010
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 29 Oct 2010 06:38:06 +0000
Subject: [Tracker-discuss] [issue355] Rietveld integration non-working
In-Reply-To: <1288326458.29.0.270667905573.issue355@psf.upfronthosting.co.za>
Message-ID: <1288334286.29.0.43589926576.issue355@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Where is the design document about Rietveld integration anyway?

----------
nosy: +techtonik
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 08:46:37 2010
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 29 Oct 2010 06:46:37 +0000
Subject: [Tracker-discuss] [issue156] Have a Core Bug Chaser Create a Bug
	Reporting Screencast
In-Reply-To: <1189687665.63.0.143239718478.issue156@psf.upfronthosting.co.za>
Message-ID: <1288334797.91.0.689886302231.issue156@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Good start would be with collecting user stories. Because the process may be different for core developers and users.

For example, this story "I'm overwhelmed with the query options" is extremely good. I may add a few more - "I want find all bugs for Python module", "I want to see the source code where bug happens", "I want to classify my bugs", "I want to vote on features I like", "I want to rate and filter comments" etc.

----------
nosy: +techtonik

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 08:48:08 2010
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 29 Oct 2010 06:48:08 +0000
Subject: [Tracker-discuss] [issue347] Reassign all doc issues from
	georg.brandl to docs@python
In-Reply-To: <1279654772.31.0.343558345169.issue347@psf.upfronthosting.co.za>
Message-ID: <1288334888.45.0.341286090843.issue347@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

And where are they?

----------
nosy: +techtonik

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 08:56:18 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Fri, 29 Oct 2010 06:56:18 +0000
Subject: [Tracker-discuss] [issue355] Rietveld integration non-working
In-Reply-To: <1288326458.29.0.270667905573.issue355@psf.upfronthosting.co.za>
Message-ID: <4CCA700F.9040509@v.loewis.de>


Martin v. L?wis <martin at v.loewis.de> added the comment:

> On http://bugs.python.org/issue6715, I tried editing the branch info
> to make a review link happen, but it did not.  Alexander reported the
> same problem with http://bugs.python.org/issue5109 but now there is a
> link.  How was it fixed?

The roundup integration is currently turned off, since it caused a
server overload.

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 09:03:33 2010
From: metatracker at psf.upfronthosting.co.za (Georg Brandl)
Date: Fri, 29 Oct 2010 07:03:33 +0000
Subject: [Tracker-discuss] [issue347] Reassign all doc issues from
	georg.brandl to docs@python
In-Reply-To: <1279654772.31.0.343558345169.issue347@psf.upfronthosting.co.za>
Message-ID: <1288335813.03.0.0385942473785.issue347@psf.upfronthosting.co.za>


Georg Brandl <g.brandl at gmx.net> added the comment:

I would guess they are in the tracker at bugs.python.org.

----------
nosy: +gbrandl

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 09:33:16 2010
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 29 Oct 2010 07:33:16 +0000
Subject: [Tracker-discuss] [issue78] Make use of keywords more obvious
In-Reply-To: <1168896602.03.0.530314090964.issue78@psf.upfronthosting.co.za>
Message-ID: <1288337596.63.0.871368762839.issue78@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

+1 for free form keywords. I'd also allow everybody to change them (like adding easy tags).
Or have a premoderation of keywords edits if smb. afraid of misuse.
Or at least have list of people with privileges to edit keywords accessible from popup help.

----------
nosy: +techtonik

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 09:44:09 2010
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 29 Oct 2010 07:44:09 +0000
Subject: [Tracker-discuss] [issue347] Reassign all doc issues from
	georg.brandl to docs@python
In-Reply-To: <1279654772.31.0.343558345169.issue347@psf.upfronthosting.co.za>
Message-ID: <1288338249.83.0.0908725033385.issue347@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

It's nice to meet a fellow developer. Only developers can give absolutely correct and absolutely useless answers. =)

I mean that it will be more useful to see the query. It will also help to track the progress.

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 09:46:33 2010
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 29 Oct 2010 07:46:33 +0000
Subject: [Tracker-discuss] [issue347] Reassign all doc issues from
	georg.brandl to docs@python
In-Reply-To: <1279654772.31.0.343558345169.issue347@psf.upfronthosting.co.za>
Message-ID: <1288338393.6.0.54567434076.issue347@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Unfortunately, my attempt to add this query has been classified as span.

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 09:47:43 2010
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 29 Oct 2010 07:47:43 +0000
Subject: [Tracker-discuss] [issue347] Reassign all doc issues from
	georg.brandl to docs@python
In-Reply-To: <1279654772.31.0.343558345169.issue347@psf.upfronthosting.co.za>
Message-ID: <1288338463.27.0.561205913586.issue347@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

BTW, who are the people who can do reassignments?

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 09:48:11 2010
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 29 Oct 2010 07:48:11 +0000
Subject: [Tracker-discuss] [issue347] Reassign all doc issues from
	georg.brandl to docs@python
In-Reply-To: <1279654772.31.0.343558345169.issue347@psf.upfronthosting.co.za>
Message-ID: <1288338491.66.0.368047344821.issue347@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

I mean that they should be in CC for this to be heard.

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 09:50:41 2010
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 29 Oct 2010 07:50:41 +0000
Subject: [Tracker-discuss] [issue355] Rietveld integration non-working
In-Reply-To: <4CCA700F.9040509@v.loewis.de>
Message-ID: <AANLkTi=8agOKE57=RHGeH7gae8uoPD8UN3AYBLsnLdLd@mail.gmail.com>


anatoly techtonik <techtonik at gmail.com> added the comment:

On Fri, Oct 29, 2010 at 9:56 AM, Martin v. L?wis wrote:
>
> The roundup integration is currently turned off, since it caused a
> server overload.

Why is it so ineffective?
Care to elaborate or share the code?

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 10:00:34 2010
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 29 Oct 2010 08:00:34 +0000
Subject: [Tracker-discuss] [issue339] Colors for quoted text
In-Reply-To: <1274389686.18.0.834229227802.issue339@psf.upfronthosting.co.za>
Message-ID: <1288339234.66.0.00793992154771.issue339@psf.upfronthosting.co.za>


anatoly techtonik <techtonik at gmail.com> added the comment:

Trac - http://trac.edgewall.org/ticket/9220#comment:12
Rietveld - http://codereview.appspot.com/2442042/diff/7001/upload.py - expand collapsed comments and see how quoted text is handled there.

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 11:44:51 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Fri, 29 Oct 2010 09:44:51 +0000
Subject: [Tracker-discuss] [issue355] Rietveld integration non-working
In-Reply-To: <AANLkTi=8agOKE57=RHGeH7gae8uoPD8UN3AYBLsnLdLd@mail.gmail.com>
Message-ID: <4CCA9791.7040009@v.loewis.de>


Martin v. L?wis <martin at v.loewis.de> added the comment:

> Why is it so ineffective?
> Care to elaborate

I don't know - if I knew, I would have fixed it.

> or share the code?

It's all checked in.

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

From martin at v.loewis.de  Fri Oct 29 11:44:49 2010
From: martin at v.loewis.de (=?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=)
Date: Fri, 29 Oct 2010 11:44:49 +0200
Subject: [Tracker-discuss] [issue355] Rietveld integration non-working
In-Reply-To: <AANLkTi=8agOKE57=RHGeH7gae8uoPD8UN3AYBLsnLdLd@mail.gmail.com>
References: <AANLkTi=8agOKE57=RHGeH7gae8uoPD8UN3AYBLsnLdLd@mail.gmail.com>
Message-ID: <4CCA9791.7040009@v.loewis.de>

> Why is it so ineffective?
> Care to elaborate

I don't know - if I knew, I would have fixed it.

> or share the code?

It's all checked in.

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 12:08:27 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Fri, 29 Oct 2010 10:08:27 +0000
Subject: [Tracker-discuss] [issue347] Reassign all doc issues from
	georg.brandl to docs@python
In-Reply-To: <1279654772.31.0.343558345169.issue347@psf.upfronthosting.co.za>
Message-ID: <1288346907.25.0.57046352229.issue347@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

I have now mass-reassigned these issues.

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

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 12:22:06 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Fri, 29 Oct 2010 10:22:06 +0000
Subject: [Tracker-discuss] [issue339] Colors for quoted text
In-Reply-To: <1274389686.18.0.834229227802.issue339@psf.upfronthosting.co.za>
Message-ID: <1288347726.21.0.773160968639.issue339@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

Can somebody propose a specific CSS that should be used? In particular, what should the colors be?

----------
nosy: +loewis

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

From metatracker at psf.upfronthosting.co.za  Fri Oct 29 13:02:27 2010
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Fri, 29 Oct 2010 11:02:27 +0000
Subject: [Tracker-discuss] [issue356] Maintain tracker modifications as
	Mercurial patch Queues
In-Reply-To: <1288350147.59.0.871553265003.issue356@psf.upfronthosting.co.za>
Message-ID: <1288350147.59.0.871553265003.issue356@psf.upfronthosting.co.za>


New submission from anatoly techtonik <techtonik at gmail.com>:

To make maintenance of bug trackers easier and encourage upstream collaborations, I propose to do tracker maintenance using Mercurial patch Queues:

1. Official RoundUp repository is mirrored to our local Mercurial ones.
2. No commits are made into mirror.
3. Patches are instead stacked into MQ repositories - one for each instance.
4. Instances are synchronized to new Roundup version using the following process
  4.1. New changes are pulled into local clone
  4.2. MQ patches are applies (and fixed if needed)
  4.3. Tests are run
  4.4. Repository is exported to production

Once proven, this can be extended to MoinMoin maintenance as well.

[1] http://psf.upfronthosting.co.za/roundup/meta/issue278

----------
messages: 1839
nosy: techtonik
priority: wish
status: unread
title: Maintain tracker modifications as Mercurial patch Queues

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

From metatracker at psf.upfronthosting.co.za  Sun Oct 31 15:53:12 2010
From: metatracker at psf.upfronthosting.co.za (Sergei)
Date: Sun, 31 Oct 2010 14:53:12 +0000
Subject: [Tracker-discuss] [issue357] Bootstrapping class not in
	Py.BOOTSTRAP_TYPES
In-Reply-To: <1288536792.61.0.21495685169.issue357@psf.upfronthosting.co.za>
Message-ID: <1288536792.61.0.21495685169.issue357@psf.upfronthosting.co.za>


New submission from Sergei <sergei175 at mail.ru>:

Bootstrapping class not in Py.BOOTSTRAP_TYPES[class=class org.python.core.PyStringMap]

----------
messages: 1840
nosy: sergei175
priority: bug
status: unread
title: Bootstrapping class not in Py.BOOTSTRAP_TYPES

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

From metatracker at psf.upfronthosting.co.za  Sun Oct 31 15:57:15 2010
From: metatracker at psf.upfronthosting.co.za (Sergei)
Date: Sun, 31 Oct 2010 14:57:15 +0000
Subject: [Tracker-discuss] [issue357] Bootstrapping class not in
	Py.BOOTSTRAP_TYPES
In-Reply-To: <1288536792.61.0.21495685169.issue357@psf.upfronthosting.co.za>
Message-ID: <1288537035.48.0.802618103151.issue357@psf.upfronthosting.co.za>


Sergei <sergei175 at mail.ru> added the comment:

I think Jython interpreter is complaining for the new jython 2.5.2r2 release.
 Example: I've replaced jython in this Jython shell:
 ttp://dev.artenum.com/projects/JRosetta/download

 and now every time I execute the shell, I have:
 init: Bootstrapping class not in Py.BOOTSTRAP_TYPES[class=class org.python.core.PyStringMap]

 This start to appear from the Jython 2.5.2b version.

 I'm using 

  
Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
Java HotSpot(TM) Server VM (build 17.1-b03, mixed mode)


 on ubuntu 10.10

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

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

From metatracker at psf.upfronthosting.co.za  Sun Oct 31 16:17:05 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 31 Oct 2010 15:17:05 +0000
Subject: [Tracker-discuss] [issue357] Bootstrapping class not in
	Py.BOOTSTRAP_TYPES
In-Reply-To: <1288536792.61.0.21495685169.issue357@psf.upfronthosting.co.za>
Message-ID: <1288538225.5.0.526582373614.issue357@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

Please understand that this is not the Jython bugtracker, but the meta-tracker (i.e. for tracking bugs in the bug trackers).

----------
nosy: +loewis
status: chatting -> resolved

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

From metatracker at psf.upfronthosting.co.za  Sun Oct 31 16:45:46 2010
From: metatracker at psf.upfronthosting.co.za (Sergei)
Date: Sun, 31 Oct 2010 15:45:46 +0000
Subject: [Tracker-discuss] [issue357] Bootstrapping class not in
	Py.BOOTSTRAP_TYPES
In-Reply-To: <1288538225.5.0.526582373614.issue357@psf.upfronthosting.co.za>
Message-ID: <4CCD8F38.6060602@mail.ru>


Sergei <sergei175 at mail.ru> added the comment:

Thanks, but how can I access the "bug reports"?
  When I go http://bugs.jython.org/Project/bugs.html

  I've got this:

  Error response

Error code 404.

Message: /jython/Project/bugs.html.

Error code explanation: 404 = Nothing matches the given URI.

On 10/31/2010 10:17 AM, Martin v. L??wis wrote:
> Martin v. L??wis<martin at v.loewis.de>  added the comment:
>
> Please understand that this is not the Jython bugtracker, but the meta-tracker (i.e. for tracking bugs in the bug trackers).
>
> ----------
> nosy: +loewis
> status: chatting ->  resolved
>
> _______________________________________________________
> PSF Meta Tracker<metatracker at psf.upfronthosting.co.za>
> <http://psf.upfronthosting.co.za/roundup/meta/issue357>
> _______________________________________________________
>
> .
>

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

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue357>
_______________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20101031/52fe1a10/attachment.html>

From metatracker at psf.upfronthosting.co.za  Sun Oct 31 16:50:25 2010
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sun, 31 Oct 2010 15:50:25 +0000
Subject: [Tracker-discuss] [issue357] Bootstrapping class not in
	Py.BOOTSTRAP_TYPES
In-Reply-To: <1288536792.61.0.21495685169.issue357@psf.upfronthosting.co.za>
Message-ID: <1288540225.94.0.96021435094.issue357@psf.upfronthosting.co.za>


Martin v. L?wis <martin at v.loewis.de> added the comment:

Use just bugs.jython.org.

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

From metatracker at psf.upfronthosting.co.za  Sun Oct 31 20:49:39 2010
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 31 Oct 2010 19:49:39 +0000
Subject: [Tracker-discuss] [issue358] Deltas in summary report
In-Reply-To: <1288554579.37.0.646958578756.issue358@psf.upfronthosting.co.za>
Message-ID: <1288554579.37.0.646958578756.issue358@psf.upfronthosting.co.za>


New submission from Ezio Melotti <ezio.melotti at gmail.com>:

The attached patch changes the values in the header of the summary report to display the difference with the previous week rather than the count of issues that have been created/closed.
I'll do some more tests before committing it.

See also http://mail.python.org/pipermail/python-dev/2010-October/104840.html and http://mail.python.org/pipermail/python-dev/2010-September/104054.html

----------
assignedto: ezio.melotti
files: issue358.diff
messages: 1845
nosy: ezio.melotti, gbrandl, pitrou, r.david.murray
priority: feature
status: testing
title: Deltas in summary report

_______________________________________________________
PSF Meta Tracker <metatracker at psf.upfronthosting.co.za>
<http://psf.upfronthosting.co.za/roundup/meta/issue358>
_______________________________________________________
-------------- next part --------------
Index: scripts/roundup-summary
===================================================================
--- scripts/roundup-summary	(revision 86022)
+++ scripts/roundup-summary	(working copy)
@@ -59,10 +59,10 @@
 To view or respond to any of the issues listed below, click on the issue.
 Do NOT respond to this message.
 
-Issues stats:
-  open   %(open)5d (%(open_new)+3d)
-  closed %(closed)5d (%(closed_new)+3d)
-  total  %(total)5d (%(total_new)+3d)
+Issues counts and deltas:
+  open   %(open)5d (%(open_delta)+3d)
+  closed %(closed)5d (%(closed_delta)+3d)
+  total  %(total)5d (%(total_delta)+3d)
 
 Open issues with patches: %(patches)-5d"""
 
@@ -207,29 +207,36 @@
         start_date, end_date = self.start_date, self.end_date
         start_str = start_date.pretty(format='%F') # %F -> yyyy-mm-dd
         end_str = end_date.pretty(format='%F')
+        # counters for current values
         open_tot = closed_tot = all_tot = 0
-        open_new = closed_new = all_old = 0
+        # counters for previous values
+        open_old = closed_old = all_old = 0
         with_patch = 0
         patch_id = DB.keyword.lookup('patch')
         for id, issue in self.issues.iteritems():
             # don't include issues created after the end date
             if issue['creation'] > end_date:
                 continue
+            all_tot += 1
             if issue['creation'] < start_date:
                 all_old += 1
-            all_tot += 1
+                # check if the issue was closed at the end of the previous
+                # period
+                if issue['last_period_status'] in OPTIONS.resolved:
+                    closed_old += 1
+                else:
+                    open_old += 1
+            # check if the issue is closed now
             if issue['closed']:
                 closed_tot += 1
-                if issue['closed_date'] >= start_date:
-                    closed_new += 1
             else:
                 open_tot += 1
-                if ((issue['creation'] >= start_date) or
-                    (issue['reopened_date'] >= start_date)):
-                    open_new += 1
                 if patch_id in issue['keyword_ids']:
                     with_patch += 1
-        all_new = all_tot - all_old
+        all_delta = all_tot - all_old
+        open_delta = open_tot - open_old
+        closed_delta = closed_tot - closed_old
+        assert all_delta == open_delta + closed_delta
         # save the values in an attribute to avoid calculating it twice
         # when both the txt and the HTML header are needed (i.e. when sending
         # HTML mails)
@@ -237,9 +244,9 @@
             timespan='%s - %s' % (start_str, end_str),
             tracker_url=DB.config.TRACKER_WEB,
             tracker_name=DB.config.TRACKER_NAME,
-            open=open_tot, open_new=open_new,
-            closed=closed_tot, closed_new=closed_new,
-            total=all_tot, total_new=all_new,
+            open=open_tot, open_delta=open_delta,
+            closed=closed_tot, closed_delta=closed_delta,
+            total=all_tot, total_delta=all_delta,
             patches=with_patch,
         )
         return header % self.header_content
@@ -497,6 +504,7 @@
         msgs_in_period = 0,
         status = None,
         real_status = sid2name(attrs['status']), # Avoid a bug in get_issue_attrs
+        last_period_status = None, # the status of the issue before start_date
         actor = None,
         activity = None,
         keyword_ids = kwds,
@@ -543,6 +551,8 @@
     # this trick catches the first time we are in the interval of interest
     if helper['activity2'] < dates.to_value:
         update(issue, helper)
+    status_changes = []
+    old_time = issue['creation']
     for _, time, userid, act, data in helper['journal']:
         in_period =  dates.to_value > time >= dates.from_value
         if in_period:
@@ -558,6 +568,8 @@
                     issue['msgs_in_period'] -= 1
             if 'status' in data:
                 helper['status1'] = sid2name(data['status'])
+                status_changes.append((old_time, helper['status1']))
+                old_time = time
                 if time < dates.to_value:
                     # want the last reopener only
                     if reopened(helper) and not issue['reopened']:
@@ -573,6 +585,16 @@
                     issue['real_status'] in OPTIONS.resolved):
                     issue['closer'] = userid
                     issue['closed_date'] = time
+    status_changes.append((old_time, issue['real_status']))
+    # if the status didn't change and this is still None set it to 'open',
+    # leave it to None for new issues
+    if issue['creation'] < dates.from_value:
+        print issue['issue_num'], status_changes
+        for time, status in status_changes:
+            if time < dates.from_value:
+                issue['last_period_status'] = status
+        if issue['last_period_status'] is None:
+            issue['last_period_status'] = 'open'
     # get these set if not done before
     update(issue, helper)
     last_opened = issue['reopened_date'] or issue['creation']