rails-devel

[Rails-devel] Preparing new release: Version number?

[Stefan F. <ste...@we...>]

Erik,
are all bug reports for 1835 fixed by now?
I would like to put out a new release tonight or tomorrow morning and if
1835 is ready, it would be version 1.6.0. Otherwise it will be 1.5.4.
Stefan

Re: [Rails-devel] Preparing new release: Version number?

[Erik V. <eri...@xs...>]

Stefan,

No, I'm not ready yet.  The issue with offering impossible special tile lays
is still open. 
(I wouldn't call such an issue a bug myself; IMO, bugs are failures and
limitations that inhibit correct play. Here we have a case of incorrect
play, that isn't even allowed, just suggested, but even if it would be
allowed I'd still consider it a mere flaw rather than a bug, as it can be
avoided. But that aside).

I know what to do, but haven't found the time yet.  
In addition, a scan through old mails and bug reports uncovered a few more
issues with 1835 (mostly raised by JDG as well) that I would like to
consider.
Later this week, I hope.

> if 1835 is ready

Or ready again.  It turns out to be very hard to exactly define "ready". 
I'd say: after I have done the outstanding fixes, it's as ready as I'm aware
of.  But so it was the previous time.
Anyhow, there is little doubt that John David Galt and another excellent
testers will keep finding bugs and flaws, until eternity, or the lifetime of
Rails, whichever comes first.

Erik.
 

Re: [Rails-devel] Preparing new release: Version number?

[Stefan F. <ste...@we...>]

Erik,
would you still agree that a 1.5.4 is possible to allow testing the fixed 
issues and close the background map error or would you prefer to wait a few 
more days to have all released in one go?
If there is developing going on I would like to keep releases in regular 
intervals, this keeps the other contributors in the loop.
Stefan

On Sunday, November 27, 2011 09:47:58 pm Erik Vos wrote:
> Stefan,
> 
> No, I'm not ready yet.  The issue with offering impossible special tile
> lays is still open.
> (I wouldn't call such an issue a bug myself; IMO, bugs are failures and
> limitations that inhibit correct play. Here we have a case of incorrect
> play, that isn't even allowed, just suggested, but even if it would be
> allowed I'd still consider it a mere flaw rather than a bug, as it can be
> avoided. But that aside).
> 
> I know what to do, but haven't found the time yet.
> In addition, a scan through old mails and bug reports uncovered a few more
> issues with 1835 (mostly raised by JDG as well) that I would like to
> consider.
> Later this week, I hope.
> 
> > if 1835 is ready
> 
> Or ready again.  It turns out to be very hard to exactly define "ready".
> I'd say: after I have done the outstanding fixes, it's as ready as I'm
> aware of.  But so it was the previous time.
> Anyhow, there is little doubt that John David Galt and another excellent
> testers will keep finding bugs and flaws, until eternity, or the lifetime
> of Rails, whichever comes first.
> 
> Erik.
> 
> 
> 
> ---------------------------------------------------------------------------
> --- All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel

Re: [Rails-devel] Preparing new release: Version number?

[Erik V. <eri...@xs...>]

I surely have no problem with a new release now.  
Erik

> -----Original Message-----
> From: Stefan Frey [mailto:ste...@we...]
> Sent: Sunday, November 27, 2011 10:01 PM
> To: Development list for Rails: an 18xx game
> Subject: Re: [Rails-devel] Preparing new release: Version number?
> 
> Erik,
> would you still agree that a 1.5.4 is possible to allow testing the fixed
issues
> and close the background map error or would you prefer to wait a few more
> days to have all released in one go?
> If there is developing going on I would like to keep releases in regular
> intervals, this keeps the other contributors in the loop.
> Stefan
> 
> On Sunday, November 27, 2011 09:47:58 pm Erik Vos wrote:
> > Stefan,
> >
> > No, I'm not ready yet.  The issue with offering impossible special
> > tile lays is still open.
> > (I wouldn't call such an issue a bug myself; IMO, bugs are failures
> > and limitations that inhibit correct play. Here we have a case of
> > incorrect play, that isn't even allowed, just suggested, but even if
> > it would be allowed I'd still consider it a mere flaw rather than a
> > bug, as it can be avoided. But that aside).
> >
> > I know what to do, but haven't found the time yet.
> > In addition, a scan through old mails and bug reports uncovered a few
> > more issues with 1835 (mostly raised by JDG as well) that I would like
> > to consider.
> > Later this week, I hope.
> >
> > > if 1835 is ready
> >
> > Or ready again.  It turns out to be very hard to exactly define "ready".
> > I'd say: after I have done the outstanding fixes, it's as ready as I'm
> > aware of.  But so it was the previous time.
> > Anyhow, there is little doubt that John David Galt and another
> > excellent testers will keep finding bugs and flaws, until eternity, or
> > the lifetime of Rails, whichever comes first.
> >
> > Erik.
> >
> >
> >
> > ----------------------------------------------------------------------
> > -----
> > --- All the data continuously generated in your IT infrastructure
> > contains a definitive record of customers, application performance,
> > security threats, fraudulent activity, and more. Splunk takes this
> > data and makes sense of it. IT sense. And common sense.
> > http://p.sf.net/sfu/splunk-novd2d
> > _______________________________________________
> > Rails-devel mailing list
> > Rai...@li...
> > https://lists.sourceforge.net/lists/listinfo/rails-devel
> 
>
----------------------------------------------------------------------------
--
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security threats,
> fraudulent activity, and more. Splunk takes this data and makes sense of
it. IT
> sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel