- http://sourceforge.net- -
- http://sourceforge.net/projects/python- -
- scp mylocalfile.html - sf_username@shell.sourceforge.net:/home/groups/python/htdocs/-If you want to edit or remove files, you can use ssh: - -
- ssh -l sf_username shell.sourceforge.net- -
- cd /home/groups/python/htdocs
- rm garbage.html
- vi changeme.html
- export - CVSROOT=:pserver:anonymous@cvs.python.sourceforge.net:/cvsroot/python-If you are indeed a developer you can check out a read/write version with ssh: - -
- cvs login
- cvs -z3 co python
- export CVS_RSH=ssh- -
- export - CVSROOT=sf_username@cvs.python.sourceforge.net:/cvsroot/python
- cvs -z3 co python
- diff -c-This defaults diff to context diffs (almost a requirement as everything else -is harder to read) and tells update to automatically checkout new -subdirectories. - -
- update -d
- Sorry, you don't have read/write access to the history file - /cvsroot/python/CVSROOT/history- -
- Permission denied
- ssh -l sf_username shell.sourceforge.net-If you have just recently (< 6 hours) been added to the Python project, you -probably have to wait for the SourceForge servers to synch up. This can take -up to 6 hours. - -
- groups
- http://sfdocs.sourceforge.net/sfdocs-For general (and more advanced) information consult the free CVS Book at - -
- http://cvsbook.red-bean.com/cvsbook.html#Introduction- -
- cvs diff | tee ~/name_of_the_patch.diff-Else you can use the diff util which comes with most operating systems (a -Windows version is available as part of the cygwin tools).
- http://www.python.org/patches-A recent copy can be found in the Appendix of this FAQ.
Click on the patch itself. In the screen that comes up, there is a drop-box -for "Assigned To:" and a drop-box for "Status:" where you can select a new -responsible developer or a new status respectively. After selecting the -appropriate victim and status, hit the "Submit Changes" button at the bottom -of the page.
- -For more information about the use of the "Status:" and "Assigned To:"
-fields consult the Patch Manager Guidelines. A recent copy
-can be found in the Appendix of this FAQ.
-
In general, the status field should be close to self-explanatory, and the -"Assigned to:" field should be the person responsible for taking the next step -in the patch process. Both fields are expected to change value over the life -of a patch; the normal workflow is detailed below.
- -When you've got the time and the ability, feel free to move any patch that -catches your eye along, whether or not it's been assigned to you. And if -you're assigned to a patch but aren't going to take reasonably quick action -(for whatever reason), please assign it to someone else ASAP: at those times -you can't actively help, actively get out of the way.
- -If you're an expert in some area and know that a patch in that area is both -needed and non-controversial, just commit your changes directly -- no need -then to get the patch mechanism involved in it.
- -You should add a comment to every patch assigned to you at least once a
-week, if only to say that you realize it's still on your plate. This rule is
-meant to force your attention periodically: patches get harder & harder to
-deal with the longer they sit.
-
- The initial status of all patches.- -
- The patch is under consideration, but has not been reviewed yet.
- The status will normally change to Accepted or Rejected next.
- The person submitting the patch should (if they can) assign it to the person - they most want to review it.
- Else the patch will be assigned via [xxx a list of expertise areas should be - developed] [xxx but since this hasn't happened and volunteers are too few, - random assignment is better than nothing: if you're a Python developer, - expect to get assigned out of the blue!]
- Discussion of major patches is carried out on the Python-Dev mailing list. - For simple patches, the SourceForge comment mechanism should be sufficient. - [xxx an email gateway would be great, ditto Ping's Roundup]
- The powers that be accepted the patch, but it hasn't been applied yet. [xxx - flesh out -- Guido Bottleneck avoidable here?]- -
- The status will normally change to Closed next.
- The person changing the status to Accepted should, at the same time, assign - the patch to whoever they believe is most likely to be able & willing to - apply it (the submitter if possible).
- The patch has been accepted and applied.- -
- The previous status was Accepted, or possibly Open if the submitter was - Guido (or moral equivalent in some particular area of -expertise).
- The patch has been reviewed and rejected.- -
- When the objections are addressed, the status may change to Open again.
- The person changing the status to Rejected should assign the patch back to - the submitter, or if it's clear the patch will never be accepted, assign it - to None.
- Note that SourceForge allows the submitter to overwrite the patch with a new - version.
- Previous status was Open or Accepted or Postponed, but the patch no longer - works.- -
- Please enter a comment when changing the status to "Out of date", to record - the nature of the problem and the previous status.
- Also assign it back to the submitter, as they need to upload a new version - (note that SourceForge will not allow anyone other than the original - submitter to update the patch).
- The previous status was Open or Accepted, but for some reason (e.g., pending - release) the patch should not be reviewed or applied until further - notice.- -
- The status will normally change to Open or Accepted next.
- Please enter a comment when changing the status to Postponed, to record the - reason, the previous status, and the conditions under which the patch should - revert to Open or Accepted. Also assign the patch to whoever is most likely - able and willing to decide when the status should change again.
- Bit bucket.- -
- Use only if it's OK for the patch and its SourceForge history to - disappear.
- As of 09-July-2000, SF does not actually throw away Deleted patches, but - that may change.
Many people contribute patches to Python. We've set up a new system to deal -with these. Here are the main guidelines:
-