Hm, there're too many TODO things. After fix examples, IO, and yarn module bugs, Let's just cut a release this month.
What do you think? On Tue, Nov 29, 2011 at 3:33 PM, Edward J. Yoon <[email protected]> wrote: >>> HAMA-438 <https://issues.apache.org/jira/browse/HAMA-438> Generate Hama >>> config files from build -> Does this really belong to 0.4.0? How important >>> is this? > > I don't know exactly at the moment but, some files should be moved > 'resources' directory and we have to learn about automated deployment > with maven before 0.4 release vote. HAMA-438 also should be fixed at > this stage. > > On Tue, Nov 29, 2011 at 10:04 AM, Edward J. Yoon <[email protected]> > wrote: >> I'd like to manage releases at least for a while, because I'm a active >> early customer in real world. However, it would really help if someone >> could help me out. >> >> On Tue, Nov 29, 2011 at 4:57 AM, Thomas Jungblut >> <[email protected]> wrote: >>> Great, thank you. >>> >>> Let's cleanup the issues in the queue. >>> >>> I think these issues are not a must-have for 0.4.0: >>> HAMA-466 <https://issues.apache.org/jira/browse/HAMA-466> Refactoring to >>> clean code -> (Ongoing efford) >>> HAMA-477 <https://issues.apache.org/jira/browse/HAMA-477> Refactor the Hama >>> examples tests -> (Ongoing efford) >>> HAMA-470 <https://issues.apache.org/jira/browse/HAMA-470> The Web Ui should >>> contain the version number -> Don't think this is really necessary for >>> 0.4.0. Although it is a nice feature. >>> HAMA-445 <https://issues.apache.org/jira/browse/HAMA-445> Make configurable >>> checkpointing -> Checkpointing is deactivated and is useless without really >>> restarting the tasks (fault tolerance). So we can cut this. >>> HAMA-438 <https://issues.apache.org/jira/browse/HAMA-438> Generate Hama >>> config files from build -> Does this really belong to 0.4.0? How important >>> is this? >>> HAMA-447 <https://issues.apache.org/jira/browse/HAMA-447> Apply Findbugs >>> and stuff -> (Ongoing efford) >>> >>> With cutting these from the roadmap we just have 9 issues left, which are >>> quite straight forward. 2-3 of them already contain patches. >>> What do you think? >>> >>> BTW who is release manager? Edward? >>> >>> 2011/11/28 Chia-Hung Lin <[email protected]> >>> >>>> I committed the patch for HAMA-363. >>>> >>>> Please let me know if anything in terms of this. >>>> >>>> On 28 November 2011 19:03, Thomas Jungblut >>>> <[email protected]> wrote: >>>> > It is very convenient for the user to view log files within the web >>>> > frontend. >>>> > But this is quite a large issue, so I'm not sure. >>>> > +-0 >>>> > >>>> > 2011/11/28 Edward J. Yoon <[email protected]> >>>> > >>>> >> Hmm, Should we add HAMA-442 to 0.4 release? >>>> >> >>>> >> 2011/11/27 Edward J. Yoon <[email protected]>: >>>> >> > +1 >>>> >> > >>>> >> > Sent from my iPhone >>>> >> > >>>> >> > On 2011. 11. 26., at 오후 8:21, Thomas Jungblut < >>>> >> [email protected]> wrote: >>>> >> > >>>> >> >> Hey all, I would like to freeze the new features for 0.4.0 from now >>>> on. >>>> >> >> >>>> >> >> The features that should be done before 0.4.0 release would be: >>>> >> >>> HAMA-479 Add Counters to Hama Jobs >>>> >> >>> HAMA-363 Add network condition monitoring >>>> >> >> >>>> >> >> What do you think? >>>> >> >> >>>> >> >> -- >>>> >> >> Thomas Jungblut >>>> >> >> Berlin <[email protected]> >>>> >> > >>>> >> >>>> >> >>>> >> >>>> >> -- >>>> >> Best Regards, Edward J. Yoon >>>> >> @eddieyoon >>>> >> >>>> > >>>> > >>>> > >>>> > -- >>>> > Thomas Jungblut >>>> > Berlin <[email protected]> >>>> > >>>> >>> >>> >>> >>> -- >>> Thomas Jungblut >>> Berlin <[email protected]> >>> >> >> >> >> -- >> Best Regards, Edward J. Yoon >> @eddieyoon > > > > -- > Best Regards, Edward J. Yoon > @eddieyoon -- Best Regards, Edward J. Yoon @eddieyoon
