public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Garrett Cooper <yanegomi@gmail.com>,
	Nathan Straz <nstraz@redhat.com>,
	Mike Frysinger <vapier@gentoo.org>
Cc: LTP list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] Goals and milestones
Date: Thu, 25 Jun 2009 14:40:38 +0530	[thread overview]
Message-ID: <1245921038.5542.46.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <A850D9FA-3282-440E-8B85-4A5BC5B4B067@gmail.com>

Great to hear back from you. Your plan looks good to me. However, i
would like to complete the Makefiles stuff this year itself. I know its
quite tedious. May be i would also pitch in to help you post my Linux
Symposium 2009 in July 2009.

On Wed, 2009-06-24 at 02:38 -0700, Garrett Cooper wrote: 
> Hi Subrata,
>      After being away from FOSS for a while I'm going to jump back in  
> a bit to get some work done in my personal time that aligns itself  
> with deliverables at Cisco. Here's the breakdown in terms of priorities:
> 1. Ltp crosscompile makefile push completion - need this to resolve  
> several issues with the current hacked make system and expedite  
> upgrades on our end. Hard goal: before July snapshot is released  
> (several items are dependent on a functioning upgrade). I will commit  
> in small, discrete patches to get the work done quicker, but I'll need  
> a makefile reviewer.

Nathan has already been helping us. So, we would get help from him and
Mike as well. I need to bring back Mike as well for more LTP
involvement. Mike, what do you say ;-)

Regards--
Subrata

> 2. Catepault work. This aligns itself with 1., but isn't directly tied  
> into 1.'s deliverable. Maybe October.
> 3. tst_res -> testreport replacement. Needs to take place somewhere  
> around 2.'s deliverable because we need a more license neutral and  
> equivalent, if not cleaner, means of doing test reporting to improve  
> whitebox testing inhouse. I'd say before Thanksgiving.
> 4. Upstart whitebox tests - I originally suggested this thinking that  
> there would be one Upstart release train, but Scott's maintaining  
> several, so I think it may be a better idea to omit these tests and  
> focus instead on exporting the graybox tests I'm working on inhouse at  
> Cisco as they are more portable and have more overall value. I'm  
> thinking maybe January or february of next year.
> 
> Hope that better describes where I'm at and what goals i'm trying to  
> accomplish.
> 
> Thanks,
> -Garrett 


------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2009-06-25 10:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24  9:38 [LTP] Goals and milestones Garrett Cooper
2009-06-24 13:24 ` Cyril Hrubis
2009-06-25  9:10 ` Subrata Modak [this message]
2009-06-25 14:18   ` Mike Frysinger
2009-06-26 11:33     ` Subrata Modak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1245921038.5542.46.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=nstraz@redhat.com \
    --cc=vapier@gentoo.org \
    --cc=yanegomi@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox