CAL-240 updated changelog for 0.2.0 release #243

ricklarsen · 2017-02-01T21:28:08Z

What does this PR do?

updates changelog

Who is reviewing it?

@bdeining @lcrosenbu

Choose 2 committers to review/merge the PR (please choose ONLY two committers from below, delete the rest).

@coyotesqrl
@figliold
@jaymcnallie
@jlcsmith
@kcwire
@lessarderic
@pklinef
@shaundmorris
@stustison

How should this be tested?

review content

Any background context you want to provide?

comment any issues that should be added/highlighted.

What are the relevant tickets?

CAL-240

Checklist:

Documentation Updated
- Change Log Updated
Update / Add Unit Tests
Update / Add Integration Tests

coyotesqrl · 2017-02-01T21:36:22Z

CHANGES.md

-	Release Build Date: pending
+
+## 0.2.0
+	Release Date: 2016-2-8


Missed this before. It's 2017.

Also, format should probably be 2017-02-08.

bdeining · 2017-02-01T22:28:59Z

CHANGES.md

- Bug fixes
-	- [Jira view of all issues resolved](https://codice.atlassian.net/issues/?jql=project%3D%22Codice%20Alliance%22%20and%20issuetype%20%3D%20bug%20AND%20fixVersion%20%3D%200.1.3%20and%20resolution%20%3D%20done) in this version.
+- Important issues resolved
+	- [Jira view of all issues resolved](https://codice.atlassian.net/issues/?jql=project%3D%22Codice%20Alliance%22%20AND%20type%20%3D%20Bug%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.2.0%20ORDER%20BY%20priority) in this version.


Currently, the CAL Kanban board does not have a Fixed status, so this would always be empty

bdeining · 2017-02-01T22:34:06Z

CHANGES.md

- [CAL-94](https://codice.atlassian.net/browse/CAL-94) Update the UdpEndpoint to create child metacards with an FMV User Subject
- [CAL-104](https://codice.atlassian.net/browse/CAL-104) add configuration for metacard security marking defaults
- [CAL-84](https://codice.atlassian.net/browse/CAL-84) klv lat-lon pairs when just one value is error value
+- new features
 	- [JIRA View of All New Features](https://codice.atlassian.net/issues/?jql=project%20%3D%20%22Codice%20Alliance%22%20and%20issuetype%20in%20%28story%2Ctask%29%20AND%20resolution%20%3D%20done%20AND%20fixVersion%20%3D%200.2.0%20ORDER%20BY%20summary%20ASC%2C%20priority)


Was it intentional to keep fixVersion = 0.2.0 in the 0.2.1 section?

nope. fixed.

lcrosenbu · 2017-02-02T22:14:00Z

CHANGES.md

- [CAL-104](https://codice.atlassian.net/browse/CAL-104) add configuration for metacard security marking defaults
- [CAL-84](https://codice.atlassian.net/browse/CAL-84) klv lat-lon pairs when just one value is error value
-	- [JIRA View of All New Features](https://codice.atlassian.net/issues/?jql=project%20%3D%20%22Codice%20Alliance%22%20and%20issuetype%20in%20%28story%2Ctask%29%20AND%20resolution%20%3D%20done%20AND%20fixVersion%20%3D%200.2.0%20ORDER%20BY%20summary%20ASC%2C%20priority)
+- new features


Curious if we have to have this level of bullet that is a duplicate of the section heading. Recommend removing it; or if we need it, recommend camel case New Features.

Global: If this level of bullet is not required, I would remove globally since it duplicates (more of a description than an item for the section) the section header. DDF change log does not have this level. If we need a description, can we just add it as a non-bullet under the heading, then use the bullets as the actual item list?

It's more of a placeholder than a description. It should/will be replaced as soon as there is a feature issue to replace it with.

Having that bullet blank breaks the formatting for the link below it. I'll try to populate something on that list before this PR gets merged.

lcrosenbu · 2017-02-02T22:14:19Z

CHANGES.md


 ### ISSUES RESOLVED

 - Important issues resolved
-	- [Jira view of all issues resolved](https://codice.atlassian.net/issues/?jql=project%3D%22Codice%20Alliance%22%20AND%20type%20%3D%20Bug%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%200.2.0%20ORDER%20BY%20priority) in this version.
+	- [Jira view of all issues resolved](https://codice.atlassian.net/issues/?jql=project%3D%22Codice%20Alliance%22%20AND%20type%20%3D%20Bug%20AND%20resolution%20%3D%20Done%20AND%20fixVersion%20%3D%200.2.1%20ORDER%20BY%20priority) in this version.


Recommend all caps JIRA and then caps first letter in each word for consistency with above section.

lcrosenbu · 2017-02-02T22:14:27Z

CHANGES.md


 ### KNOWN ISSUES

 - Open bugs affecting this version
-	- [Jira view of open Issues](https://codice.atlassian.net/issues/?jql=project%3D%20%22Codice%20Alliance%22%20AND%20issuetype%20%3D%20bug%20%20AND%20status%20%3D%20Open%20AND%20affectedVersion%20%3D%200.2.0%20ORDER%20BY%20priority) affecting this version.
+	- [Jira view of open Issues](https://codice.atlassian.net/issues/?jql=project%3D%20%22Codice%20Alliance%22%20AND%20issuetype%20%3D%20bug%20%20AND%20status%20%3D%20Open%20AND%20affectedVersion%20%3D%200.2.1%20ORDER%20BY%20priority) affecting this version.


Recommend all caps JIRA and then caps first letter in each word for consistency with above section.

lcrosenbu · 2017-02-02T22:16:10Z

CHANGES.md

+
+### NEW FEATURES
+
+- new features


Same as above.

lcrosenbu · 2017-02-02T22:16:18Z

CHANGES.md

- Bug fixes
-	- [Jira view of all issues resolved](https://codice.atlassian.net/issues/?jql=project%3D%22Codice%20Alliance%22%20and%20issuetype%20%3D%20bug%20AND%20fixVersion%20%3D%200.1.3%20and%20resolution%20%3D%20done) in this version.
+- Important issues resolved
+	- [Jira view of all issues resolved](https://codice.atlassian.net/issues/?jql=project%3D%22Codice%20Alliance%22%20AND%20type%20%3D%20Bug%20AND%20resolution%20%3D%20Done%20AND%20fixVersion%20%3D%200.2.0%20ORDER%20BY%20priority) in this version.


Same as above.

lcrosenbu · 2017-02-02T22:16:28Z

CHANGES.md

- Known issues
-	- [Jira view of open Issues](https://codice.atlassian.net/issues?jql=project%20%3D%20%22Codice%20Alliance%22%20AND%20issuetype%20%3D%20bug%20AND%20status%20not%20in%20%28Closed%2C%20Done%29%20AND%20affectedVersion%20%3D%200.1.3%20ORDER%20BY%20priority) affecting this version.
+- Open bugs affecting this version
+	- [Jira view of open Issues](https://codice.atlassian.net/issues/?jql=project%3D%20%22Codice%20Alliance%22%20AND%20issuetype%20%3D%20bug%20%20AND%20status%20%3D%20Open%20AND%20affectedVersion%20%3D%200.2.0%20ORDER%20BY%20priority) affecting this version.


Same as above.

lcrosenbu · 2017-02-02T22:16:33Z

CHANGES.md

@@ -164,7 +166,7 @@ replace with next unreleased version
 ### BUG FIXES

 - None in this version. Initial release.
-	- [Jira view of all issues resolved](https://codice.atlassian.net/issues/?jql=project%3D%22Codice%20Alliance%22%20AND%20type%20%3D%20Bug%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20Alliance-0.2%20ORDER%20BY%20priority) in this version.
+	- [Jira view of all issues resolved](https://codice.atlassian.net/issues/?jql=project%3D%22Codice%20Alliance%22%20AND%20type%20%3D%20Bug%20AND%20resolution%20%3D%20Done%20AND%20fixVersion%20%3D%20Alliance-0.2%20ORDER%20BY%20priority) in this version.


Same as above.

coyotesqrl approved these changes Feb 1, 2017

View reviewed changes

coyotesqrl requested changes Feb 1, 2017

View reviewed changes

bdeining reviewed Feb 1, 2017

View reviewed changes

ricklarsen force-pushed the CAL-240 branch 2 times, most recently from 6121b79 to 6ed89f2 Compare February 1, 2017 23:40

bdeining approved these changes Feb 1, 2017

View reviewed changes

lessarderic approved these changes Feb 2, 2017

View reviewed changes

lcrosenbu approved these changes Feb 2, 2017

View reviewed changes

CAL-240 updated changelog for 0.2.0 release

927ea82

ricklarsen force-pushed the CAL-240 branch from 6ed89f2 to 927ea82 Compare February 3, 2017 16:14

shaundmorris assigned coyotesqrl and lessarderic Feb 4, 2017

coyotesqrl approved these changes Feb 7, 2017

View reviewed changes

shaundmorris approved these changes Feb 8, 2017

View reviewed changes

shaundmorris merged commit 1c8e27d into codice:master Feb 8, 2017

ricklarsen deleted the CAL-240 branch February 8, 2017 17:33

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

CAL-240 updated changelog for 0.2.0 release #243

CAL-240 updated changelog for 0.2.0 release #243

ricklarsen commented Feb 1, 2017

coyotesqrl Feb 1, 2017

ricklarsen Feb 1, 2017

bdeining Feb 1, 2017

ricklarsen Feb 1, 2017

bdeining Feb 1, 2017

ricklarsen Feb 1, 2017

lcrosenbu Feb 2, 2017

ricklarsen Feb 3, 2017

lcrosenbu Feb 2, 2017

ricklarsen Feb 3, 2017

lcrosenbu Feb 2, 2017

ricklarsen Feb 3, 2017

lcrosenbu Feb 2, 2017

ricklarsen Feb 3, 2017

lcrosenbu Feb 2, 2017

ricklarsen Feb 3, 2017

lcrosenbu Feb 2, 2017

ricklarsen Feb 3, 2017

lcrosenbu Feb 2, 2017

ricklarsen Feb 3, 2017

CAL-240 updated changelog for 0.2.0 release #243

CAL-240 updated changelog for 0.2.0 release #243

Conversation

ricklarsen commented Feb 1, 2017

What does this PR do?

Who is reviewing it?

Choose 2 committers to review/merge the PR (please choose ONLY two committers from below, delete the rest).

How should this be tested?

Any background context you want to provide?

What are the relevant tickets?

Checklist:

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment