[infinispan-dev] Keeping a healthy changelog

[Dan Berindei]

+1 for updating the JIRA title/description, but to me it's even more
important to get the Git comment right (even if it doesn't match the JIRA
title) - once it's in upstream you can't go back and tweak it.

Cheers
Dan


On Mon, Nov 12, 2012 at 9:22 AM, Sanne Grinovero <sanne at infinispan.org>wrote:

> Thanks!
> @Mircea yes I agree updating this descriptions is good enough, the
> idea of creating a new one is just something people should consider as
> well for the general case: I (for one) can't check all patches and
> expect to be able to track the project changes by reading the
> changelog on JIRA.
>
> Cheers,
> Sanne
>
> On 12 November 2012 09:12, Adrian Nistor <anistor at redhat.com> wrote:
> > I updated ISPN-2471 title and description to match the actual cause of
> > the issue.
> >
> > Cheers
> >
> > On 11/11/2012 04:33 PM, Mircea Markus wrote:
> >> On 10 Nov 2012, at 11:35, Sanne Grinovero wrote:
> >>
> >>> I noticed occasionally some pull requests and JIRAs are resolved
> >>> without updating the true nature of the resolved issues; of course one
> >>> might start thinking to work on one thing which then turns out to be a
> >>> different problem, these things are frequent but as soon as you notice
> >>> the mismatch it would be great to update the JIRA description, or
> >>> create a separate one.
> >> +1. Updating the JIRA description should be enough IMO.
> >>
> >> Cheers,
> >
> > _______________________________________________
> > infinispan-dev mailing list
> > infinispan-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/infinispan-dev
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20121112/618f951f/attachment.html