From metatracker at psf.upfronthosting.co.za  Mon Jul  2 22:20:02 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?=C3=89ric_Araujo?=)
Date: Mon, 02 Jul 2012 20:20:02 +0000
Subject: [Tracker-discuss] [issue471] Link from Rietveld issue to Roundup
	issue
Message-ID: <1341260402.17.0.425409478246.issue471@psf.upfronthosting.co.za>


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

There used to be a link from b.py.o/review/NNN/ to b.py.o/NNN ; I guess a recent update broke it.

----------
messages: 2551
nosy: eric.araujo, ezio.melotti
priority: bug
status: unread
title: Link from Rietveld issue to Roundup issue

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

From metatracker at psf.upfronthosting.co.za  Fri Jul  6 20:30:39 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Fri, 06 Jul 2012 18:30:39 +0000
Subject: [Tracker-discuss] [issue470] "Links" entry in tracker sidebar leads
	to empty page
In-Reply-To: <1340744034.84.0.70532644913.issue470@psf.upfronthosting.co.za>
Message-ID: <1341599439.02.0.497726139677.issue470@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Fixed in r88980.

----------
assignedto:  -> ezio.melotti
nosy: +ezio.melotti
status: unread -> resolved

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

From metatracker at psf.upfronthosting.co.za  Sat Jul  7 08:18:04 2012
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Sat, 07 Jul 2012 06:18:04 +0000
Subject: [Tracker-discuss] [issue472] b.p.o logo link back to python.org
Message-ID: <1341641884.43.0.0541944736351.issue472@psf.upfronthosting.co.za>


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

Why does logo on bug tracker doesn't link back to main site?

----------
messages: 2553
nosy: techtonik
priority: bug
status: unread
title: b.p.o logo link back to python.org

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

From metatracker at psf.upfronthosting.co.za  Sat Jul  7 14:49:28 2012
From: metatracker at psf.upfronthosting.co.za (Danny Staple)
Date: Sat, 07 Jul 2012 12:49:28 +0000
Subject: [Tracker-discuss] [issue448] Login not working (mostly)
In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za>
Message-ID: <1341665368.23.0.153913116752.issue448@psf.upfronthosting.co.za>


Danny Staple <danny at orionrobots.co.uk> added the comment:

This also occurred for me having done a search, then login to add a bug. Considering this is a standard workflow when seeing a bug to report (search first, so as not to add a duplicate), then the login action at least should support this some way - perhaps the url should be "action=login&original_action="urlescaped end of original" such that a successful login can redirect to the logged in version of the previous action.

----------
nosy: +dannystaple

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

From metatracker at psf.upfronthosting.co.za  Sat Jul  7 14:51:28 2012
From: metatracker at psf.upfronthosting.co.za (Danny Staple)
Date: Sat, 07 Jul 2012 12:51:28 +0000
Subject: [Tracker-discuss] [issue448] Login not working (mostly)
In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za>
Message-ID: <1341665488.44.0.290414136749.issue448@psf.upfronthosting.co.za>


Danny Staple <danny at orionrobots.co.uk> added the comment:

I am bumping this to urgent. I think that the red bar will discourage some people from submitting bugs on roundup sites.

----------
priority: bug -> urgent

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

From metatracker at psf.upfronthosting.co.za  Sat Jul  7 16:59:46 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Sat, 07 Jul 2012 14:59:46 +0000
Subject: [Tracker-discuss] [issue448] Login not working (mostly)
In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za>
Message-ID: <1341673186.52.0.363906622495.issue448@psf.upfronthosting.co.za>


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

dannystaple: are you sure the issue you encountered is the very same issue as the one discussed here?

What is the exact sequence of URLs that you navigated to, and what is the error message that you got? roundup most certainly has a came_from parameter in the login process, so what you ask for should already work.

Please understand that assigning priorities to issues is largely irrelevant. The issue may be deal with today, a year from now, or five years from now - mostly independent of what it's priority is (but issues that we don't consider urgent, as this one, will likely be lowered again in their priority).

----------
priority: urgent -> bug

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

