Communication of changes made to MLS - how does this work?
- ericb
- Member
- Posts: 109
- Joined: Fri Feb 23, 2007 8:51 am
- Location: Vancouver USA
Communication of MLS revisions - how does this work?
During my short tenure as ward clerk (6 months), I've noticed a number of changes to the MLS software that have occured either via a Send/Receive or performed by the Stake Computer Specialist. This morning, I noticed our ward computer is now running MLS version 2.6. I'm feeling I have too little knowledge of what these changes encompass.
My question is this -- when MLS updates are deployed, how are the changes supposed to be communicated to ward clerks? Is my stake not passing along the information? Is there revision history information I can refer to (and if so, where)? Even though I'm not directly involved in the update processes, I feel I should be informed of how the changes affected MLS since everyone else in the ward (particularly the bishop) depends on me to know the ins & outs of the application.
My question is this -- when MLS updates are deployed, how are the changes supposed to be communicated to ward clerks? Is my stake not passing along the information? Is there revision history information I can refer to (and if so, where)? Even though I'm not directly involved in the update processes, I feel I should be informed of how the changes affected MLS since everyone else in the ward (particularly the bishop) depends on me to know the ins & outs of the application.
- thedqs
- Community Moderators
- Posts: 1042
- Joined: Wed Jan 24, 2007 8:53 am
- Location: Redmond, WA
- Contact:
-
- Senior Member
- Posts: 773
- Joined: Tue Jan 23, 2007 2:03 pm
While at this time there is no need for me to be on MLS as my calling does not require it, I have still let some of those that do in my ward know of things discussed here, and they have sounded surprised that some of the things happened.
Has anyone seen any 'release notes' or 'readme' file sent with any MLS update? Back in 2005 when I was the HP group secretary we were just flying by the seat of our pants on a few things namely in handling HT companionship changes/reporting, found a tarantula sized bug in that part of it, and I knew who to contact due to some casual comments made about the future initial deployment of MLS I had heard about only two months earlier in another setting. That was when I think v2.4 was released, maybe it was an even earlier version.
Still it's good software, just having growing pains is all, as the Church finds how useful it is and will yet be.
Has anyone seen any 'release notes' or 'readme' file sent with any MLS update? Back in 2005 when I was the HP group secretary we were just flying by the seat of our pants on a few things namely in handling HT companionship changes/reporting, found a tarantula sized bug in that part of it, and I knew who to contact due to some casual comments made about the future initial deployment of MLS I had heard about only two months earlier in another setting. That was when I think v2.4 was released, maybe it was an even earlier version.
Still it's good software, just having growing pains is all, as the Church finds how useful it is and will yet be.
-
- New Member
- Posts: 7
- Joined: Thu Mar 29, 2007 8:20 pm
There is a release notes.htm that goes with the update. It was included in the reimaging that took place on our wards computer in order to upgrade to 2.6. There have been some additional changes (like adding a checkbox for tracking people that have been set apart) but nothing "major" that I can remember
- ericb
- Member
- Posts: 109
- Joined: Fri Feb 23, 2007 8:51 am
- Location: Vancouver USA
JamesAnderson wrote:...I have let some of those in my ward know of things discussed here, and they have sounded surprised that some of the things [have] happened.
I think this is essentially my point -- those of us that work with MLS on a regular basis should not be surprised with changes, but need to be kept well informed. Someone might indicate nothing much has changed, and then I'll happen to read somewhere else that "oh yeah, that was introduced" or "oh yeah, that changed a little". We really need to have an official, concise, and ongoing source for changes. Here are some suggestions I have for improving the process of communication (if some of these are in place, please point me in the right direction):
.
- For every change to MLS that may impact how the software is used, provide clerks a message (using the standard message feature of MLS) with information regarding the change -- include the purpose for the change, how it is to be used, etc.
- As appropriate, provide change information prior to an update being deployed. This would apply more to 'in your face' changes that affect normal use. For example, I'm still seeing posts on various sites regarding the temple activation report warning message -- I ran across this several months ago (and posted a message in this forum), which really should have been addressed by now.
- As appropriate (say every 6 months or so), provide a roll-up of information regarding changes to MLS for the previous 6-12 months. That would give clerks the opportunity to review the changes in a glance, and (hopefully) consider how the improvements could be effectively implemented.
-
- Community Administrator
- Posts: 34513
- Joined: Sat Jan 20, 2007 2:53 pm
- Location: U.S.
By default, "release notes" are installed on the Desktop.ericb wrote:My question is this -- when MLS updates are deployed, how are the changes supposed to be communicated to ward clerks?
I believe major changes, just as this last MLS 2.6 is communicated via the MLS messaging system. It at least gives you a heads up that change is coming.
- McDanielCA
- Member
- Posts: 486
- Joined: Wed Jul 18, 2007 4:38 pm
- Location: Salt Lake City, Utah
- thedqs
- Community Moderators
- Posts: 1042
- Joined: Wed Jan 24, 2007 8:53 am
- Location: Redmond, WA
- Contact:
- WelchTC
- Senior Member
- Posts: 2085
- Joined: Wed Sep 06, 2006 8:51 am
- Location: Kaysville, UT, USA
- Contact:
- thedqs
- Community Moderators
- Posts: 1042
- Joined: Wed Jan 24, 2007 8:53 am
- Location: Redmond, WA
- Contact: