From David.Messina at sbc.su.se  Wed May  4 03:53:23 2011
From: David.Messina at sbc.su.se (Dave Messina)
Date: Wed, 4 May 2011 09:53:23 +0200
Subject: [Bioperl-dev] Changes file
Message-ID: <BANLkTi=LdVRFefeZZ_ZxzEeK1jacx5eLxw@mail.gmail.com>

I noticed Chris has been updating the Changes file a little more regularly
(which is great!).

Should I be adding a line in there to document bug fixes, new code, etc? For
example, the new MSPtools module from Jessen.


Dave

From rmb32 at cornell.edu  Wed May  4 16:12:18 2011
From: rmb32 at cornell.edu (Robert Buels)
Date: Wed, 04 May 2011 13:12:18 -0700
Subject: [Bioperl-dev] Changes file
In-Reply-To: <BANLkTi=LdVRFefeZZ_ZxzEeK1jacx5eLxw@mail.gmail.com>
References: <BANLkTi=LdVRFefeZZ_ZxzEeK1jacx5eLxw@mail.gmail.com>
Message-ID: <4DC1B322.1000709@cornell.edu>

On 05/04/2011 12:53 AM, Dave Messina wrote:
> Should I be adding a line in there to document bug fixes, new code, etc? For
> example, the new MSPtools module from Jessen.

Absolutely!  By all means scribble in Changes!  When in doubt, put it in.

It's a lot easier to prune irrelevant things *out* of Changes before 
releasing, than it is to go through the commit logs at release time and 
try to back-fill it.

Rob

From cjfields at illinois.edu  Wed May  4 16:27:23 2011
From: cjfields at illinois.edu (Chris Fields)
Date: Wed, 4 May 2011 15:27:23 -0500
Subject: [Bioperl-dev] Changes file
In-Reply-To: <4DC1B322.1000709@cornell.edu>
References: <BANLkTi=LdVRFefeZZ_ZxzEeK1jacx5eLxw@mail.gmail.com>
	<4DC1B322.1000709@cornell.edu>
Message-ID: <E22C6A44-B0A0-4679-A64D-4432BB9094A8@illinois.edu>

On May 4, 2011, at 3:12 PM, Robert Buels wrote:

> On 05/04/2011 12:53 AM, Dave Messina wrote:
>> Should I be adding a line in there to document bug fixes, new code, etc? For
>> example, the new MSPtools module from Jessen.
> 
> Absolutely!  By all means scribble in Changes!  When in doubt, put it in.
> 
> It's a lot easier to prune irrelevant things *out* of Changes before releasing, than it is to go through the commit logs at release time and try to back-fill it.
> 
> Rob

