search

Esri / joint-military-symbology-xml

Joint Military Symbology Markup Language is a data encapsulation of MIL-STD-2525D and APP-6(D).
Apache License 2.0
143 stars 56 forks source link

Branch/Milestone maintenance #294

Closed joebayles closed 8 years ago

joebayles commented 8 years ago

Per the guidance to the team, we should have a dev branch and a v.next branch.

I'd also suggest we clean up some of the other branches that currently exist but may be old.

Version - Next Milestone is overdue by 6 months.

abouffard commented 8 years ago

Thanks. I'll take care of it. Since most of our current work is for DCGS-A, which is designed for use with released software, we'll start using the new dev branch for that project.

abouffard commented 8 years ago

Branches dev and v.next have been created from the current master.

Changes for DCGS-A (Pro 1.2 and ArcGIS 10.3.1) should go in dev. Changes for Pro 1.3 and ArcGIS 10.4 should go in v.next

csmoore commented 8 years ago

Just a quick note - v.next is optional and was primarily intended to be for actual future (ArcGIS) product dependencies (which I wouldn't anticipate this repo would have - but you may want something similar for Change 1).

Also, if/when you clean up the branches - please leave: https://github.com/Esri/joint-military-symbology-xml/tree/Esri-implementation-mil2525c https://github.com/Esri/joint-military-symbology-xml/tree/Esri-implementation-no-subtypes Until the source data is capable of producing this output.

abouffard commented 8 years ago

Thanks @csmoore. I think v.next will be used for Change 1 - for "future projects" like that.

joebayles commented 8 years ago

We can call v.next or Change 1 mil-std-2525-d-c1 or maybe just 2525-d-c1. @csmoore I didn't mean those, but the patch-1's and sssmc branch look old/unnecessary.

joebayles commented 8 years ago

@abouffard can you update the milestones, please?

joebayles commented 8 years ago

Verified.