> http://manatee.mojam.com/py222wiki/
>
> I did *nothing* other than set it up. I don't know how people want to use
> the Wiki. Feel free to organize it any way you want, or give me some clues
> and I'll take a crack at a top-level structure.
>
> Michael McLay had suggested:
>
> >> Perhaps Wiki pages would be a good mechanism for collaboration on the
> >> classification of patches. Create one page for each classification
> >> type and then use the patch names and title as section titles within
> >> the page.
>
> What are the classification types he referred to?
I suppose he was referring to this (from my initial 2.2.2 post last
Friday):
Basically, someone does the tedious part of triage, which means
going over *every* 2.3 checkin message (with quick access to the
corresponding diffs) and sorting them into:
- already applied
- trivial reject (e.g. new feature or fix for a bug introduced in
2.3)
- trivial accept (pure bugfix that applies cleanly to 2.2)
- messy (e.g. unclear whether it's a bugfix or a feature even
after staring at the source, bugfixes that affect binary
compatibility, bugfixes that can only be applied with much code
wrangling due to other changes in the code at the same place,
etc.)
Feel free to compile a list of "messy" ones and send it to
python-dev. It doesn't have to be all at once -- for big messy
ones a separate python-dev discussion may be appropriate.
--Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4