Difference between revisions of "Preparing Code"

Latest revision as of 00:59, 27 January 2024

If you have a piece of source code (be it a fix, new feature, or optimization of existing code) prepare your changes in a way that makes it easy for the Lindens to incorporate them into the source code.

Good Change Practice

It's easy for the people who review and apply changes to be the bottleneck in the system. If you can make it easier for Lindens to understand, test, and integrate your change, it is much better for everyone concerned.

Before You Start

Understand and use the Project Snowstorm Processes; making sure that your change is part of the plan is the most important thing you can do to get it accepted.

You must complete and sign the Linden_Lab_Official:Contribution_Agreement.

Coding Standard

Please read and follow our coding standard: Second Life coding standard.

Comments

Do not add issue numbers and your name to the code itself. While comments explaining code in a general working context are helpful and strongly encouraged, bracketing a change with comments like // PATCH START and // PATCH END does not add any information, and is likely to get your change returned for revision.

Do not comment out or use the preprocessor to disable code that you are replacing: just delete it. The source control system can find it again if we need it, and leaving dead code around makes things harder to read and much harder to search.

In short, make your change what is expected to appear in the final source.

Give Yourself Credit!

While names shouldn't appear in source, they do belong in doc/contributions.txt. Please don't be shy about adding the issue label and adding your name. If you already have one or more entries in contributions.txt, add new ones at the appropriate positions (sorting yours, if desired).

One Change For One Issue

Each submission should do exactly one thing. If you have three different bugs to fix, please submit three different change sets (unless they are very closely related and being treated as one item in the sprint). If you are unsure whether or not it is ok to combine changes into one submission, ask the Lindens.

Less Is More

Smaller change sets are easier to review and therefore more likely to be integrated quickly. This does not mean that you should omit comments or unit tests, however - adding to those is strongly encouraged.

When The Code Is Ready

See How To Submit A Viewer Change

@@ Line 1: / Line 1: @@
 {{OSWikiContribBox}}
