Exactly, you need to backport the scm changes in all pom.xmls from https://issues.apache.org/jira/browse/OAK-9440 <https://issues.apache.org/jira/browse/OAK-9440> to other branches if you want to cut releases from them. Konrad
> On 14. Jul 2021, at 15:02, Julian Sedding <[email protected]> wrote: > > Hi Andrei > > I assume you would need to adjust the SCM Info in the pom of the > "1.22" branch in Git (compare with the pom in "trunk" branch). The SVN > branches are dead after migration to Git AFAIK. > > I don't know if other adjustments are required. Konrad would likely know. > > Regards > Julian > > On Wed, Jul 14, 2021 at 2:44 PM Andrei Dulceanu <[email protected]> wrote: >> >> Hi all, >> >> I have a quick question for you: are all Oak svn branches still updated >> after migration to Git? >> >> I’m trying to cut 1.22.8 release and obviously it fails if I try it under >> git checkout, so I moved in the svn checkout, but then this seems outdated: >> >> jackrabbit-oak-1-22 dulceanu$ svn log -l 1 >> ------------------------------------------------------------------------ >> r1888717 | mreutegg | 2021-04-13 12:58:52 +0300 (Tue, 13 Apr 2021) | 3 >> linesOAK-9393: Release Oak 1.22.7Fix version of oak-doc and >> oak-doc-railroad-macro after release >> >> >> I quickly checked what’s the status for trunk and this one is up-to-date: >> >> jackrabbit-oak dulceanu$ svn log -l 1 >> ------------------------------------------------------------------------ >> r1890974 | miroslav | 2021-06-22 18:33:17 +0300 (Tue, 22 Jun 2021) | 1 >> lineOAK-9469 in case of the timeout in AzureRepositoryLock, retry >> renewing the lease >> ------------------------------------------------------------------------ >> >> How can I progress with cutting 1.22.8 release? Any ideas? >> >> Regards, >> Andrei