Yes, completely agree.  I got so frustrated after adding the bug fixes on this last run I almost gave up (and I'm sure I missed a number of them).

chris




From David.Messina at sbc.su.se  Wed May  4 16:34:05 2011
From: David.Messina at sbc.su.se (Dave Messina)
Date: Wed, 4 May 2011 22:34:05 +0200
Subject: [Bioperl-dev] Changes file
In-Reply-To: <E22C6A44-B0A0-4679-A64D-4432BB9094A8@illinois.edu>
References: <BANLkTi=LdVRFefeZZ_ZxzEeK1jacx5eLxw@mail.gmail.com>
	<4DC1B322.1000709@cornell.edu>
	<E22C6A44-B0A0-4679-A64D-4432BB9094A8@illinois.edu>
Message-ID: <BANLkTimJ5wKPTRjbkx2BBmcy72BCgcu82Q@mail.gmail.com>

Alrighty then!

Let's make a habit of it.

D



On Wed, May 4, 2011 at 22:27, Chris Fields <cjfields at illinois.edu> wrote:

> On May 4, 2011, at 3:12 PM, Robert Buels wrote:
>
> > On 05/04/2011 12:53 AM, Dave Messina wrote:
> >> Should I be adding a line in there to document bug fixes, new code, etc?
> For
> >> example, the new MSPtools module from Jessen.
> >
> > Absolutely!  By all means scribble in Changes!  When in doubt, put it in.
> >
> > It's a lot easier to prune irrelevant things *out* of Changes before
> releasing, than it is to go through the commit logs at release time and try
> to back-fill it.
> >
> > Rob
>
> Yes, completely agree.  I got so frustrated after adding the bug fixes on
> this last run I almost gave up (and I'm sure I missed a number of them).
>
> chris
>
>
>
> _______________________________________________
> bioperl-dev mailing list
> bioperl-dev at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/bioperl-dev
>

From David.Messina at sbc.su.se  Wed May  4 07:53:23 2011
From: David.Messina at sbc.su.se (Dave Messina)
Date: Wed, 4 May 2011 09:53:23 +0200
Subject: [Bioperl-dev] Changes file
Message-ID: <BANLkTi=LdVRFefeZZ_ZxzEeK1jacx5eLxw@mail.gmail.com>

I noticed Chris has been updating the Changes file a little more regularly
(which is great!).

Should I be adding a line in there to document bug fixes, new code, etc? For
example, the new MSPtools module from Jessen.


Dave


From rmb32 at cornell.edu  Wed May  4 20:12:18 2011
From: rmb32 at cornell.edu (Robert Buels)
Date: Wed, 04 May 2011 13:12:18 -0700
Subject: [Bioperl-dev] Changes file
In-Reply-To: <BANLkTi=LdVRFefeZZ_ZxzEeK1jacx5eLxw@mail.gmail.com>
References: <BANLkTi=LdVRFefeZZ_ZxzEeK1jacx5eLxw@mail.gmail.com>
Message-ID: <4DC1B322.1000709@cornell.edu>

On 05/04/2011 12:53 AM, Dave Messina wrote:
> Should I be adding a line in there to document bug fixes, new code, etc? For
> example, the new MSPtools module from Jessen.

Absolutely!  By all means scribble in Changes!  When in doubt, put it in.

It's a lot easier to prune irrelevant things *out* of Changes before 
releasing, than it is to go through the commit logs at release time and 
try to back-fill it.

Rob


From cjfields at illinois.edu  Wed May  4 20:27:23 2011
From: cjfields at illinois.edu (Chris Fields)
Date: Wed, 4 May 2011 15:27:23 -0500
Subject: [Bioperl-dev] Changes file
In-Reply-To: <4DC1B322.1000709@cornell.edu>
References: <BANLkTi=LdVRFefeZZ_ZxzEeK1jacx5eLxw@mail.gmail.com>
	<4DC1B322.1000709@cornell.edu>
Message-ID: <E22C6A44-B0A0-4679-A64D-4432BB9094A8@illinois.edu>

On May 4, 2011, at 3:12 PM, Robert Buels wrote:

> On 05/04/2011 12:53 AM, Dave Messina wrote:
>> Should I be adding a line in there to document bug fixes, new code, etc? For
>> example, the new MSPtools module from Jessen.
> 
> Absolutely!  By all means scribble in Changes!  When in doubt, put it in.
> 
> It's a lot easier to prune irrelevant things *out* of Changes before releasing, than it is to go through the commit logs at release time and try to back-fill it.
> 
> Rob

Yes, completely agree.  I got so frustrated after adding the bug fixes on this last run I almost gave up (and I'm sure I missed a number of them).

chris





From David.Messina at sbc.su.se  Wed May  4 20:34:05 2011
From: David.Messina at sbc.su.se (Dave Messina)
Date: Wed, 4 May 2011 22:34:05 +0200
Subject: [Bioperl-dev] Changes file
In-Reply-To: <E22C6A44-B0A0-4679-A64D-4432BB9094A8@illinois.edu>
References: <BANLkTi=LdVRFefeZZ_ZxzEeK1jacx5eLxw@mail.gmail.com>
	<4DC1B322.1000709@cornell.edu>
	<E22C6A44-B0A0-4679-A64D-4432BB9094A8@illinois.edu>
Message-ID: <BANLkTimJ5wKPTRjbkx2BBmcy72BCgcu82Q@mail.gmail.com>

Alrighty then!

Let's make a habit of it.

D



On Wed, May 4, 2011 at 22:27, Chris Fields <cjfields at illinois.edu> wrote:

> On May 4, 2011, at 3:12 PM, Robert Buels wrote:
>
> > On 05/04/2011 12:53 AM, Dave Messina wrote:
> >> Should I be adding a line in there to document bug fixes, new code, etc?
> For
> >> example, the new MSPtools module from Jessen.
> >
> > Absolutely!  By all means scribble in Changes!  When in doubt, put it in.
> >
> > It's a lot easier to prune irrelevant things *out* of Changes before
> releasing, than it is to go through the commit logs at release time and try
> to back-fill it.
> >
> > Rob
>
> Yes, completely agree.  I got so frustrated after adding the bug fixes on
> this last run I almost gave up (and I'm sure I missed a number of them).
>
> chris
>
>
>
> _______________________________________________
> bioperl-dev mailing list
> bioperl-dev at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/bioperl-dev
>