+__NOTOC__
-If you have a piece of source code (be it a fix, new feature, or optimization of existing code) submit the patches in a way that makes it easy for the Lindens to incorporate them into the source code.
+If you have a piece of source code (be it a fix, new feature, or optimization of existing code) prepare your changes in a way that makes it easy for the Lindens to incorporate them into the source code.
-== Good Patch Practise ==
+== Good Change Practice ==
-=== General ===
+It's easy for the people who review and apply changes to be the bottleneck in the system. If you can make it easier for Lindens to understand, test, and integrate your change, it is much better for everyone concerned.
-The best way to think about patches is that the people who are reviewing and applying your patches are the bottleneck in the system.  If you can make it easier for us to understand and apply patches without lots of cleanup, we can spend more time reviewing and incorporating your work.
+==Before You Start==
-===Before You Start===
+* Understand and use the [[Project Snowstorm#Processes|Project Snowstorm Processes]]; making sure that your change is part of the plan is the most important thing you can do to get it accepted.
-Check [https://jira.secondlife.com/secure/Dashboard.jspa| JIRA Bug Tracker] to see if the issue has been submitted and its status.
+* You ''must'' complete and sign the [[Linden_Lab_Official:Contribution_Agreement]].
-If you're going to write a patch, don't forget to sign and send in the [http://secondlife.com/developers/opensource/submitting contribution agreement].  The sooner you do that, the sooner we can accept your patch.
+== Coding Standard ==
-=== Coding Standard ===
+Please read and follow our coding standard: [[Coding_standard|Second Life coding standard]].
-Please read and follow the coding standard: [[Coding_standard|Second Life coding standard]]
+== Comments ==
-=== Comments ===
+Do not add issue numbers and your name to the code itself.  While comments explaining code in a general working context are helpful and strongly encouraged, bracketing a change with comments like <code>// PATCH START</code> and <code>// PATCH END</code> does not add any information, and is likely to get your change returned for revision.
-Please do not add issue numbers or your name to patches.  We have to remove these by hand.  Also, please be careful in how you add comments.  Bracketing a patch with comments like "// PATCH START" and "// PATCH END" does not add any information, and adds to the manual cleanup we have to do.
+Do not comment out or use the preprocessor to disable code that you are replacing: just delete it.  The source control system can find it again if we need it, and leaving dead code around makes things harder to read and much harder to search.
-If you want to make sure you get credited, then
+In short, make your change what is expected to appear in the final source.
-add yourself to doc/contributions.txt as part of the patch.  That makes
-it easier for people to see the exact nature of the changes you've added.
-In short, just add to the patch what is expected to appear in the final source.
+== Give Yourself Credit! ==
-=== One Patch for one Issue ===
+While names shouldn't appear in source, they do belong in <code>doc/contributions.txt</code>. Please don't be shy about adding the issue label and adding your name.  If you already have one or more entries in <code>contributions.txt</code>, add new ones at the appropriate positions (sorting yours, if desired).
-Each patch should do exactly one thing.  If you have three different bugs to fix, please submit three different patches.  When you fold unrelated hunks into a single patch, we have to try to figure out which part of the patch applies to which bug, and split it out by hand, sometimes into several patches.  Combo patches are particularly time consuming, and the manual splitting up makes it very easy to lose pieces of patches altogether.
+== One Change For One Issue ==
-=== Less is more ===
+Each submission should do exactly one thing. If you have three different bugs to fix, please submit three different change sets (unless they are very closely related and being treated as one item in the sprint).  If you are unsure whether or not it is ok to combine changes into one submission, ask the Lindens.
-Smaller patches are easier to review and therefore more likely to be integrated quickly. The longer it takes for a patch to be incorporated, the higher the likelihood that the underlying code will change enough for the patch to fail. Please do not include formatting or other clean-up changes as that makes it harder to review and more likely to fail.
+== Less Is More ==
-== Creating a Patch ==
+Smaller change sets are easier to review and therefore more likely to be integrated quickly.  This does not mean that you should omit comments or unit tests, however - adding to those is strongly encouraged.
-Patches should be submitted in unified diff format.  This format is similar to simple diffs, but with more detailed information, and it can be automatically integrated into the source.  You can generate a unified diff by calling ''diff -uwB <original file> <new file>'' (under Windows you will find the diff command as part of the CygWin project in C:\CYGWIN\BIN).
+==When The Code Is Ready==
-Please submit a single plain text uncompressed patch file that affects all of the files you need to modify.  This is far easier to review than a collection of tiny one-file patches.
+See [[How To Submit A Viewer Change]]
-Also bad for reviewability are a compressed patch, or a tarball or zip containing one or more patches.
-<br/>
-=== Unified diff of all changed files in a folder tree ===
-The easiest way to generate a clean patch is to keep two copies of the source tree.  Leave one completely unmodified, and make all of your changes in the second.  Then use "diff -urN" to generate the patch.  You can use the --exclude option to omit unwanted files.  For example:
- diff -urNwB --exclude="*.o" my_untouched_tree my_modified_tree
-<br/>
-=== Unified diff of multiple files ===
-If for any reason you can not use a whole tree diff as above, you can still merge patches from different files into one, by appending the output of patch commands to the previous output (via '''>>''' redirection for the 2nd and later commands).
- diff -uwB linden-untouched/indra/newview/viewer.h linden/indra/newview/viewer.h >mychanges.patch.txt
- diff -uwB linden-untouched/indra/newview/viewer.cpp linden/indra/newview/viewer.cpp '''>>'''mychanges.patch.txt
- diff -uwB linden-untouched/indra/newview/llviewerwindow.cpp linden/indra/newview/llviewerwindow.cpp '''>>'''mychanges.patch.txt
-<br/>
-=== Sample output ===
-For reference, here's what a unified diff looks like.
- --- linden-untouched/indra/newview/viewer.cpp    2007-05-14 16:47:26.000000000 +0200
- +++ linden/indra/newview/viewer.cpp 2007-05-22 08:49:50.484375000 +0200
- @@ -6302,7 +6326,7 @@
-     llinfos << "Cleaning Up" << llendflush;
- -   LLKeyframeMotion::flushKeyframeCache();
- +   LLKeyframeMotion::flushKeyframeCache(TRUE);
-     // Must clean up texture references before viewer window is destroyed.
-     LLHUDObject::cleanupHUDObjects();
- @@ -6562,6 +6586,8 @@
-     delete gVFS;
-     gVFS = NULL;
- +   LLCurl::cleanup();
- +
-     // This will eventually be done in LLApp
-     LLCommon::cleanupClass();
- }
-== Submitting the Patch on JIRA ==
-When you are ready for the world to view your patch, submit the patch on the [https://jira.secondlife.com/secure/Dashboard.jspa| JIRA Bug Tracker].  Create a new issue or attach the patch to an existing entry as appropriate. Attach the ''.patch'' file itself as a file attachment and make sure that the check mark for ''Patch attached'' is set (you can do that when creating the issue or by choosing Edit for an existing one).  Take a look at existing patches through the ''Issues with patches attached'' filter on the JIRA main page to get a general idea how it is done.
-With larger or sensitive patches it is a good idea to submit the patch for peer review on the [[Developer_communication_tools|mailing list]].  This way fellow developers can review the patch, uncover possible bugs, comment on undesired interactions or generally share ideas with you.
-Just subscribe to the mailing list, then write an email to the list with a link to the description of what it does in the text.
-Also, offer a description of the patch (the why and what) as a separate file and/or as a description or comment with the issue.
-Good luck!