commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Gregory <garydgreg...@gmail.com>
Subject Re: [maven build] Jira report?
Date Wed, 23 Oct 2013 17:15:39 GMT
One of the problems I have is that we do not solve is the following story
well, and it is not a particular problem of Commons or the ASF: I want to
update from [foo] version 2 to the current version 5. How do I know what's
changed and what I need to do to migrate/upgrade?

The first thing I do is look at the Release Notes (RN). Sometimes we have
the RN cover ONLY the current version (bad). Sometimes the RN cover all
versions (good) with the newest at the top.

The last thing I want to do is start navigating JIRA and click around for
an hour in different versions, reports, filters and so on. Worse (and I've
had to do this with some software), is that I have to download all versions
and check their release notes.

If I have no good release notes to work with, I have the changes report and
the JIRA report. The JIRA report is automatically generated, which is good.
The changes report depends on the diligence of the developers having kept
up to date the data. Humans = potential for errors; computers = less so ;)

So I am not crazy about removing information for a given component unless
the RN is of the historical nature.

Gary


On Wed, Oct 23, 2013 at 12:58 PM, Henri Yandell <flamefew@gmail.com> wrote:

> On Tue, Oct 22, 2013 at 12:04 PM, Benedikt Ritter <britter@apache.org
> >wrote:
>
> > 2013/10/22 sebb <sebbaz@gmail.com>
> >
> > > On 22 October 2013 19:40, Henri Yandell <flamefew@gmail.com> wrote:
> > > > Anyone know what the point of the JIRA report is?
> > > >
> > > > It seems to be much like the changes report, but with less active
> > > > authorship and a confusing inclusion of resolved issues for different
> > > > versions.
> > > >
> > > > I'm wondering why we include it.
> > >
> > > The changes report only includes changes for the current version.
> > >
> > > The JIRA report includes changes for multiple versions; provided that
> > > the sort mode is correct - and provided that the JIRA fix versions are
> > > set up correctly - it would be more useful than just the changes
> > > report.
> > >
> >
> > It just duplicates what we have in the release notes. And since the site
> > can change anytime, I'm not giving to much about the reports at all
> (after
> > the release vote). But that's a different issue.
> >
> >
> Agreed on both issues :)
>
> Sebb points out that JIRA report has more info, but given its an out of
> date version of JIRA itself, I'm not seeing why we would want the JIRA
> report (even more so than the others).
>
> Any reason to keep it turned on for Commons?
>
> Hen
>



-- 
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message