Hello Brahma, OK. Thanks. I will be sure to take a look. subtasks seems meaningful.
J > Gesendet: Donnerstag, 16. März 2023 um 03:56 Uhr > Von: "Brahma Reddy Battula" <bra...@apache.org> > An: dev@ambari.apache.org > Betreff: Re: Re: what were the plans for: AMBARI-25504 > > Thanks jtane reaching out on this. This is one of the planned improvements > for the trunk. > > Ideally it's better to have subtasks based on the *module* or dependency so > that review can be easier. ( script by script isn't a good idea here, as > there are a lot of scripts there.) > We can try to have as much as possible unit tests and some amount manula > verification by deploying the changes. > > There are some tasks created on *AMBARI-25854, *Let's continue discussing > further tasks there. > > > On Thu, Mar 16, 2023 at 5:27 AM <jt...@web.de> wrote: > > > Hello again, > > > > OK... So I don't know whether you want to consider this as a real > > duplicate. > > What is the development/commit/testing process here. > > > > Should it be: > > - commits scripts by scripts, feature type by feature type > > - all in one go using the py2to3 script and one commit > > - ... > > > > How are the test performed.... From my understanding (after reading > > https://cwiki.apache.org/confluence/display/AMBARI/How+to+Contribute), > > there is a review process here. But by performing py2to3 on the whole > > script base might be too much to check in one go. > > > > What do you think ? I would be glad to be of help, knowing that our team > > would like to be able to deploy ambari on new machine with debian11 where > > python2 is not available. > > > > > > Thanks in advance for any relevant information. > > > > J > > > > > > > > > > > > > Gesendet: Donnerstag, 16. März 2023 um 00:42 Uhr > > > Von: jt...@web.de > > > An: dev@ambari.apache.org > > > Betreff: Aw: Re: what were the plans for: AMBARI-25504 > > > > > > Hello, > > > > > > Thanks I will take a look at > > https://issues.apache.org/jira/browse/AMBARI-25854 . > > > > > > Thanks for the answer. So it would make sense, to mark the issue > > https://issues.apache.org/jira/browse/AMBARI-25504 as duplicate of > > AMBARI-25854 > > > > > > my 2c, > > > > > > J > > > > > > > Gesendet: Mittwoch, 15. März 2023 um 07:45 Uhr > > > > Von: "吴治国" <wzg547228...@163.com> > > > > An: "dev@ambari.apache.org" <dev@ambari.apache.org> > > > > Betreff: Re: what were the plans for: AMBARI-25504 > > > > > > > > Sorry, we didn't see AMBARI-25504, but the OpenEuler community is > > helping with this feature and creating a new JIRA for it: AMBARI-25854, > > maybe we can discuss it there. > > > > > > > > > > > > Best Regards, > > > > Zhiguo Wu > > > > ---- Replied Message ---- > > > > | From | <jt...@web.de> | > > > > | Date | 3/14/2023 05:15 | > > > > | To | <dev@ambari.apache.org> | > > > > | Subject | what were the plans for: AMBARI-25504 | > > > > Hello, > > > > > > > > I was wondering what were the plans for: > > https://issues.apache.org/jira/browse/AMBARI-25504 > > > > > > > > kind Regards, > > > > > > > > J > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org > > > > For additional commands, e-mail: dev-h...@ambari.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org > > > For additional commands, e-mail: dev-h...@ambari.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org > > For additional commands, e-mail: dev-h...@ambari.apache.org > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@ambari.apache.org For additional commands, e-mail: dev-h...@ambari.apache.org
