Updated notes for 1.42 release plus 1.5 fixes

This commit is contained in:
sam 2011-01-27 13:59:05 +00:00
parent d5af78c41d
commit facdab15e3
3 changed files with 28 additions and 12 deletions

View File

@ -110,4 +110,8 @@ v1.4.2 (released December 12th 2010)
- Patient Appointment List now shows the names of the clinics as what you called them in the Scheduling GUI, not what they are called in VISTA. - Patient Appointment List now shows the names of the clinics as what you called them in the Scheduling GUI, not what they are called in VISTA.
- New kids build - New kids build
v1.5 (Alpha released Jan 27 2010)
- Speed issues mitigated.
- Ability to Cancel checked-in appointments (including walk-ins) added.
- Grid now responds to mouse wheel movements
- Clearer error messages for end users.

View File

@ -9,13 +9,13 @@ Kernel 8
XB 3 or above XB 3 or above
SD 5.3 SD 5.3
SD 5.3 patch 11310 (to fix a problem with the code) SD 5.3 patch 11310 (to fix a problem with the code)
BMX 2.2 (now required) BMX 2.21
For a Virgin WorldVistA 6-08 release install the following in this order: For a Virgin WorldVistA 6-08 release install the following in this order:
1. XB 4 (see https://trac.opensourcevista.net/browser/IHS-VA_UTILITIES-XB/tag/rel_20091207) 1. XB 4 (see https://trac.opensourcevista.net/browser/IHS-VA_UTILITIES-XB/tag/rel_20091207)
2. BMX 2.2 (see https://trac.opensourcevista.net/browser/BMXNET_RPMS_dotNET_UTILITIES-BMX/trunk/k) 2. BMX 2.21 (see https://trac.opensourcevista.net/browser/BMXNET_RPMS_dotNET_UTILITIES-BMX/trunk/k)
3. XWB 1.1 patch 113102 (see https://trac.opensourcevista.net/browser/BMXNET_RPMS_dotNET_UTILITIES-BMX/trunk/k) 3. XWB 1.1 patch 113102 (see https://trac.opensourcevista.net/browser/BMXNET_RPMS_dotNET_UTILITIES-BMX/trunk/k)
4. BSDX 1.41 (see https://trac.opensourcevista.net/browser/Scheduling/trunk/kids) 4. BSDX 1.42 (see https://trac.opensourcevista.net/browser/Scheduling/trunk/kids)
5. SD 5.3 patch 11310 (see https://trac.opensourcevista.net/browser/Scheduling/trunk/kids) 5. SD 5.3 patch 11310 (see https://trac.opensourcevista.net/browser/Scheduling/trunk/kids)
Client (download from https://trac.opensourcevista.net/browser/Scheduling/trunk/cs/bsdx0200GUISourceCode/bin/Release): Client (download from https://trac.opensourcevista.net/browser/Scheduling/trunk/cs/bsdx0200GUISourceCode/bin/Release):
@ -125,11 +125,10 @@ Enhancement requests:
- Show today's column in a different color. - Show today's column in a different color.
Speed issues: Speed issues:
- Loading takes a long time <solved> - Loading takes a long time <solved in 1.5>
- Search <enter> Select <enter> <enter> takes a long time when adding appointment - Search <enter> Select <enter> <enter> takes a long time when adding appointment <solved in 1.5>
- Wait cursor when updating <solved> - Wait cursor when updating <solved in 1.5>
- Checkin takes a long time - Checkin takes a long time <solved in 1.5>
- Printing the routing slip takes a slightly longer than necessary time - Printing the routing slip takes a slightly longer than necessary time <not an issue in main version>
- Select patient dialog takes a tiny while to show up. - Select patient dialog takes a tiny while to show up. <solved in 1.5>
- Date-change selection not optimal (calls server with each tiny change) <solved> - Date-change selection not optimal (calls server with each tiny change) <solved in 1.5>

View File

@ -9,3 +9,16 @@ Steps for Creating a new Release for Scheduling GUI.
8. Write out the build, and update svn with the new build. 8. Write out the build, and update svn with the new build.
9. Update Readme file with new version. Add any tidbits if necessary. 9. Update Readme file with new version. Add any tidbits if necessary.
0. Update the Change Log. 0. Update the Change Log.
Steps for Creating a new Release for BMX
1. Increment version number on the GUI (assembly and file).
2. Compile GUI and dll in release mode. Update svn.
3. Increment version number in the BMX APPLICATION file.
4. Copy kids build into new kids build, incrementing the version number.
5. Edit build. Change Date Distributed.
6. Change version number on routines using the Update Version Number option.
7. Copy modified routines just created from patches back to svn directory. Update svn.
8. Write out the build, and update svn with the new build.
9. Update Readme file with new version. Add any tidbits if necessary.
0. Update the Change Log.