Am Dienstag, 16. September 2008 04:54:36 schrieb bugs buggy:
> On 9/15/08, Dennis Schridde <[EMAIL PROTECTED]> wrote:
> > Am Monday 15 September 2008 21:17:24 schrieben Sie:
> > > On 9/15/08, Dennis Schridde <[EMAIL PROTECTED]> wrote:
> > Aren't there any Mac gamers forums/mailinglist/newsgroups anywhere?
> > Mac gaming news sites? ModDB? GameDev? ...
> > Maybe we can draw testers from one of those locations?
>
> I am sure there are, just nobody I know, knows about them...
> We got a few people in the forums, but with the timezone differences, it is
> really, really hard to get everyone in one place to test.
Maybe we can ask those people whether they know good places to ask for more
help? Maybe we can make them test among each other and just report bugs?
Maybe we can even get them to recruit testers for us...
> > When we went to Gna we changed the versioning scheme from 0.x to x.y.z
> > (again: x - major / stunning rewrite release, y - minor / feature
> > release, z -
> > bugfixes). It drifted towards that after the move and I, when I was sole
> > maintainer of the project, officially decided on this.
> > For 2.0 it did not really work exactly like that since we were missing
> > the vcs
> > branching a bit, I think. But for 2.1 (I think "we") decided to have real
> > bugfix only releases. (At least that was my plan.)
> >
> > A future versioning idea I was developing for 3.x was to maybe drop the
> > bugfixing and replace it by betas (as we do currently...) and do just 3.x
> > versions, where x are both smaller new features and bugfixes.
> > Though I think that needs some more thoughts and I dont really want to
> > change
> > everything again in such a short time, especially without finding a
> > proper development model for that. (Would require lots more qa-testing, I
> > think. Maybe Chojun wants to comment on that, since he may have a bit
> > more experience
> > with QA from Warzone 2200.)
> > Basic idea was that this is a game and no kernel or system library, so
> > strict
> > bugfix-only releases may not be as sexy to our users.
> > (And a x.y.z release suggests bugfix releases, imo. At least that is what
> > everyone using that scheme in the FOSS/Linux crowd implies.)
>
> I guess that could work.
So you're pro the x.y scheme as opposed to x.y.z?
We need a proper plan for that though, I think. When to branch, when to fix
bugs, when to integrate features, how to test, when to release, ...
> We already have nightly builds working for trunk (not sure about 2.1, but,
> it would be nice to have those also), so we could release what we have
> available now.
"release" as in final 2.1?
> Then just post that on the front page of the site asking people to test
> those.
> The only problem I see is that we have no way to automate mac builds, so
> they will, once again, be left out of testing, unless we can find a way to
> make nightly builds for them also.
Building Mac builds is only possible on Macs, correct?
That would be an issue. Maybe someone has a spare (or always-on-and-unused-
during-the-night) Mac we could use for that.
In 2 months I could investigate into finding that Mac and setting it up for
nightlies. Cannot guarantee that I will get it and whether it will work
though.
> > Maybe someone wants to do one commit a day less to some random parts, but
> > instead add one line to the ChangeLog per day. That would probably
> > already have fixed the issue entirely, if it was done since the first
> > time I talked about it.
> >
> > If everyone was adding a line to the ChangeLog directly for everything
> > important (and be it unordered), that would of course make it *even*
> > simpler.
> >
> > Per: Care to add this to the development/commit guidelines?
>
> I was thinking, how about adding a changelog entry (or 1 line summary) into
> the svn log, then we can use a bot to parse the logs, and then it can auto
> add it to the changelog by date /time.
Wouldn't that be the same work for everyone as adding one line to a file?
> > ... 2.2 ...
> > Given that it is September already, I think early 2009 sounds like a good
> > candidate. And yes, I think a delay of half a year is not really
> > acceptable...
> > Doing 2-weekly betas 1-2 months before the target release date sounds
> > like something good. (No matter of the actual state of the game, skipped
> > just by *very major* blockers.)
>
> It actually can be quicker than that, since, as I said, we already got
> nightly builds... just got to figure out how to handle this for macs.
Quicker than early 2009? I do not see the final 2.1 release before Oktober,
but rather later. Several things need integration, improvement, fixes.
(widgets, projectiles, netcode, pathfinding, ...) I simply do not see how that
work shall get done in less than 3 months...
Especially with an activity like currently.
--Devu
signature.asc
Description: This is a digitally signed message part.
___
Warzone-dev mailing list
Warzone-dev@gna.
