Don't think AHS will block any releases. If the security stuff arrives by the time everything else planned for 2.4 is done, we can include it. Otherwise, we will call it not-feature-complete.
Going forward I think we should change to this mechanism. Now that we have a base stable release 2.2., we need to have alpha/beta/stable tags for features as opposed to the entire releases. Will start a separate thread about this on common-dev. Thanks +Vinod On Jan 13, 2014, at 4:13 PM, Alejandro Abdelnur <[email protected]> wrote: > Until we have security in AHS, will this block the 2.4 release (current > branch-2)? Or we would release 2.4 with AHS as 'not ready for production > use yet' > > Thanks > > > On Thu, Jan 9, 2014 at 3:22 PM, Vinod Kumar Vavilapalli < > [email protected]> wrote: > >> Tx for the heads up Zhijie! >> >> I propose that we merge it into trunk *and* branch-2 but don't call the >> feature stable till it really is. This is actually no different than other >> stuff like RM HA which is directly done on trunk+branch-2, but aren't >> stable yet. >> >> On top of this, I can see YARN-1530 needing a branch and that too on top >> of what we already have in YARN-321 because they are related. Maintaining a >> YARN-321 branch separately and then YARN-1530 is a massive pain. >> >> Thanks, >> +Vinod >> >> On Jan 9, 2014, at 11:14 AM, Alejandro Abdelnur <[email protected]> wrote: >> >>> Zhijie, >>> >>> Thanks for updating YARN-321 branch to latest trunk. >>> >>> By doing a diff between the trunk and the YARN-321 branch the following >>> java files already existing in trunk are being modified: >>> >>> [....] >> >>> In many cases the changes are clean lump additions, however for the >>> following files: >>> >>> * YarnClientImpl.java >>> * ApplicationCLI.java >>> * RMServerUtils.java >>> * RMAppImpl.java >>> * RMContainerImpl.java >>> * plus many of the testcase classes >>> >>> The changes are interleaved in the existing code. >>> >>> Merging this into trunk but not into branch-2 will complicate things for >>> all patches (after the merge) that touch the above files and have to go >> to >>> branch-2. >>> >>> I see a couple of alternatives here: >>> >>> 1. if the changes outside of AHS (the java files listed above) are not >>> destabilizing, we could make sure all of them make it to branch-2 and >> just >>> leave AHS in trunk (until security is done) >>> 2. finish up security in branch YARN-321, then do the merge in trunk & >>> branch-2. For this, branch YARN-321 developers should make sure they >> update >>> branch YARN-321 to latest trunk on regular basis (ideally every couple of >>> days), then things should not be that painful. >>> >>> Thoughts? >>> >>> Thanks. >>> >>> >>> On Wed, Jan 8, 2014 at 11:36 PM, Zhijie Shen <[email protected]> >> wrote: >>> >>>> Hi folks, >>>> >>>> The new YARN-321 branch is done. >>>> >>>> Thanks, >>>> Zhijie >>>> >>>> >>>> On Wed, Jan 8, 2014 at 3:35 PM, Zhijie Shen <[email protected]> >> wrote: >>>> >>>>> Hi folks, >>>>> >>>>> I'm going to deprecate the current YARN-321 branch, create a new one >>>> based >>>>> on the latest trunk, and then merge the YARN-321 commits into the new >>>>> branch. >>>>> >>>>> Please allow me to hold the branch for a while. Will send another >>>>> notification email when it is done. >>>>> >>>>> Thanks, >>>>> Zhijie >>>>> >>>>> -- >>>>> Zhijie Shen >>>>> Hortonworks Inc. >>>>> http://hortonworks.com/ >>>>> >>>> >>>> >>>> >>>> -- >>>> Zhijie Shen >>>> Hortonworks Inc. >>>> http://hortonworks.com/ >>>> >>>> -- >>>> 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. >>>> >>> >>> >>> >>> -- >>> Alejandro >> >> >> -- >> 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. >> > > > > -- > Alejandro -- 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.
