Hi Josh,
Thanks for the explanation. Let me see if I understand what you've wrote. Each quarterly release of the OpenLMIS reference distribution will consist of many components that will each have their own version. So, for example, you could have:
OpenLMIS 3.1 containing
Reference UI 3.0
Notifications service 3.1
Inventory Management 1.0
Vaccines 0.9
Etc.
If this is correct, will we be publishing this "table of contents" information in our release notes moving forward?
As we progress, will the reference distribution support only one version of each component or a range? How will the community be made aware of support and interdependency?
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
What may not be clear is that the releases we talk about at a product level (Beta, 3.0, 3.1, 3.2, etc) are for theReference Distribution currently residing at openlmis-blue. Each component (Service, Reference UI, Extension Module, etc) that makes up the Reference Distribution may be versioned and released independently. An example of how this could have worked for the Beta release: the Notification Service hasn't seen much activity recently, and in fact nothing changed in this service for a few weeks before the Beta release at the end of October. It appears that this service was ready to be a stable release on it's own (perhaps as Notification v3.0) prior to the official Reference Distribution Beta release. This is something we could have done were we ready, though for Beta we weren't quite there.
The ability for various components to progress and be released independently is a goal of the re-architecture. Those responsible for a component should be able to plan their component's releases (beta, stable, etc) independently and in accordance to the contract that they provide to their clients. Similarly the Product Owner and the OpenLMIS community will pull in component releases when a new Reference Distribution release is in progress.
Moving forward not all new components need to start at 3.0, and for brand new functionality I'd recommend that those components work toward a 1.0 release. Next time a new repository or component is created, SolDevelo and VillageReach should talk about its version in order to make a purposeful decision.
If you have a question about how this will work, please ask.
Best,
Josh
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev...@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/8cbcbb6b-7f8c-477d-82ed-768bfda651d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev...@googlegroups.com.
To post to this group, send email to openlm...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CY1PR02MB1119834D4629B57912D9C640E3A10%40CY1PR02MB1119.namprd02.prod.outlook.com.
You did, thanks.
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
Kevin Cussen | kevin.cussen@villagereach.org
Manager, Information Systems
2900 Eastlake Ave. E, Suite 230, Seattle, WA 98102, USACELL: 1.206.604.4209 FAX: 1.206.860.6972SKYPE: kevin.cussen.vr
From: openlmis-dev@googlegroups.com <openlm...@googlegroups.com> on behalf of Josh Zamor <josh....@villagereach.org>
Sent: Tuesday, November 1, 2016 14:08
To: OpenLMIS Dev
Subject: [openlmis-dev] Versioning post-Beta
Hi all,--
This is a quick note about versioning now that Beta has been released. As we saw in the last showcase, components are now versioned, and I level-set all components shipping in 3.0.0-Beta at the same "3.0.0-beta" version in the hope that it would be easier to talk about the version we are working on.
What may not be clear is that the releases we talk about at a product level (Beta, 3.0, 3.1, 3.2, etc) are for theReference Distribution currently residing at openlmis-blue. Each component (Service, Reference UI, Extension Module, etc) that makes up the Reference Distribution may be versioned and released independently. An example of how this could have worked for the Beta release: the Notification Service hasn't seen much activity recently, and in fact nothing changed in this service for a few weeks before the Beta release at the end of October. It appears that this service was ready to be a stable release on it's own (perhaps as Notification v3.0) prior to the official Reference Distribution Beta release. This is something we could have done were we ready, though for Beta we weren't quite there.
The ability for various components to progress and be released independently is a goal of the re-architecture. Those responsible for a component should be able to plan their component's releases (beta, stable, etc) independently and in accordance to the contract that they provide to their clients. Similarly the Product Owner and the OpenLMIS community will pull in component releases when a new Reference Distribution release is in progress.
Moving forward not all new components need to start at 3.0, and for brand new functionality I'd recommend that those components work toward a 1.0 release. Next time a new repository or component is created, SolDevelo and VillageReach should talk about its version in order to make a purposeful decision.
If you have a question about how this will work, please ask.
Best,
Josh
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.
To post to this group, send email to openlmis-dev@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/8cbcbb6b-7f8c-477d-82ed-768bfda651d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.
To post to this group, send email to openlmis-dev@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CY1PR02MB1119834D4629B57912D9C640E3A10%40CY1PR02MB1119.namprd02.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openlmis-dev/CY1PR02MB11191FCD294BEA191F4B3E74E3A00%40CY1PR02MB1119.namprd02.prod.outlook.com.