A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2001-December/018876.html below:

[Python-Dev] python2.1.2 plans, plus the curse of PEP-006.

[Python-Dev] python2.1.2 plans, plus the curse of PEP-006.Anthony Baxter Anthony Baxter <anthony@interlink.com.au>
Thu, 06 Dec 2001 13:59:11 +1100
>>> Aahz Maruch wrote
> What does "should be maintained" mean?  With CVS, IIUC, there's no
> reason not to keep branches around forever.  If instead what you're

I mean "should continually have backported patches applied".

> talking about is policy for work to be assigned, I won't let that into
> PEP6; the entire point of PEP6 is that it only prescribes procedure for
> someone who is already working, it does not specify any work to be
> accomplished in the abstract.  

Oh, sure - I'm not talking about adding it to PEP006 - it's not appropriate
for it. More talking about the abstract here.
 
> The problem lies in creating the social structure to make that happen.
> People who monitor CVS need to get into the habit of reminding each
> other to mark bugfix candidates.  But that's beyond the scope of PEP6.

*nod* absolutely.



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