Re: [linux-distros-dev] 0.2 + agile development

[Andrew Overholt <overholt@xxxxxxxxxx>]

On Wed, 2009-02-25 at 16:09 +0100, Alexander Kurtakov wrote:
> Andrew Overholt wrote:
> > Hi,
> >
> > What do people think about an 0.2 release?  If we want to do it before
> > EclipseCon (23 - 26 March), we need to get started on the process very
> > soon.  In fact, I'm not even sure we _can_ have something out before
> > EclipseCon, but we can at least have a release candidate -- which
> > doesn't have to go through a release review since it isn't an official
> > release.
> >   
> I would like to start the process next Monday.
> Having a release before EclipseCon would allow us to gain even more 
> publicity.

I agree.  I will work with you to come up with release engineering
procedures and I can set up Hudson builds and get signing done, etc.

> > - aim for at least 80% test coverage
> > -- this is an area that's a bit weak for us
> > -- hopefully the exposure of code coverage reports as part of the common
> > builder and in Hudson will help
> > -- if you're not already using it, EclEmma is a great tool
> >   
> Another tool that can help a lot is moreUnit.
> I think we should start with lower aim than 80% and increasing the level 
> for every release with 5 or 10%.

This is a great idea.  Should we aim for 20% overall (all projects) for
0.2 since we won't have time to focus on it too much and then 30% for
0.3 and so on?

> Just FYI specfile editor had around 45% coverage but after I started 
> looking at tests so much unneeded code was removed that the coverage is 
> now below 40. So it really worth it.

:)

> I would propose putting some coverage level as a guideline to every 
> release. Of course this is not going to hold any release but it will 
> allow us to at least have some plan.

Agreed.

Thanks for the thoughts.

Andrew