lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: Changes Mess
Date Mon, 06 Dec 2010 16:20:49 GMT
Hi Robert,

On Dec 6, 2010, at 7:11 AM, Robert Muir wrote:

> 
> So I don't know how jira would handle this case? because we merged
> contrib/snowball with contrib/analyzers in 3.1 i would have to create
> a separate jira issue just so that 3.1 has the correct
> description/path name in its release notes? and in 4.0 i'd have to
> create a third duplicate JIRA issue because we merged all the
> analyzers, so there it needs to refer to modules/analysis?

Yeah in the end all I can say is that you basically get out of JIRA what you put into it.
What you call extra work is just something that I would do anyways working on some of my projects.
I'm not saying it's *not difficult* and super easy, but we've just decided in those cases
to invest time into the issue management system so that we can get the reports we want out
of it.

I've seen this work both ways: in the early days of Nutch there were intense debates on simply
moving everything to JIRA versus maintaining a disconnected CHANGES.txt file. I've heard all
the arguments (many times over) on both sides including tidbits like "oh I don't want to go
to a separate URL as a consumer of software just to see what changed in it" to "what's so
hard about doing a curl or wget on an Internet-connected system which most of our software
assumes nowadays"?, those types of things. 

When the dust cleared, I think I like the approach we use in Tika (and that I use in a number
of projects at JPL) which is just to maintain the information in JIRA. It's worked for us
since it's a single source to curate that type of information; it produces very useable reports
(not perfect, but useable) that are good enough for us in terms of trading between the different
properties we want to maximize (user contribution acknowledgement, change history, etc.)

Cheers,
Chris


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


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


Mime
View raw message