On 6/24/10, Per Inge Mathisen wrote:
On Thu, Jun 24, 2010 at 5:40 AM, buginator wrote:
If we start to add features that do require beta testing, what are we
going to do ?
We could do beta testing...
I was hoping for less work, not more, with the upcoming release of the
3.0 beta, doing
On 6/23/10, Per Inge Mathisen wrote:
One thing we should consider backporting to 2.3 is the wavecast code,
which makes visibility a ton faster in trunk than in 2.3.
Though, that doesn't answer the question on what we should do with the
2.3 branch.
If we start to add features that do require
On Thu, Jun 24, 2010 at 5:40 AM, buginator buginato...@gmail.com wrote:
If we start to add features that do require beta testing, what are we
going to do ?
We could do beta testing...
- Per
___
Warzone-dev mailing list
Warzone-dev@gna.org
Currently, I was assuming that 2.3 was feature locked, and we would
only be doing bug fixes.
However, it has been expressed that the branch shouldn't be feature locked.
Do we make a new branch, which would be the current 2.3 base (and name
it something like branch/2.x, delete the current
On Tuesday, 22 June 2010 at 19:57, buginator wrote:
Currently, I was assuming that 2.3 was feature locked, and we would
only be doing bug fixes.
However, it has been expressed that the branch shouldn't be feature locked.
I especially expressed that it shouldn't be bug fix only, since that
