Stock-management repo update

Hi everyone,

Thanks to work by Chongsun and the ThoughtWorks team, the contents of the “stock-management” sub-module are now folded into the main OpenLMIS repository. The “2.0” branch no longer relies upon the sub-module.

This change will be reflected with the next merge of 2.0 to VIMS. Elias, when do you think this will occur?

We don’t believe there are any pending updates to the stock-management repo, nor should there be. We can keep the repository around until all branches have removed the dependency, and maybe a month or two thereafter, then we can simply remove it. Any objections?

Thanks - Rich

FYI - happy to explain the repercussions of this and how this plays into the re-architecture.

Cheers,

···

Kevin Cussen

Technology Manager

Village****Reach* ** Starting at the Last Mile*

2900 Eastlake Ave. E, Suite 230, Seattle, WA 98102, USA

CELL: 1.206.604.4209

www.villagereach.org

Connect on Facebook, Twitter** ** and our Blog


From: openlmis-dev@googlegroups.com openlmis-dev@googlegroups.com on behalf of Rich Magnuson rich.magnuson@villagereach.org

Sent: Monday, December 21, 2015 11:45

To: OpenLMIS Dev; Elias Muluneh

Cc: Chrispinus Melkiory; Paschal Bwile; Hussein Hassan

Subject: [openlmis-dev] Stock-management repo update

Hi everyone,

Thanks to work by Chongsun and the ThoughtWorks team, the contents of the “stock-management” sub-module are now folded into the main OpenLMIS repository. The “2.0” branch no longer relies upon the sub-module.

This change will be reflected with the next merge of 2.0 to VIMS. Elias, when do you think this will occur?

We don’t believe there are any pending updates to the stock-management repo, nor should there be. We can keep the repository around until all branches have removed the dependency, and maybe a month or two thereafter, then we can simply remove it. Any objections?

Thanks - Rich

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/BN1PR02MB02108E443F948DFBD99211493E40%40BN1PR02MB021.namprd02.prod.outlook.com
.

For more options, visit
https://groups.google.com/d/optout
.

Hi Rich,

If there are no objections or merge conflicts, I think this could be merged next week.

Thanks - Elias,

···

On Mon, Dec 21, 2015 at 2:45 PM, Rich Magnuson rich.magnuson@villagereach.org wrote:

Hi everyone,

Thanks to work by Chongsun and the ThoughtWorks team, the contents of the “stock-management” sub-module are now folded into the main OpenLMIS repository. The “2.0” branch no longer relies upon the sub-module.

This change will be reflected with the next merge of 2.0 to VIMS. Elias, when do you think this will occur?

We don’t believe there are any pending updates to the stock-management repo, nor should there be. We can keep the repository around until all branches have removed the dependency, and maybe a month or two thereafter, then we can simply remove it. Any objections?

Thanks - Rich

Hi Rich

Did you manage to look at the way dates are returned by api (decremented)?

···

On Mon, Dec 21, 2015 at 2:45 PM, Rich Magnuson rich.magnuson@villagereach.org wrote:

Hi everyone,

Thanks to work by Chongsun and the ThoughtWorks team, the contents of the “stock-management” sub-module are now folded into the main OpenLMIS repository. The “2.0” branch no longer relies upon the sub-module.

This change will be reflected with the next merge of 2.0 to VIMS. Elias, when do you think this will occur?

We don’t believe there are any pending updates to the stock-management repo, nor should there be. We can keep the repository around until all branches have removed the dependency, and maybe a month or two thereafter, then we can simply remove it. Any objections?

Thanks - Rich