On Thu, Sep 4, 2014 at 7:11 AM, Simon Steiner <[email protected]> wrote:
> Hi, > > > > I don’t see how finishing the cleanup affects the vote. Im not aware of > what you are currently working on. > Perhaps you are not signed up for the email list that notifies we devs of new commits in SVN? Because if you were, and at least scanning this traffic, then you could not help but be aware. Also, if you look at the svn log on findbug-excludes you will see I have been making many changes recently. Please add yourself to that list if not already added. In any case, please revert your changes so I can complete my work. Perhaps I could have made this work in progress more publicized, but I suppose I have been presuming that other devs monitor new commits. > > > Thanks > > > > *From:* Glenn Adams [mailto:[email protected]] > *Sent:* 04 September 2014 15:00 > *To:* FOP Developers > *Subject:* Re: [VOTE] Enable findbugs > > > > -1 because I'm not ready for this due to still in progress making findbugs > clean up; you should coordinate in the future when you know someone else is > working on a config change of this sort > > > > On Thu, Sep 4, 2014 at 5:48 AM, Simon Steiner <[email protected]> > wrote: > > Hi, > > > > Vote to fail fop on Jenkins if findbugs 2.0.3 finds a warning. The exclude > file has been updated so present warning types are excluded therefore more > controversial warnings are not enabled. > > > > You would at minimum only maintain exclude file. > > > > The vote will run for 7 days until 11 Sept. > > > > Here's my +1 > > > > Thanks > > >
