Hi,

Are there any documents outlining how critical bugs are handled?
Are fixes backported to older pygtk versions? Surely distributors will
need to do it for their LTS releases so it would make sense to do at
least part of that job in one place? Or do we have to file bugs with all
major distros against all versions that have the affected version?
Apologies if this is obvious and documented somewhere, I couldn't find it.
I see a tag but no branch for 2.17, and it's a year old... how come?
http://git.gnome.org/browse/pygtk/
A few distros ship that version (Fedora for one), so how do they all
maintain it?

Concretely, say I found a trivial DoS bug like this one:
https://bugzilla.gnome.org/show_bug.cgi?id=640738#c2
What is the best way to get some attention from the developers with
commit access? Is this going to be picked up by distros afterwards, or
is it more of a manual process?

Cheers
Antoine
_______________________________________________
pygtk mailing list   [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://faq.pygtk.org/

Reply via email to