feedback about last release

[cybersphinx]

My point was that a heated discussion is not likely to start in a forum section dedicated to it, but wherever some issue comes up. If it disturbs the original thread, it can then be dealt with (e.g. by splitting it off), I don't see the need for a special forum section.

[NoQ]

My point was that a heated discussion is moved to the forum section seen only by the participants of (any) heated discussion. Anyway, never mind, i'm just curious about this sort of things in general.

[Iluvalar]

To say this is annoying, is a understatement.

One more time, since some people can't understand what is going on.
The version that we just released was feature locked for the most part.
We didn't want to mess with a stable release on unproven things.
We don't have enough people to fix all the bugs we would like to fix.

Got it ?

You don't have enough people to fix all the bugs we would need to fix.
And there are reasons for that.

One of you ask "make a ticket do the patch". The other stumble 8 hour later, complain and close the ticket : http://developer.wz2100.net/ticket/2925#comment:1%29:

WTF ! And you ask why there is no tickets for the bugs yet ?

Btw, how can an open source project come to become "locked" ? I know, you'd like the master to triumph over the puny 2.3 branch. But that should not happen by making obstruction to the 2.3 developments and bug fixes. It will happen naturally when master will really have some interesting features.

[lav_coyote25]

To say this is annoying, is a understatement.

One more time, since some people can't understand what is going on.
The version that we just released was feature locked for the most part.
We didn't want to mess with a stable release on unproven things.
We don't have enough people to fix all the bugs we would like to fix.

Got it ?

You don't have enough people to fix all the bugs we would need to fix.
And there are reasons for that.

One of you ask "make a ticket do the patch". The other stumble 8 hour later, complain and close the ticket : http://developer.wz2100.net/ticket/2925#comment:1%29:

WTF ! And you ask why there is no tickets for the bugs yet ?

Btw, how can an open source project come to become "locked" ? I know, you'd like the master to triumph over the puny 2.3 branch. But that should not happen by making obstruction to the 2.3 developments and bug fixes. It will happen naturally when master will really have some interesting features.

well, you know how to fix all the problems. what is the hold up?? as being locked - possibly might be, but if there is no one to do said project because all the developing is on some OLD branch - why should anyone bother. just an observation.

[MaNGusT]

If you want to change warzone code use the proper methods, tickets for bugs and patches of code updates to help the dev team along less destructive attitudes would be good.

You did nice updates to wzgm (i.e. animation improvements), but you didn't create tickets and patches to include it all into wz... so I suppose you don't want to help the dev team improve the wz?

[Berg]

You Jest?

[Safety0ff]

The disappearing unicode lobby chat text #2896 was not fixed

That one might have fallen off our radar and forgotten, it definitely looks like a legitimate criticism/feedback about the release.

but you didn't create tickets and patches to include it all into wz...

Everything that went into wzgm can be found here: http://wzgraphicmods.svn.sourceforge.ne ... aphicmods/
Not everything that went into wzgm is ready or should be integrated with wz, the coding philosophy was also significantly different.

so I suppose you don't want to help the dev team improve the wz?

You know what they say about people who assume.

[MaNGusT]

You Jest?

no
you could finish some of your code, at least a small part of it.

[Berg]

If you want to change warzone code use the proper methods, tickets for bugs and patches of code updates to help the dev team along less destructive attitudes would be good.

You did nice updates to wzgm (i.e. animation improvements), but you didn't create tickets and patches to include it all into wz... so I suppose you don't want to help the dev team improve the wz?

Berg wrote:You Jest?

no

If you care to look I have submitted a good many things to Warzone dev.

You assume because you don't see what happens that nothing has been done...Maybe I should Brag more..but then I would be like you and thats not a good thing...

You Provoke flaming Mangust and thats not a good thing either.

[MaNGusT]

You assume because you don't see what happens that nothing has been done...Maybe I should Brag more..but then I would be like you and thats not a good thing...

I just thought that you stopped with your help to devs, haven't seen credits to you a long time. Also, I don't remember where I bragged(may be just a little ) but never mind.

ok, let's back to the topic.
2.3.* is feature locked now, but is it opened to bug fixes and balance changes? if so, let Iluvalar prepare a good patch with patch notes. He's also a manpower, Why do you deny his help? oh, he didn't prepare a good patch...

[vexed]

You don't have enough people to fix all the bugs we would need to fix.
And there are reasons for that.

One of you ask "make a ticket do the patch". The other stumble 8 hour later, complain and close the ticket : http://developer.wz2100.net/ticket/2925#comment:1%29:

The ticket was closed, since it already is in the code, as I wrote in that ticket.
As for knowing it was requested, my crystal ball is broken.

WTF ! And you ask why there is no tickets for the bugs yet ?

That isn't a bug, that was a design choice. Again, that was fixed already in master, and, again, it was already fixed for another version.

Btw, how can an open source project come to become "locked" ? I know, you'd like the master to triumph over the puny 2.3 branch. But that should not happen by making obstruction to the 2.3 developments and bug fixes. It will happen naturally when master will really have some interesting features.

Last I looked, we are still accepting bug reports for this release, and that hasn't changed.
Open source projects can't be locked, I have no idea what you are talking about.

You assume because you don't see what happens that nothing has been done...Maybe I should Brag more..but then I would be like you and thats not a good thing...

I just thought that you stopped with your help to devs, haven't seen credits to you a long time. Also, I don't remember where I bragged(may be just a little ) but never mind.

Hmm ? 5839c490b10500c1ff251085ceed9434f2f675aa Looks pretty recent to me...

ok, let's back to the topic.
2.3.* is feature locked now, but is it opened to bug fixes and balance changes? if so, let Iluvalar prepare a good patch with patch notes. He's also a manpower, Why do you deny his help? oh, he didn't prepare a good patch...

2.3 was always feature locked.
Yes, we are accepting bug tickets.