Re: [Warzone-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[7027] trunk/data/mp/stats
2009/4/20 Per Inge Mathisen :
> ... and discuss the bigger changes on the forum prior to making them ;-)
Yeah, yeah.
> I would still *prefer* to get a detailed changelog each time, and I
> also think it would be better for you, since that makes it much easier
> to playtest the new changes instead of going about it merely by
> guesswork.
The current changelogs are detailed enough to point to what needs playtesting.
2009/4/20 bugs buggy :
> Are you saying you commit the changes first, then write your changelog
> at your site?
Hmm. Apparently, I've been committing with a summarized changelog from
my site. I guess I'll use the full changelog now.
> If not, a simple copy & paste from that would be good enough for the most
> part.
> I rather see a '+' | '-' table generated, so at a quick glance, we can
> all tell if you nerfed something, or made something stronger.
>
> The main point is, when you say something like "VTOLs partially fixed.
> " and don't go into details on the how & why, it gets a bit confusing
> to those that don't live in CSV hell ;), and they must do a diff to
> see what you have done.
Other than "VTOLs fixed" and "cyborgs fixed" every once in a while, I
generally indicate which direction ("Heavy cyborgs are slightly
lighter. Should be able to move now."). In those cases, it's because
it's a bunch of minor tweaks in both directions: Some are slightly
weaker, some are slightly stronger - saying which one's which takes
_way_ too much time. The diff generated automatically by Trac should
be enough, I think.
-Zarel
___
Warzone-dev mailing list
Warzone-dev@gna.org
https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Source code formatting
On 4/17/09, Gerard Krol wrote: > bugs buggy wrote: > > I think we should start converting the source code, on a file by file > > basis, starting with the libs, and working our way to src. > > > > You have ANY idea how badly this will mess up all branches? Please > please don't > > - Gerard I don't think it would mess them up that much, since those libs haven't really been touched in a very long time, but I don't want to cause any friction / distractions either. That means, this will be put on indefinite hold. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[7027] trunk/data/mp/stats
On 4/20/09, Zarel wrote: > 2009/4/19 Giel van Schijndel : > > > Please include the full changelog in your commit message. There's no > > size limit on it... I don't like dependencies like this on external > > sources. > > > This isn't the first time this has come up. Let's agree on a solution > right here and now, so we don't have to go through this every time I > commit Rebalance. > > Per and I agreed on this solution: considering I change everything so > many times, it's simpler to just provide a full changelog from 2.1 > when Rebalance is finished. Otherwise, it's too much information. I > change minor values once, then change them back when they don't work, > etc, etc. > > I will name every single change I made when Rebalance is finished. > Doing it each commit simply requires more time than even making the > changes and playtesting them over and over. The summary of major > changes and the website with detailed changes is enough. It won't go > down before my full changelog when Rebalance is finished, anyway. And > the data is separate enough that we can revert all of it while leaving > the rest of the code untouched. > > Everyone agree? > Are you saying you commit the changes first, then write your changelog at your site? If not, a simple copy & paste from that would be good enough for the most part. I rather see a '+' | '-' table generated, so at a quick glance, we can all tell if you nerfed something, or made something stronger. The main point is, when you say something like "VTOLs partially fixed. " and don't go into details on the how & why, it gets a bit confusing to those that don't live in CSV hell ;), and they must do a diff to see what you have done. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[7027] trunk/data/mp/stats
On Mon, Apr 20, 2009 at 9:34 AM, Zarel wrote: > This isn't the first time this has come up. Let's agree on a solution > right here and now, so we don't have to go through this every time I > commit Rebalance. > > Per and I agreed on this solution: considering I change everything so > many times, it's simpler to just provide a full changelog from 2.1 > when Rebalance is finished. Otherwise, it's too much information. I > change minor values once, then change them back when they don't work, > etc, etc. ... and discuss the bigger changes on the forum prior to making them ;-) I would still *prefer* to get a detailed changelog each time, and I also think it would be better for you, since that makes it much easier to playtest the new changes instead of going about it merely by guesswork. - Per ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] [Warzone2100-commits] SF.net SVN: warzone2100:[7027] trunk/data/mp/stats
2009/4/19 Giel van Schijndel : > Please include the full changelog in your commit message. There's no > size limit on it... I don't like dependencies like this on external > sources. This isn't the first time this has come up. Let's agree on a solution right here and now, so we don't have to go through this every time I commit Rebalance. Per and I agreed on this solution: considering I change everything so many times, it's simpler to just provide a full changelog from 2.1 when Rebalance is finished. Otherwise, it's too much information. I change minor values once, then change them back when they don't work, etc, etc. I will name every single change I made when Rebalance is finished. Doing it each commit simply requires more time than even making the changes and playtesting them over and over. The summary of major changes and the website with detailed changes is enough. It won't go down before my full changelog when Rebalance is finished, anyway. And the data is separate enough that we can revert all of it while leaving the rest of the code untouched. Everyone agree? - Zarel ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
