Allow a Master Feature to span multiple releases Merged

Today I have no way to create one master feature and have it span across multiple releases. I either resort to duplicating the Master Feature and/or moving it after a release is done. I need a way for a Master Feature to represent work being started in one release and finished in another. It seems the solution is to place it in the release in which it is 'finished' but when showing a roadmap against master features, work may be occurring in an earlier release and it is not known on the roadmap, it appears it is only occurring at the final release when it is completed. Unless you somehow represent the features on the roadmap, it appears to the viewer (who may not be intimate with the Master Feature) that the work isn't even occurring until the very last release.