-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
bugs buggy wrote:
This is just a heads up for everyone, stating, if you have anymore
changes (aka fixes) that needs to be in 2.2, speak up now, or wait for
2.2.x.
Updated de.po expected by Wednesday
-BEGIN PGP SIGNATURE-
Version: GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
bugs buggy wrote:
For those of you that have missed it, I am currently changing (some)
ASSERT()s to ASSERT_OR_RETURN() to prevent crashes and / or garbage
output in release builds.
Of course, the change only happens if the condition in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Per Inge Mathisen wrote:
However, you need, obviously, an sf.net account to do so. If you lack
one, contact me or gerard_ for the time being.
I'd like to have commit access on SF.net as well.
https://sourceforge.net/users/kreuvf
-BEGIN PGP
all :D
- - Kreuvf
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFKBouG4y86f1GXLDwRAgKdAKCXGLxa9StIuD9N8lbb9jPsXDGi3wCghqSx
DduJT23wZSBWPWMlfTeWXrg=
=3VL9
-END PGP SIGNATURE
in support
cybersphinx neutral
Buggy, stiv against
And while all that talking was going on, one could have created a hundred
builds...
After all team communication and coordination is essential.
- - Kreuvf
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
bugs buggy wrote:
On 5/8/09, Kreuvf kre...@warzone2100.de wrote:
bugs buggy wrote:
2.2 has been 'cooking' for a extremely long period of time.
Pushing beta builds to a lackluster community response, and, what is
worse is, people are still
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Zarel wrote:
2009/5/9 Kreuvf kre...@warzone2100.de:
Just in case this scheme is a proposal: This reminds me of New File (1),
New
File (2) etc. which is why I suggest adding the date to the file-name such
as
cutscenes-2009-05-09.wz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
bugs buggy wrote:
2.2 has been 'cooking' for a extremely long period of time.
Pushing beta builds to a lackluster community response, and, what is
worse is, people are still creating new content for 2.1, which won't
work with 2.2.
Has there ever
to be expected IMHO.
- - Kreuvf
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJ/y9n4y86f1GXLDwRAlxvAKDMSD6r5FmKmM15FgygI+kIuQCqdQCgjQnA
eO9npcFVM3BEQDhec6wDEX0=
=WgSf
-END PGP SIGNATURE
;)
- - Kreuvf
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJ9ds14y86f1GXLDwRAiIuAKC9yaHzDdv+c+KyJG9j0cdN2N41VQCgyOMi
kAY+rdK2suc0sJTfc9AzdsE=
=Nqha
-END PGP SIGNATURE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
bugs buggy wrote:
We are short of active developers, and we could use more help.
It is a huge PITA for the release maintainer to handle all that needs
to be done themselves, and then nobody wants to be the release
maintainer, since it is a ton
the commit-mails?
- - Kreuvf
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJ2IQs4y86f1GXLDwRAnxPAJ4t2IXKjscy+KL1AafZg2ztCiYOagCgyQj8
uxNulI9SsiNJwqmdMAAaVr4=
=Ttot
-END PGP SIGNATURE
it be possible to publish something like an
original_videos.wz mod that everybody could apply to every version instead of
including the videos in the windows installer every time? I am pretty sure I saw
such a .wz file once on gna ;)
- - Kreuvf
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dennis Schridde wrote:
Am Sonntag, 5. April 2009 12:13:05 schrieb Kreuvf:
What about the commit-mails?
SF can send them to Gna lists.
And will the structure of that mails be the same as before (on Gna.org SVN)?
-BEGIN PGP SIGNATURE
, if that is necessary, the decision should be clear, shouldn't it?
Therefore we need to decide if we want to allow this or not, - and if so what
is the best way to map Cairo to Lua. I am sure Elio has some comments/ideas.
Keep it as simple as possible.
- - Kreuvf
-BEGIN PGP SIGNATURE-
Version
Warzone 2100 is played
fundamentally, so I think there is room for much discussion. :)
- - Kreuvf
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJz+I94y86f1GXLDwRAgBFAJ9kaimx6x9ZrMRjc8wdpZEZRYd+OwCfWqOn
) you have some hash-like strings as revision and you probably
cannot derive from such a string if it belongs to an earlier or a later version
of the game. Correct me, if I am wrong.
- - Kreuvf
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http
specifing
a new port),
Do we stick with the format above, and just make it 2.2?
I'd say: Yes. I doubt there were any real problems with it.
Anyone think of anything else that needs changing before we kick out
the alpha (or beta)?
Is the Changelog up-to-date?
- - Kreuvf
-BEGIN PGP
as well) is to not use the
fix for netplay (aka the unfixed netcode), if 2.1.3 or no version is detected.
Dirty: Yes.
Convenient for the users: Yes.
Convenient for distributors: Yes.
Going to a stable 2.2 ASAP could help with overcoming this mess.
P.S.: Everything's IMHO ;)
- - Kreuvf
-BEGIN
no problem for me to contact him.
And afaik he has not that much experience using version control systems and is
not used to the common way of doing things. I am quite sure that he will happily
add the missing information once things have been explained to him.
- - Kreuvf
-BEGIN PGP SIGNATURE
does have time when?
b) Who is next?
c) Who does it, if the regularly scheduled next one does not show any activity?
d) Who does the management?
e) Where is the management done?
There are probably more questions that need to be answered :)
- - Kreuvf
-BEGIN PGP SIGNATURE-
Version: GnuPG
codebase that everyone loves working with.
Although I cannot be of a great help, I appreciate this idea. If things go well,
I'll be there for an interview ;)
- - Kreuvf
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
bugs buggy wrote:
Or perhaps, add a bug report, and have the needed information in that
'bug' report so people know where to go?
Sounds good. Bug with highest priority on top Cannot submit bug-reports to
Gna.
- Kreuvf
___
Warzone-dev mailing list
mediawiki to tracwiki)
Would this be a good way to handle it?
Could be wise to make a more general decision on it as you may want to bundle
several mods as well.
- Kreuvf
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo
Hi there,
I added a section on colours to that proposal. Please have a look and tell me
what you think of this.
http://wiki.wz2100.net/Organization_Proposal#Colour_support
___
Warzone-dev mailing list
Warzone-dev@gna.org
Gerard Krol wrote:
Please check out
http://forums.wz2100.net/viewtopic.php?f=6t=2379p=23075#p23075 and
tell me what you think.
Regards,
Gerard
How is the performance affected?
- Kreuvf
___
Warzone-dev mailing list
Warzone-dev@gna.org
https
bugs buggy wrote:
Would anyone object if I encoded the sound into the video? Or is it
better to leave it as it is now?)
Afaik sound and video were separated with the intention of distributing the same
video material with different sound files (for every language).
The original game came with
match). WZ veterans will find skirmish in SP after having
taken a look into the MP menu ;)
And we will, of course, leave a message in the change log (and we may highlight
this item).
- Kreuvf
___
Warzone-dev mailing list
Warzone-dev@gna.org
https
break anything.
Solutions are welcome.
- Kreuvf
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev
101 - 129 of 129 matches
Mail list logo
