Carlos, IMO, your arguments are flawed. You are saying because there was a bug or two before we got the CI process working, we have to throw out that process and start over.
You are also essentially saying that because you removed code and the algorithm is now broken, it is time to go back to the prior algorithm which did not work. Look at the commits. The Maven changes removed the flags I added to allow the CI steps to work. If you had looked at the ramifications of removing the Maven options, and why the options were added in the first place, or even asked why on the list, you would hopefully have preserved the options and then the CI steps would have worked. But I see no evidence that was done. Instead, it looks like options were just removed. Sometimes that happens unintentionally in a refactor, but then you go back and look at commit history to try to understand why, or ask questions on the list. We used to use standards. I have now written this 3 times at least. The standards worked for me, but did not work for others. Having a set of steps on CI gives us a single known good configuration to work on that we can all access, instead of wondering why the RM's computer isn't doing the right thing. Fixing the CI should be as simple as re-introducing the noPush and skipGPG options, assuming nothing else was touched regarding creating the reproducible binaries. It is entirely possible that in the time spent on this thread so far, you could have made significant progress on the CI steps. -Alex On 3/18/20, 8:32 AM, "Carlos Rovira" <[email protected]> wrote: Hi Piotr, if you check CI server, I duplicated 1,2 and 3 steps (to avoid removing anything from the original steps from Alex), and worked over there. I was trying lots of things, and in the process I did get to pass those ones. Even I can't ensure but seems to me that not always the process was doing the same since some times I had hanging problems that exasperated me. Its clear that the work done for Alex was intense and amazing, and never compared by the few time I take to try to fix it. But it's not that the problem. I just thing we need take the whole problem with another perspective to take the opportunity of remove most of the current problems or we'll be doing the same ones one time and again. This is not about talking about the serious work done. I applauded that effort many times here. It's that as Yishay, I don't see the final results get what we all wanted. But as we said, is just my opinion and my vote and is clear that I can't start such huge effort and ask Chris to invest in it if I don't get a back on you all to do it. El mié., 18 mar. 2020 a las 12:42, Piotr Zarzycki (< [email protected]>) escribió: > Btw. I truly doubt that it would be bigger than time which was invested in > building this whole release process. > > śr., 18 mar 2020 o 12:41 Piotr Zarzycki <[email protected]> > napisał(a): > > > Carlos, > > > > Why it is so huge effort ? What was broken so much that you are talking > > about huge effort ? > > > > śr., 18 mar 2020 o 12:37 Carlos Rovira <[email protected]> > > napisał(a): > > > >> Hi Piotr, > >> > >> as I responded before, I think that will be a huge task, in effort and > >> time, and a task that can be easily broken again as any other one > >> introduces new changes, what is something will happen for sure as we > >> evolve. So what I'm offering is my time to be used in a way that can > allow > >> us to have a more reliable workflow. If I work on trying to fix as it's > >> now, I probably will not succeed since I already tried for several hours > >> and days (you can check emails around 19 or 20th Nov I think), and > nothing > >> of my tries could make a difference. Instead, I'm think taking a big > >> different approach can make a difference. I can be wrong, but in that > >> case, > >> we'll know for sure that the way to go is the current one. > >> > >> > >> El mié., 18 mar. 2020 a las 12:05, Piotr Zarzycki (< > >> [email protected]>) escribió: > >> > >> > Carlos, > >> > > >> > In the other ways you are not going to fix current steps and release > new > >> > version of SDK ? > >> > > >> > > >> > > >> > śr., 18 mar 2020 o 10:39 Carlos Rovira <[email protected]> > >> > napisał(a): > >> > > >> > > Hi all and thanks for your responses: > >> > > > >> > > @greg, yes the plan I point is to do research to try a new way and > see > >> > > where we go. At the end, we don't get it, it will be our > >> responsibility > >> > and > >> > > our time. > >> > > > >> > > @yishay, I think you state a concrete but very real issue. I think > the > >> > work > >> > > done by Alex was amazing (no doubt here), but I'm afraid, as much as > >> it > >> > > pains me to say it, that it does not solve the problem you state and > >> the > >> > > proof is that only Piotr tried to use the process and it was not > easy > >> and > >> > > then when fixing other things, it has broken with some ease. > >> > > > >> > > @om, as I said in the initial email. There's no war anymore between > >> Maven > >> > > and ANT. We all want both, and I'm using both when developing Royale > >> to > >> > > test. As well I continually know more about how things are done in > >> Maven. > >> > > My position is just that we need to separate concerns. One thing is > to > >> > have > >> > > both systems for developers and user to use (Maven and ANT), but my > >> point > >> > > is that Releasing should just involve Maven, since is more suite for > >> > > releasing at Apache and CIs, and ensure Ant continue working as > >> expected. > >> > > So no one wants one over the other, or remove one of them. That's > not > >> the > >> > > problem anymore. > >> > > > >> > > @piotr, I think your experience is very important, since you were > the > >> > only > >> > > one that do the full process. My guess is that removing ANT from the > >> > > release process will remove completely all the pain with such > complex > >> > > process and we all be able release from our own machines without > >> having > >> > > problems with complex task, uploading artifacts to a.o and more. We > >> just > >> > > need to ensure ANT still can be build exactly as before, and > continue > >> to > >> > > produce the same. > >> > > > >> > > So in the end, we can stick with the old process, or try another > >> > different > >> > > approach to it build over standards. That means Chris and I will be > >> using > >> > > our times not yours. If we succeed, your test of the new approach > will > >> > need > >> > > to ensure all the prerequisites and be lot more simpler. If we don't > >> get > >> > to > >> > > that and fail in the process, just announce here and we can continue > >> in > >> > the > >> > > old process. > >> > > > >> > > That's my proposal (that will need to be consensuated first here and > >> then > >> > > with Chris) > >> > > > >> > > Thanks > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > El mié., 18 mar. 2020 a las 8:14, Alex Harui > >> (<[email protected] > >> > >) > >> > > escribió: > >> > > > >> > > > > >> > > > > >> > > > On 3/17/20, 11:37 PM, "OmPrakash Muppirala" < > [email protected]> > >> > > wrote: > >> > > > > >> > > > My 2 cents: > >> > > > > >> > > > I don't think we need to go back to the Ant vs Maven > discussion. > >> > If > >> > > > the > >> > > > Maven build/stage/release scripts works flawlessly, an Ant > task > >> can > >> > > > simply > >> > > > call it. There is no reason both cannot be worked on > >> continuously. > >> > > > In the > >> > > > same way, if Maven users want, they can call Ant scripts as > >> needed. > >> > > > > >> > > > Why do both camps want the other way to go away? > >> > > > > >> > > > I don't want one to go away. I want to use Maven for what it is > >> good > >> > for > >> > > > and Ant for what it is good for. > >> > > > > >> > > > For example, we also publish to NPM as part of the release. > >> There > >> > is > >> > > a > >> > > > node.js script that gets called from the Ant script during the > >> > > release > >> > > > process. The node.js script is a black box as far as the Ant > >> > script > >> > > is > >> > > > concerned. > >> > > > > >> > > > That said, Carlos if you think you can get a release done with > >> just > >> > > > Maven, > >> > > > please go ahead and give it a shot. From what I remember, the > >> > Maven > >> > > > part > >> > > > of the build/release was the issue and not the Ant portions. > We > >> > all > >> > > > would > >> > > > love to see improvements there. > >> > > > > >> > > > Alex, you say that Carlos did not work in the trenches during > >> the > >> > > > release > >> > > > process, but are objecting (I think, if I understand your > email > >> > > > correctly) > >> > > > to him wanting to work now. That seem contradictory, IMHO. > >> > > > > >> > > > I'm saying that if Carlos/Chris go back to the Maven Release > Plugin > >> > > > process, it will likely bring us back to the same problems we > >> created > >> > the > >> > > > CI steps to work around. So why go through all of that again? > >> > > > > >> > > > Like Piotr just posted, Carlos should get in the trenches and get > >> the > >> > CI > >> > > > steps to work with the new Maven poms. Not acknowledging that > >> there > >> > > have > >> > > > been past problems using the process they propose is going to > >> result in > >> > > > more time wasted. > >> > > > > >> > > > -Alex > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > >> > > -- > >> > > Carlos Rovira > >> > > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C62313a2951e04905eebb08d7cb5196aa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637201423589581093&sdata=d6lrb8AjhzVvIOjaL7bStowSJMG4IsIWpv6EaQPWG04%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%7C62313a2951e04905eebb08d7cb5196aa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637201423589581093&sdata=SGsBKW4Qg%2Bu5lb7TppHyBg0VaENwQaFdCb11KvHbjkw%3D&reserved=0 > >> > <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C62313a2951e04905eebb08d7cb5196aa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637201423589581093&sdata=SGsBKW4Qg%2Bu5lb7TppHyBg0VaENwQaFdCb11KvHbjkw%3D&reserved=0>* > >> > > >> > >> > >> -- > >> Carlos Rovira > >> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C62313a2951e04905eebb08d7cb5196aa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637201423589581093&sdata=d6lrb8AjhzVvIOjaL7bStowSJMG4IsIWpv6EaQPWG04%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%7C62313a2951e04905eebb08d7cb5196aa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637201423589581093&sdata=SGsBKW4Qg%2Bu5lb7TppHyBg0VaENwQaFdCb11KvHbjkw%3D&reserved=0 > > <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C62313a2951e04905eebb08d7cb5196aa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637201423589581093&sdata=SGsBKW4Qg%2Bu5lb7TppHyBg0VaENwQaFdCb11KvHbjkw%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%7C62313a2951e04905eebb08d7cb5196aa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637201423589581093&sdata=SGsBKW4Qg%2Bu5lb7TppHyBg0VaENwQaFdCb11KvHbjkw%3D&reserved=0 > <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C62313a2951e04905eebb08d7cb5196aa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637201423589591083&sdata=zx8%2Bw0r75sYsdeAY2MTYNpirklE0SS5f8AiegQSMNlQ%3D&reserved=0>* > -- Carlos Rovira https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C62313a2951e04905eebb08d7cb5196aa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637201423589591083&sdata=FuwtzrOf1EGE9hhvyTpfLLrJ7KTlInxENapPLG5jlnQ%3D&reserved=0
