commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Simon Kitching <skitch...@apache.org>
Subject Re: [beanutils] bugzilla blitz?
Date Thu, 26 May 2005 02:16:56 GMT
Hi Niall,

In general the patches we are applying are likely to be small; they are
bugfixes for bugzilla reports not new features.

So I wouldn't have thought that posting patches separately would be
useful. After all, every subversion commit automatically generates a
patch file that gets emailed to the list anyway. If someone queries the
patch they see in a commit mail then we can talk about it and
potentially back it out again.

The commit-first approach would seem to save a large amount of time over
posting a patch then waiting a few days to see if anyone comments on it.

Obviously if the developer has any concerns about the patch they are
applying then posting first is a good idea.

If you have filtering set up for beanutils mails, then I would recommend
that you make sure that filter also picks up commit emails containing
"commons/proper/beanutils" in the subject, so that you don't miss any
commit emails.

I would expect that when we roll a release candidate for beanutils we
would run the struts unit tests using that beanutils RC jar to see if
any problems occur. And likewise for digester. And for any other
significant beanutils-using projects if someone tells me about them.
Hopefully we will get a struts developer or two to join the beanutils
maintenance (I've posted on dev@struts.apache.org), in which case that
person could run beanutils HEAD during their struts development to pick
up any problems.

But I'm open to arguments on this...

Regards,

Simon

-- 
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?

On Thu, 2005-05-26 at 03:08 +0100, Niall Pemberton wrote:
> I would like to help, but I'm not sure how much time I can realistically
> spare. I will at least try to give feedback. When I started committing on
> beanutils it was suggested by other committers that the best approach was to
> attach patches to bugzilla for review first - given that changes to
> beanutils have a widespread impact on other projects. Are you planning to
> adopt this approach?
> 
> Niall
> 
> ----- Original Message ----- 
> From: "Simon Kitching" <skitching@apache.org>
> Sent: Thursday, May 26, 2005 2:08 AM
> 
> 
> > Hi All,
> >
> > BeanUtils currently has 88 bugzilla entries. And there doesn't seem to
> > be anyone maintaining the project at the moment.
> >
> > I would like to tackle this backlog, but can't do it alone as
> > (a) it's dull and boring working on code on your own, and
> > (b) it's much safer to have someone around to check the patches
> >
> > I'm not talking about developing new features, just fixing reported
> > problems and getting a maintenance release out.
> >
> > James, a couple of months ago you volunteered to join me in an attack on
> > beanutils' bugzilla backlog. Are you still interested?
> >
> > Can anyone else spare some time for this fairly important commons
> > library?
> >
> > I'll also post to the struts list as that is a heavy user of this
> > package. Anyone know of any other packages that depend heavily on
> > beanutils and therefore have an interest in maintaining it?
> >
> > Regards,
> >
> > Simon



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message