...
Section | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Issue Title | Issue Description |
---|---|
Code cleanup for release x.x | Clean up comments, ensure public APIs are fully commented and JSLint new javascript files. |
Check licenses and copyrights | Ensure all javascript files have a license and copyright. Also make sure thirdparty code is compatibly licensed and a license file is included in the same directory as the code. |
Update and expand on unit test coverage | Increase unit test coverage and ensure that all tests are passing. |
Update all version numbers for the release | All references to the version number must be updated to the new version number. This includes: package.json, all *.js files, "fluid.version" in Fluid.js |
Comment any "unsupported" functions/variables/etc | Anything in our code that is "unsupported" (i.e. not meant for public use despite the fact that technically it is public) needs to be indicated as such in the comments in the code. This covers
|
Update the README.txt and ReleaseNotes.txt files | Be sure to update the version number, the zip file names (which include the version number), the "What's New" section with a list of features of the release, folder hierarchy if it has changed at all (e.g. new sample-code folders added), the list of supported browsers if it has changed, and the "Known Issues" section with highlights of the known issues. |
Turn off debug mode | Update fluid.fail() to throw an error, turn off debug mode for the renderer, etc. |
screen source files for DOS line ending | Run source tree through an utility like dos2unix to normalize line endings for Unix. See note below for more information. |
Removing DOS CR/LF
For Ubuntu using fromdos command:
...
The Fluid community should be relied on for testing assistance. The best way to obtain testing help is through the fluid-work mailing list and the #fluid-work irc channel:matrix.org.