Post-Product Committee Follow-up 2/9
Kevin Cussen
Hi all,
Thanks for the great call this morning. You can find the minutes and the recording here.
Additionally, we had a few remaining items I'd like to address / provide reminders:
Ashraf - you agreed to try and find the Tanzania and Zambia eLMIS use case white papers and share with the group.
I've discussed with Rich at which point the Tech Committee would like to be involved in the global requirements discussion per Renee's comments. He will bring it up on the February 23rd call and provide us feedback.
Brian - you had some specific questions regarding the release numbering algorithm that I wasn't able to answer. Rich is on this group, so please reply with specifics.
Someone from VillageReach will host the next Product Committee meeting (although it may not be me). Please be active in crafting the agenda in my absence as my replacement won't have as much context on past calls. Also, consider diving into a few of the
Open Questions listed
here as time allows.
I'll follow-up later this week with the high level requirements for SIIL (Benin).
Lastly, you can find the information on our next call
here. Please feel welcome to update the agenda!
Cheers,
Kevin Cussen | kevin....@villagereach.org
Manager, Information Systems
VillageReach Starting at the Last Mile
2900 Eastlake Ave. E, Suite 230, Seattle, WA 98102, USA
CELL: 1.206.604.4209 FAX: 1.206.860.6972
SKYPE: kevin.cussen.vr
Connect on Facebook, Twitter and our Blog
Taliesin, Brian
Thank you for the recap, Kevin.
My questions/comments around the release numbering were twofold:
1. Any changes to the code should result in an increment in the patch numbering. Even if a bug is found right after posting, and it will take less time to fix the error than to create the documentation and follow the process to repost with a fix.
2. I agree with the rubrics associated with the numbering scheme. Who decides what is a dot vs. a full release (e.g., product owner, technical committee, someone else)?
Warm regards,
Brian Taliesin
Systems Analyst, Digital Health Solutions
2201 Westlake Ave. Suite 200, Seattle, WA 98121 USA
Direct: +1.206.302.6039
Mobile: +1.206.387.8932
Skype: btaliesin
Email: btal...@path.org
Learn more about our work in health information systems and supply chain solutions.
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Product Committee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
openlmis_product_co...@googlegroups.com.
To post to this group, send email to
openlmis_prod...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/openlmis_product_committee/CY1PR02MB11193A6127A34218346510F1E3D60%40CY1PR02MB1119.namprd02.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.