cobertura-devel

RE: [Cobertura-devel] Cobertura 1.5

[M C <mor...@ya...>]

Mark Doliner wrote:
>Hi, I'm thinking about releasing Cobertura 1.5 soon. 
>It still doesn't supported multiple source
directories >for reporting (I REALLY need to look at
that patch), >or multiple class directories for
instrumenting, but >there are a lot of other changes.
>What do you guys think?

IMHO Without the patch for multiple source directories
I personally do not see the point of a release now.
Better to wait for the real thing.

Cheers,
Morten

RE: [Cobertura-devel] Cobertura 1.5

[Mark D. <Mar...@sa...>]

> -----Original Message-----
> To: cob...@li...
> Subject: RE: [Cobertura-devel] Cobertura 1.5
>=20
> Mark Doliner wrote:
> > Hi, I'm thinking about releasing Cobertura 1.5 soon.=20
> > It still doesn't supported multiple source
> > directories for reporting (I REALLY need to look at
> > that patch), or multiple class directories for
> > instrumenting, but there are a lot of other changes.
> > What do you guys think?
>=20
> IMHO Without the patch for multiple source directories
> I personally do not see the point of a release now.
> Better to wait for the real thing.

I've been numbering things like crazy lately:

1. Releasing is easy.
2. Releasing gives us publicity (announcement on freshmeat.net, etc).
3. I'm completely willing to release now and then again a week later.
4. I don't really see a difference between releasing 1.5 now and then =
1.6 next week vs. releasing 1.5beta now and then 1.5final next week.
5. I try to avoid making lots of changes to code and then releasing =
without waiting a few days to let the dust settle.  And these changes =
for multiple source directories seem pretty large, to me
6. There are a lot of changes in 1.5 that I'd like to get out the door.

-Mark

Re: [SPAM-LOW] RE: [Cobertura-devel] Cobertura 1.5

[Jeremy T. <jer...@gm...>]

I'd rather see us commit / test the multiple fileset fixes and release in a=
=20
couple of days personally. The multiple fileset thing seems to be the=20
biggest thing that has been asked for by users.=20

I agree with the publicity generated by releases, but the more we have, the=
=20
more people have the potential for thinking that we over-release, so they=
=20
ignore the new features, especially when they're looking for a feature (i.e=
.=20
multiple filesets) and it's not released (i.e. if we release 1.5 now).

Just my $0.02....

Just wondering, if I commit the multiple fileset changes tonight.... how=20
many on this list would be willing / able to take the latest build from CVS=
=20
and test in their setup over the next few days (let's say Tuesday,=20
Wednesday, Thursday) so that we can be sure it's production-ready, and then=
=20
release Friday?

If we could have three or more people test it wherever they currently use=
=20
Cobertura, it would be great. This way we also ensure=20
backwards-compatibility.

Jeremy

On 8/1/05, Mark Doliner <Mar...@sa...> wrote:
>=20
> > -----Original Message-----
> > To: cob...@li...
> > Subject: RE: [Cobertura-devel] Cobertura 1.5
> >
> > Mark Doliner wrote:
> > > Hi, I'm thinking about releasing Cobertura 1.5 soon.
> > > It still doesn't supported multiple source
> > > directories for reporting (I REALLY need to look at
> > > that patch), or multiple class directories for
> > > instrumenting, but there are a lot of other changes.
> > > What do you guys think?
> >
> > IMHO Without the patch for multiple source directories
> > I personally do not see the point of a release now.
> > Better to wait for the real thing.
>=20
> I've been numbering things like crazy lately:
>=20
> 1. Releasing is easy.
> 2. Releasing gives us publicity (announcement on freshmeat.net<http://fre=
shmeat.net>,=20
> etc).
> 3. I'm completely willing to release now and then again a week later.
> 4. I don't really see a difference between releasing 1.5 now and then 1.6=
next week vs. releasing=20
> 1.5beta now and then 1.5final next week.
> 5. I try to avoid making lots of changes to code and then releasing=20
> without waiting a few days to let the dust settle. And these changes for=
=20
> multiple source directories seem pretty large, to me
> 6. There are a lot of changes in 1.5 that I'd like to get out the door.
>=20
> -Mark
>=20
>=20
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>=20
>

Re: [SPAM-LOW] RE: [Cobertura-devel] Cobertura 1.5

[Jeremy T. <jer...@gm...>]

I made all the changes last night that we mentioned above, but I'm not goin=
g=20
to commit until I have time to integrate pieces of everyone else's patches,=
=20
too (since Grzegorz and James had additional unit tests as well, I'd like t=
o=20
integrate those). I'll do this tonight.

I ended up working much later than I though I would while we were managing =
a=20
release.

Until then...
Jeremy