From metatracker at psf.upfronthosting.co.za  Sat Jul  7 17:52:13 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 07 Jul 2012 15:52:13 +0000
Subject: [Tracker-discuss] [issue471] Link from Rietveld issue to Roundup
	issue
In-Reply-To: <1341260402.17.0.425409478246.issue471@psf.upfronthosting.co.za>
Message-ID: <1341676333.37.0.775467710515.issue471@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

I pushed a fix in d712347ee856.

----------
assignedto:  -> ezio.melotti
status: unread -> resolved

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

From metatracker at psf.upfronthosting.co.za  Sat Jul  7 18:10:21 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sat, 07 Jul 2012 16:10:21 +0000
Subject: [Tracker-discuss] [issue472] b.p.o logo link back to python.org
In-Reply-To: <1341641884.43.0.0541944736351.issue472@psf.upfronthosting.co.za>
Message-ID: <1341677421.36.0.814079199656.issue472@psf.upfronthosting.co.za>


Ezio Melotti <ezio.melotti at gmail.com> added the comment:

Because clicking on it is the easiest way to get to the b.p.o home, and I would prefer to leave it that way.

I agree though that the Python logo might lead user to think the logo links to w.p.o, and afaict there's no direct link to w.p.o.
Two things could be done:
 1) add a link to w.p.o somewhere (e.g. at the top of the sidebar);
 2) use a b.p.o-specific logo  (writing "Issues" somewhere in the current logo might be enough);

----------
nosy: +ezio.melotti
status: unread -> chatting

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

From metatracker at psf.upfronthosting.co.za  Sun Jul  8 01:27:37 2012
From: metatracker at psf.upfronthosting.co.za (Danny Staple)
Date: Sat, 07 Jul 2012 23:27:37 +0000
Subject: [Tracker-discuss] [issue448] Login not working (mostly)
In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za>
Message-ID: <1341703657.62.0.0781153584339.issue448@psf.upfronthosting.co.za>


Danny Staple <danny at orionrobots.co.uk> added the comment:

Hmm - point taken about the priority, I know how these things can go down.

The initial comment (msg2432) has "If I do a search and do same [log in] from results page, get same error [red background - broken form error]". I've annotated with the square brackets, but this, including the same message, is consistent with what happened to me too.

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

From metatracker at psf.upfronthosting.co.za  Sun Jul  8 01:47:47 2012
From: metatracker at psf.upfronthosting.co.za (anatoly techtonik)
Date: Sat, 07 Jul 2012 23:47:47 +0000
Subject: [Tracker-discuss] [issue472] b.p.o logo link back to python.org
In-Reply-To: <1341641884.43.0.0541944736351.issue472@psf.upfronthosting.co.za>
Message-ID: <1341704867.86.0.816518558581.issue472@psf.upfronthosting.co.za>


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

I'm +1 on both.

1) link can be a back arrow to the left of the logo. similar to google docs - it appears on hover next to title for opened document leading to doc list. but here it could be persistent and in appropriate style (grid aligned rectangle with blue)

still the easiest way for 1) seems to add a "<<< www.python.org" above the menu.

2) i don't know how to make the font or style of the word "Issues", I'd just distort the 'o' like vertical sync is lost for this letter - similar for typewriter error. the easiest way probably is to take pypng and randomize starting position of each vertical line

http://www.python.org/community/logos/



BTW, the hack with removing whitespace introduced in r88812 is not really nice.
56 #menu ul.level-one li a
57 {
58	  margin-left: 0;
59 }
http://svn.python.org/view/tracker/instances/python-dev/html/style.css?annotate=88932

As you may see the logo becomes misaligned with the menu. The proper way to make align them and put whitespace on the left to a good use is to change margin-left:3% property to 1% for #logo and left:3% to 1% for #left-hand-navigation. Margin hack like the one above takes time to debug, so my reserve for today is over.

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

