| 1 | Steps for Creating a new Release for Scheduling GUI.
|
|---|
| 2 | 1. Increment version number on the GUI (both assembly and file).
|
|---|
| 3 | 2. Compile GUI and dll in release mode. Update svn.
|
|---|
| 4 | 3. Increment version number in the BSDX APPLICATION file.
|
|---|
| 5 | 4. Copy kids build into new kids build, incrementing the version number.
|
|---|
| 6 | 5. Edit build. Change Date Distributed.
|
|---|
| 7 | 6. Change version number on routines using the Update Version Number option.
|
|---|
| 8 | 7. Copy modified routines just created from patches back to svn directory. Update svn.
|
|---|
| 9 | 8. Write out the build, and update svn with the new build.
|
|---|
| 10 | 9. Update Readme file with new version. Add any tidbits if necessary.
|
|---|
| 11 | 0. Update the Change Log.
|
|---|
| 12 |
|
|---|
| 13 | Steps for Creating a new Release for BMX
|
|---|
| 14 | 1. Increment version number on the GUI (assembly and file).
|
|---|
| 15 | 2. Compile GUI and dll in release mode. Update svn.
|
|---|
| 16 | 3. Increment version number in the BMX APPLICATION file.
|
|---|
| 17 | 4. Copy kids build into new kids build, incrementing the version number.
|
|---|
| 18 | 5. Edit build. Change Date Distributed.
|
|---|
| 19 | 6. Change version number on routines using the Update Version Number option.
|
|---|
| 20 | 7. Copy modified routines just created from patches back to svn directory. Update svn.
|
|---|
| 21 | 8. Write out the build, and update svn with the new build.
|
|---|
| 22 | 9. Update Readme file with new version. Add any tidbits if necessary.
|
|---|
| 23 | 0. Update the Change Log.
|
|---|
| 24 |
|
|---|
