Re: [Fink-devel] [ fink-Package Submissions-3132981 ] freeciv 2.2.4 update

[David L. <doc...@ea...>]

On 14 Dec, 2010, at 11:37 AM, SourceForge.net wrote:

> ----------------------------------------------------------------------
> 
>> Comment By: Hanspeter Niederstrasser (nieder)
> Date: 2010-12-14 13:37
> 
> Message:
> Moving to stable normally requires that there be positive feedback from
> users (mostly to guarantee that it works on more than just the maintainer's
> computer).  So far, the 2.2.x series has worked for me.
> 
> Once 2.3 comes out, it'll probably be OK to move 2.2.last to stable to
> make room for 2.3, especially if you've heard from others saying that
> 2.2.last also works for them.  You don't need to open a new tracker item
> for this.  Just post a note to either fink-users or fink-devel asking to
> have 2.2.last to be moved to stable because it seems, well, stable.
> 
> ----------------------------------------------------------------------
> 
> Comment By: David Lowe (doctorjlowe)
> Date: 2010-12-09 07:00
> 
> Message:
> This contains several small bugfixes and a security patch, and is probably
> the last of the 2.2.x series, as 2.3.0 is expected to be released next
> week.  Should i hold back on 2.3.0 until 2.2.4 can be moved to stable, and
> if so how long is a reasonable amount of time to wait?

	I'm guestimating that i should have a 2.3.0 info file Monday-ish.  I would like to recommend that freeciv-2.2.4-9 be moved to stable at that time.  However, upstream has decided to make my life more 'interesting'.  Specifically: some time after the impending 2.3.0 release, they now plan to do a 2.2.5 bugfix release.  I see no point in replacing the 2.3.0 info file with a 2.2.5 info file, so 2.2.5 will never be able to be tested by the masses.  Do i just ignore the 2.2.5 update, or is there another approach i can use for this?

Sent from my MacBookPro

"He was only 14 and he was burned out on marijuana." - Nancy Reagan