From metatracker at psf.upfronthosting.co.za  Wed Jul 11 10:00:10 2012
From: metatracker at psf.upfronthosting.co.za (=?utf-8?q?Martin_v=2E_L=C3=B6wis?=)
Date: Wed, 11 Jul 2012 08:00:10 +0000
Subject: [Tracker-discuss] [issue448] Cannot log into search results page
In-Reply-To: <1333644181.93.0.427714955722.issue448@psf.upfronthosting.co.za>
Message-ID: <1341993610.28.0.629116256269.issue448@psf.upfronthosting.co.za>


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

Ok, to focus the bug: the issue appears that people cannot log in when a search results page is displayed. Login seems to work fine otherwise.

----------
title: Login not working (mostly) -> Cannot log into search results page

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

From chris.jerdonek at gmail.com  Sun Jul 15 23:38:20 2012
From: chris.jerdonek at gmail.com (Chris Jerdonek)
Date: Sun, 15 Jul 2012 14:38:20 -0700
Subject: [Tracker-discuss] resolution status for issues fixed by other issues
Message-ID: <CAOTb1wef6wJaPDNC87hF3EDunVJy0kVzy6YgsD9AXnnV1z0_nA@mail.gmail.com>

What is the right resolution status when closing an issue that was
originally valid but later fixed indirectly by another issue?  Fixed, out
of date, or duplicate (and putting the other issue in the Superseder)?

--Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/tracker-discuss/attachments/20120715/8460917e/attachment.html>

From rdmurray at bitdance.com  Mon Jul 16 01:25:11 2012
From: rdmurray at bitdance.com (R. David Murray)
Date: Sun, 15 Jul 2012 19:25:11 -0400
Subject: [Tracker-discuss] resolution status for issues fixed by other
	issues
In-Reply-To: <CAOTb1wef6wJaPDNC87hF3EDunVJy0kVzy6YgsD9AXnnV1z0_nA@mail.gmail.com>
References: <CAOTb1wef6wJaPDNC87hF3EDunVJy0kVzy6YgsD9AXnnV1z0_nA@mail.gmail.com>
Message-ID: <20120715232512.A5B9C250182@webabinitio.net>

On Sun, 15 Jul 2012 14:38:20 -0700, Chris Jerdonek <chris.jerdonek at gmail.com> wrote:
> What is the right resolution status when closing an issue that was
> originally valid but later fixed indirectly by another issue?  Fixed, out
> of date, or duplicate (and putting the other issue in the Superseder)?

I'd go with duplicate, I think.  That way there is a link to the
issue that actually fixed the problem.

But don't worry about it much; those resolutions purely informational
and not really all that reliable in the general case.

--David

From metatracker at psf.upfronthosting.co.za  Sun Jul 29 06:24:16 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 29 Jul 2012 04:24:16 +0000
Subject: [Tracker-discuss] [issue301] SVN cleanup - remove vendor/
In-Reply-To: <1253190010.89.0.509247878942.issue301@psf.upfronthosting.co.za>
Message-ID: <1343535856.82.0.266110910873.issue301@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

The tracker has been moved to http://hg.python.org/tracker/ so this issue can be closed.

----------
assignedto:  -> ezio.melotti
nosy: +ezio.melotti
status: chatting -> resolved

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

From metatracker at psf.upfronthosting.co.za  Sun Jul 29 06:31:15 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 29 Jul 2012 04:31:15 +0000
Subject: [Tracker-discuss] [issue437] Ignore a dot in urls if it's the last
	character
In-Reply-To: <1330951468.67.0.643931051848.issue437@psf.upfronthosting.co.za>
Message-ID: <1343536275.68.0.406373204652.issue437@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

The upstream issue (http://issues.roundup-tracker.org/issue2550759) has been fixed and I updated our tracker instance to include the fix.

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

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

From metatracker at psf.upfronthosting.co.za  Sun Jul 29 06:42:26 2012
From: metatracker at psf.upfronthosting.co.za (Ezio Melotti)
Date: Sun, 29 Jul 2012 04:42:26 +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: <1343536946.25.0.0664910685251.issue356@psf.upfronthosting.co.za>


Ezio Melotti added the comment:

This is now done with a separate branch on http://hg.python.org/tracker/roundup/.

----------
assignedto:  -> ezio.melotti
nosy: +ezio.melotti
status: unread -> resolved

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