On 8/1/05, Jeremy Thomerson <jer...@gm...> wrote:
>=20
> I'd rather see us commit / test the multiple fileset fixes and release in=
=20
> a couple of days personally. The multiple fileset thing seems to be the=
=20
> biggest thing that has been asked for by users.=20
>=20
> I agree with the publicity generated by releases, but the more we have,=
=20
> the more people have the potential for thinking that we over-release, so=
=20
> they ignore the new features, especially when they're looking for a featu=
re=20
> (i.e. multiple filesets) and it's not released (i.e. if we release 1.5now=
).
>=20
> Just my $0.02....
>=20
> Just wondering, if I commit the multiple fileset changes tonight.... how=
=20
> many on this list would be willing / able to take the latest build from C=
VS=20
> and test in their setup over the next few days (let's say Tuesday,=20
> Wednesday, Thursday) so that we can be sure it's production-ready, and th=
en=20
> release Friday?
>=20
> If we could have three or more people test it wherever they currently use=
=20
> Cobertura, it would be great. This way we also ensure=20
> backwards-compatibility.
>=20
> Jeremy
>=20
> On 8/1/05, Mark Doliner <Mar...@sa...> wrote:
> >=20
> > > -----Original Message-----
> > > To: cob...@li...
> > > Subject: RE: [Cobertura-devel] Cobertura 1.5
> > >
> > > Mark Doliner wrote:=20
> > > > Hi, I'm thinking about releasing Cobertura 1.5 soon.
> > > > It still doesn't supported multiple source
> > > > directories for reporting (I REALLY need to look at
> > > > that patch), or multiple class directories for=20
> > > > instrumenting, but there are a lot of other changes.
> > > > What do you guys think?
> > >
> > > IMHO Without the patch for multiple source directories
> > > I personally do not see the point of a release now.=20
> > > Better to wait for the real thing.
> >=20
> > I've been numbering things like crazy lately:
> >=20
> > 1. Releasing is easy.
> > 2. Releasing gives us publicity (announcement on freshmeat.net=20
> > <http://freshmeat.net>, etc).
> > 3. I'm completely willing to release now and then again a week later.
> > 4. I don't really see a difference between releasing 1.5 now and then=
=20
> > 1.6 next week vs. releasing 1.5beta now and then 1.5final next week.
> > 5. I try to avoid making lots of changes to code and then releasing=20
> > without waiting a few days to let the dust settle. And these changes fo=
r=20
> > multiple source directories seem pretty large, to me
> > 6. There are a lot of changes in 1.5 that I'd like to get out the door.
> >=20
> > -Mark
> >=20
> >=20
> > -------------------------------------------------------
> > SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> > from IBM. Find simple to follow Roadmaps, straightforward articles,
> > informative Webcasts and more! Get everything you need to get up to
> > speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id=16492&opclick<http:=
//ads.osdn.com/?ad_idt77&alloc_id%16492&opclick>
> > _______________________________________________
> > Cobertura-devel mailing list
> > Cob...@li...
> > https://lists.sourceforge.net/lists/listinfo/cobertura-devel
> >=20
> >=20
>

[Cobertura-devel] Re: Cobertura 1.5

[Jeremy T. <jer...@gm...>]

I spent a few hours today making instrumentation and reporting work
with multiple source directories.  Rather than committing it, I am
sending out the patch, asking for someone to review it.  It also adds
a second directory of source (just one simple faux class) so that we
have the multiple filesets / multiple source directories in our
instrumentation and reporting build.

I didn't have time to update any documentation that we have for usage,
so if someone could update that (assuming that everyone likes this
solution), that would be great.  Also, I just realized that the
reporting task should be backwards-compatible with the old srcdir
attribute, but I don't think I remembered to do that with the
instrumentation task.  If I didn't, but everyone likes this patch,
I'll commit these changes and add that to the instrumentation class
for backwards compatibility.

Please let me know what you think.

Jeremy Thomerson

On 7/27/05, M C <mor...@ya...> wrote:
> Mark Doliner wrote:
> >Hi, I'm thinking about releasing Cobertura 1.5 soon.=20
> >It still doesn't supported multiple source
> directories >for reporting (I REALLY need to look at
> that patch), >or multiple class directories for
> instrumenting, but >there are a lot of other changes.
> >What do you guys think?
>=20
> IMHO Without the patch for multiple source directories
> I personally do not see the point of a release now.
> Better to wait for the real thing.
>=20
> Cheers,
> Morten
>=20
>=20
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September
> 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing & Q=
A
> Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
> _______________________________________________
> Cobertura-devel mailing list
> Cob...@li...
> https://lists.sourceforge.net/lists/listinfo/cobertura-devel
>=20
>