[
https://issues.apache.org/jira/browse/IGNITE-12082?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-12082:
------------------------------------
Summary: [Release] Update versions for pre-build DEB/RPM and describe how
to set these versions (was: [Release] Automate version assignment to pre-build
DEB/RPM or describe how to set packages version to RC version)
> [Release] Update versions for pre-build DEB/RPM and describe how to set these
> versions
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-12082
> URL: https://issues.apache.org/jira/browse/IGNITE-12082
> Project: Ignite
> Issue Type: Bug
> Reporter: Dmitriy Pavlov
> Assignee: Dmitriy Pavlov
> Priority: Major
> Fix For: 2.7.6
>
>
> Problem:
> https://ci.ignite.apache.org/viewLog.html?buildTypeId=Releases_ApacheIgniteMain_ReleaseBuild&buildId=4513186&branch_Releases_ApacheIgniteMain_ReleaseBuild=ignite-2.7.6
> RC 0 for 2.7.6. the build was successful, but versions for packages remain
> unchanged
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process does not
> require Release manager to update versions, but pre-build DEB & RPM keeps
> version from the previous release.
> Solution 1 (manual):
> We need to add a new step
> https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.Updatereleasebranchversionsandyearincopyrightmessages
> e.g. 4.1.4, where will ask a release manager to update versions.
> May be similar with commit
> https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=84c2dac5103a448bdaee88cb8290fd6e05a435bb
> Solution 2 (automatic)
> patch ./scripts/update-versions.sh to set packages version to current project
> version. This will not require any actions from the release manager since
> versions will be updated at step 4.1 with other assemblies versions.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
