collecting Python 3 status information

[Allison Randal]

On 02/20/2011 11:16 PM, Robert Collins wrote:
> I think you need an upstream status field, for instance for
> python-testtools which is single-source python 3.2+ compatible, but
> may not be packaged thusly.

Ah, thanks, yes the field needs a clearer name. I've changed "Notes" to 
"Upstream Python 3 Plans". For the distros, we really only need a short 
status tag ("packaged", "not packaged", "waiting for upstream", "won't 
package", etc), but for the upstreams we'll need any details we can 
gather about whether, when, and how they plan to migrate.

Allison