Changes between Version 30 and Version 31 of Developer/Contributing


Ignore:
Timestamp:
Nov 12, 2018, 7:09:04 PM (7 months ago)
Author:
a-bhatt
Comment:

minor grammatical errors and typos

Legend:

Unmodified
Added
Removed
Modified
  • Developer/Contributing

    v30 v31  
    2929
    3030
    31 We encourage you to test changes with as many host and target combinations as is practical. In addition to using real hardware, you can use [wiki:TBR/UserManual/Simulators  simulators] to increase your test coverage. When choosing targets to test a patch with try to exercise all aspects of the code you are changing in various RTEMS configurations. Also remember that RTEMS supports targets with 16, 32, and 64 bit integers. This means that much of the RTEMS source tree must build without warnings on ALL of those targets. 
     31We encourage you to test changes with as many hosts and target combinations as is practical. In addition to using real hardware, you can use [wiki:TBR/UserManual/Simulators  simulators] to increase your test coverage. When choosing targets to test a patch with try to exercise all aspects of the code you are changing in various RTEMS configurations. Also remember that RTEMS supports targets with 16, 32, and 64-bit integers. This means that much of the RTEMS source tree must build without warnings on ALL of those targets. 
    3232
    3333Sometimes a change is mechanical in nature and just verifying it compiles all impacted configurations is sufficient.
    3434
    35 You will of course have tested that your change does what you expected it to do: fix a bug, improve an optimization, add a new feature. If possible you should automate your test cases and add them to RTEMS's test suite. You should also perform regression tests to ensure that your patch does not break anything else.
     35You will, of course, have tested that your change does what you expected it to do: fix a bug, improve an optimization, add a new feature. If possible you should automate your test cases and add them to RTEMS's test suite. You should also perform regression tests to ensure that your patch does not break anything else.
    3636
    3737With documentation changes, you must make the doc manuals and correct any errors.
     
    6262Don't be afraid to announce your interest on the [wiki:TBR/Website/RTEMSMailingLists rtems-users mailing list] or to ask questions to help you along!
    6363
    64 Here're some ideas for work that'd be really useful to RTEMS users. It's non-exhaustive, and largely cobbled together from what's been suggested over time (in fact, one way you could contribute is to update this list with ideas that (for example) have been raised on the mailing lists).
     64Here're some ideas for work that'd be really useful to RTEMS users. It's non-exhaustive and largely cobbled together from what's been suggested over time (in fact, one way you could contribute is to update this list with ideas that (for example) have been raised on the mailing lists).
    6565
    6666See also the [wiki:Developer/OpenProjects  Open Projects] page.