Sure. Makes sense. Sent from my iPhone
> On 18-Aug-2014, at 10:18 pm, "Arpit Gupta" <[email protected]> wrote: > > Sounds good. Should i create a jira to create a new CHANGES.txt and move > appropriate jira's from top level CHANGES.txt to the new one? > > > Arpit > > > On Fri, Aug 15, 2014 at 10:07 AM, Srikanth Sundarrajan <[email protected]> > wrote: > >> My preference would be to maintain the test suite changes independently. >> >> Regards >> Srikanth Sundarrajan >> >>> From: [email protected] >>> Date: Thu, 14 Aug 2014 16:01:40 -0700 >>> Subject: [DISCUSS] Documenting commits in falcon-regression >>> To: [email protected] >>> >>> Hi All >>> >>> >>> We now have falcon regression module on falcon which will allow people to >>> run regression on deployed clusters. This mail is to discuss how do we >> want >>> to track the changes in that code >>> >>> a. We use the same CHANGES.txt and add all commits made for falcon >>> regression there. >>> >>> b. create a new CHANGES.txt under the falcon-regression folder and track >>> all the changes there for falcon regression >>> >>> >>> What do others think about this? >>> >>> Can we rename the component merlin to falcon-regression so its easier for >>> new folks to understand what that component is for? >>> >>> -- >>> CONFIDENTIALITY NOTICE >>> NOTICE: This message is intended for the use of the individual or entity >> to >>> which it is addressed and may contain information that is confidential, >>> privileged and exempt from disclosure under applicable law. If the reader >>> of this message is not the intended recipient, you are hereby notified >> that >>> any printing, copying, dissemination, distribution, disclosure or >>> forwarding of this communication is strictly prohibited. If you have >>> received this communication in error, please contact the sender >> immediately >>> and delete it from your system. Thank You. > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity to > which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You.
