Nope Maven didn't provide such feature or at least I didn't get any questions on console.
I was today on a last step which takes lot's of time - build on machine whole framework by ant, but if failed on mustella tests. I will try tomorrow and see whether it happen again. If that very last step will be successful I will post vote thread. BTW. I had to still use in releasesteps.xml Mac that path ../../folder which I have mention In previous emails. On Thu, Aug 15, 2019, 8:36 PM Alex Harui <aha...@adobe.com.invalid> wrote: > Good to know. When it failed on Windows, did Maven offer command-line > options to continue from the point of failure? Unless all future RMs have > Macs, we still need to find a way for Windows-only RMs to be successful. > > -Alex > > On 8/15/19, 5:12 AM, "Piotr Zarzycki" <piotrzarzyck...@gmail.com> wrote: > > Good news. I tried today again upload artifacts from my Windows > machine - > it failed again. I copied my signed artifacts to my Mac machine which > is > using different internet connection. I'm not sure how it influences > all the > process but I have uploaded artifacts without any problem. I'm moving > forward with all of that. > > śr., 14 sie 2019 o 18:40 Alex Harui <aha...@adobe.com.invalid> > napisał(a): > > > Carlos, > > > > In [1] that you referenced it says about release branches: > > > > "During that time, bug fixes may be applied in this branch (rather > than on > > the develop branch)." > > > > To me, that means that new unstable changes should go into develop, > but > > changes to make the release better should be discussed with the RM > and > > committed to the release branch if agreed. We want to avoid > cherry-picking > > the develop branch to the release branch if at all possible. > > > > -Alex > > > > On 8/14/19, 1:58 AM, "Carlos Rovira" <carlosrov...@apache.org> > wrote: > > > > Hi Alex, > > > > El lun., 12 ago. 2019 a las 19:30, Alex Harui > > (<aha...@adobe.com.invalid>) > > escribió: > > > > > Also, the other committers should be aware that an RC is being > > created > > > because they see the emails being sent by the CI server and > ask the > > RM to > > > agree to accept a commit to the release branch instead of the > develop > > > branch. > > > > > > AFAIK, we should always commit to dev branch and not to release > branch. > > Releases are cut from develop. Only hot-fixes use to be branches > that > > have > > commits that fix something important in the release and then use > to be > > merged back to develop and master. Making commits to release > branches > > could > > bring some confusion and problems. > > > > At least from is what I always learnt and used [1] > > > > [1] > > > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnvie.com%2Fposts%2Fa-successful-git-branching-model%2F&data=02%7C01%7Caharui%40adobe.com%7C86e1e58dae864a33809708d72179c053%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014679195903060&sdata=bjUheSRli9gqZ7mGNo77rHSJULBlChoR9wpJevToGak%3D&reserved=0 > > > > -- > > Carlos Rovira > > > > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C86e1e58dae864a33809708d72179c053%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014679195903060&sdata=rA2ejTyLa08eWmDaDAQsMpAgdeNklbIuOMYLJWMVj4E%3D&reserved=0 > > > > > > > > -- > > Piotr Zarzycki > > Patreon: * > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C86e1e58dae864a33809708d72179c053%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014679195903060&sdata=zyWAUHptRYTuNyIzrlLhV4a3CCCQTRX%2F%2FDT3XoxKK4Y%3D&reserved=0 > < > https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C86e1e58dae864a33809708d72179c053%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637014679195903060&sdata=zyWAUHptRYTuNyIzrlLhV4a3CCCQTRX%2F%2FDT3XoxKK4Y%3D&reserved=0 > >* > > >
