Develop release-4.1.4 about jmri HOT 6 CLOSED

I've redone the way we dynamically create the version strings. The goal is to have release branches not have a special commit at the top to mark their status. That was making it confusing for e.g. somebody who wanted to develop starting from the branch, or who wanted to pull something onto a release branch to update it. See #244

from jmri.

The release-4.1.4 branch has been created.

From now on, please document your changes in the jmri4.1.5.shtml release note file.

Maintainers, please set the 4.1.5 milestone on pulls from now on.

from jmri.

Waiting for a fix to a problem with icons (from jmri-developers list); #251 may be the fix.

from jmri.

Pete Cressman working on a better fix than #251.

See also #232 and #236.

from jmri.

I'm going to advance the 4.1.4 branch to include current master (all non-WIP PRs have been merged)

Steps:

• reopen the 4.1.4 milestone, add it to all PRs since the earlier build (some were 4.1.5 already)
• merge master onto the branch
• builds and test files.
• remind everybody to move their release note updates from the 4.1.5 file back to the 4.1.4 one

from jmri.

Released 11/25/2015

from jmri.