PhilNeal Posted May 21, 2007 Posted May 21, 2007 The registration period not showing in the timeline is an unfortunate error which I very much regret because I can imagine the problems that it caused immediately after the update. It wasn't the testers fault, it was human error that occurred in the final build stage. We are changing our source control system at the next release because it should pick up this type of error. We have debated issuing a new executable but the June release is due on 15th June and it does contain some important changes to meet the autumn census. A re-release would cause a delay and we believe that there are adequate workarounds available. I'm not sure who said that LAs wanted the information screen but it was our decision to do it. I think this is a no win because we want people to know what is in a release as there are usually significant improvements that are designed to make things easier for people. However I can certainly understand that if an update has taken a few minutes you don't have the time to read through the notes before taking the register.
TechMonkey Posted May 22, 2007 Posted May 22, 2007 The registration period not showing in the timeline is an unfortunate error which I very much regret because I can imagine the problems that it caused immediately after the update. It wasn't the testers fault, it was human error that occurred in the final build stage. We are changing our source control system at the next release because it should pick up this type of error. We have debated issuing a new executable but the June release is due on 15th June and it does contain some important changes to meet the autumn census. A re-release would cause a delay and we believe that there are adequate workarounds available. Well Edugeek wins out again. Thanks for the explaination. It is good to know the whys and wherefores sometimes I'm not sure who said that LAs wanted the information screen but it was our decision to do it. I think this is a no win because we want people to know what is in a release as there are usually significant improvements that are designed to make things easier for people. However I can certainly understand that if an update has taken a few minutes you don't have the time to read through the notes before taking the register. We phoned up our county support team and they told us it was a voted change request. The problem we have with it, besides the time and teacher inconvienience, is that you all ready get the PDF whats new docment (not the fancy branded one) and that means we can look through and work out what the staff need to know or would find useful and then release that with training. It just means that the teachers get continuity from day to day (we had got it at one point that teachers wouldn't have know about an update unless omse major cosmetic change had happened) and we can realase training as they want and need it. Not wanting to sound condescening but some teachers do get very confuddled with a slight change so if you can break it gently to them with a warm cup of tea and a biscuit (ok that is condescending) then it goes smoother.
the.damon Posted May 22, 2007 Posted May 22, 2007 The problem for SIMS is that what works for one school doesnt for another. I think alot of my primary schools would appreciate some form of update information upon first login. However perhaps the delivery of this information does need fine tuning. Perhaps just a large message on the homepage offering a link to the PDF the first time they login after upgrade would be sufficient. RE: Voted change requests - Anyone with a supportnet account can vote for change requests. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now