...
| Section |
|---|
| Column |
|---|
A major constituent of the release is the "source code". This is a collection of JavaScript, Java, HTML, CSS, build script, example, and unit test files that are tracked using the Infusion source code repository. The main tasks to create a release of the source code are to tag the current revisions of the source files, and to bundle them into an archive (e.g., a zip file). |
| Column |
|---|
| | Panel |
|---|
| borderColor | #566b30 |
|---|
| bgColor | #fff |
|---|
| titleBGColor | #D3E3C4 |
|---|
| borderStyle | solid |
|---|
| title | Tag, Package, Post and Announce |
|---|
| |
|
|
Tag the Source Code
| Include Page |
|---|
| Tagging the Source Code |
|---|
| Tagging the Source Code |
|---|
|
Bundle the Source Code
| Include Page |
|---|
| Building a Bundle |
|---|
| Building a Bundle |
|---|
|
Test the Release Bundles
Testing tasks for the release bundles can be found on the Release Package QA Test Plan page.
Additionally, once the bundles have been deployed to the builder, it also needs to be tested and primed.
- Testing
- In the various browser/OS config download a package.
- Verify contents of the download
- Try using the concatenated file in a demo or something to ensure it is constructed properly
- Priming
- Create builds of the components individually
- Create common builds
- Create some random builds
back to top