A release plan connects a useful scope to a forecast of when it could be ready. A minimum viable product is the smallest coherent version that can test important assumptions or deliver the intended value. It is not permission to remove required quality or safety controls.
Historical velocity can produce a rough range when estimation and team conditions are comparable. Divide remaining points by a plausible delivery range and round up to whole Sprints. State the assumptions: scope may change, dependencies may slip and the future may differ from the past.
Avoid a date that hides those conditions. Break the release into useful increments, inspect progress and revise the forecast. A precise average-based calculation is still uncertain; more decimal places do not make it a promise.
A forecast range makes its assumptions visible.