We are releasing from specific commit. The problem is laying out on setup appropriate values for ANT build and Maven build. This is where all failing. All the problem is happening because we need omit one version, cause npm was updated with 0.9.3 - Not sure why.
Update of version should happen automatically and releasecandidate script is doing that. I don't know now what to do: 1. Update develop branch from 0.9.4-SNAPSHOT to 0.9.5-SNAPSHOT 2. Update release/0.9.4 to 0.9.4 3. Deploy maven artifacts to staging area All of that things are complex because we need to skip one version. I'm the second release manager (after Om) who gave up with whole process. Piotr śr., 19 wrz 2018 o 10:59 Carlos Rovira <carlosrov...@apache.org> napisał(a): > Hi Olaf, > > hehe, I think we overlap and mostly said the same ;-) > for me that's the right way. > Thanks > > > > El mié., 19 sept. 2018 a las 10:57, Olaf Krueger (<m...@olafkrueger.net>) > escribió: > > > > I think there should be some rules where during release process > > committing > > > to develop is stopped. > > > > What do you think about creating a "release/v0.9.x" branch which has to > be > > merged back to master and dev after the release is done instead of doing > > the > > release from dev? > > > > Thanks for doing all the hard work, keep it up!!! > > > > Olaf > > > > > > > > > > > > -- > > Sent from: http://apache-royale-development.20373.n8.nabble.com/ > > > > > -- > Carlos Rovira > http://about.me/carlosrovira > -- Piotr Zarzycki Patreon: *https://www.patreon.com/piotrzarzycki <https://www.patreon.com/piotrzarzycki>*
