Duncan Findlay wrote:
Any chance we can rescore for 3.0.4 release?
I'm -1 on this. We are close enough to 3.1 that that would be a pointless waste
of time.
I'm also (nonbinding) -1 on releasing 3.0.4. Our plan was to focus on
getting 3.1 out the door. We eventually decide to get 3.0.3 out the
door because distros were asking for it (me included). Now that we're
done with that, we really don't need another one. These bugs are
relatively minor.
Dan was ready to prepare a pre-release for 3.1.0 (until people started
checking tons of code in anticipation...) We are close to 3.1.0. We
don't need this distraction. Also, if we lasted so long between 3.0.2
and 3.0.3, it doesn't make sense to me why we are releasing 3.0.4 so
soon after, given that no bugs were introduced by 3.0.3. All this
enthusiasm for the 3.0.x branch seems misplaced. :-)
On the other hand 3.0.4 seems to be *done*. How many bugs fixed now?
Why not release?
Would collection of data necessary to rescore 3.0.4 help in the
rescoring of 3.1 too, or is 3.1 too far off at this point?
No, it would not help. And it would probably take most of a
month. (Although 3.1 scoring shouldn't take as long!?)
Eh? It sounds like *both* 3.0.4 and 3.1.0 are nearly done in code by
your description. And when I asked earlier about rescoring, the answer
was that collecting the data is the hard part, and number crunching on
that data is relatively easy. So it would take relatively little
additional effort to recompute scores for both versions. And why would
it take less time to compute 3.1.0 than 3.0.4?
Warren Togami
[EMAIL PROTECTED]
