Jump to content

Bertram

Community Newbie
  • Posts

    4
  • Joined

  • Last visited

Posts posted by Bertram

  1. Hey, :)

    Branching in SVN is not fun. When we switch to GIT, we will be able to fix bugs on a release branch and still continue working on the next release concurrently.

    It is true that creating a branch on SVN, especially now you're trying to release, could create other kind of problems.

    I've seen and followed the git mirror since some time now on Github, are there plans to move there as a main repo?

    Btw, if you happen to actually do that, you should avoid pushing the nightly builds there, since it will create a good amount of data overhead on git.

    From experience, big data that isn't required to run the game is usually better in another specific repo, or maybe to stay in SVN.

    Best regards,

  2. Hey there, :)

    congrats in advance for the next release! I've been following the work done and I find it impressive already. :D

    We're really sorry for the time it takes, we're also a bit tired of waiting because we can't push modifications to the game during the meantime! :D


    Now, that's funny. I'm sure you already thought about it, but isn't it possible to simply push to another branch instead of waiting a week or two? Especially on SVN, where conflicts can be harder to deal with AFAIK. Just pointing this out, in case it may help about earning some time and pain here. :)

    Best regards,

    • Like 1
  3. Thanks for your both answers. :)

    I know what you mean i also love to see some naval support for the AI and all the other that keeps getting post-poned but yeah maybe we get some new programmers soon that will help make this game rise even more!...

    Well, I didn't mean to put any pressure here, don't worry. ;) I was just saying that letting those issues be post-poned from one release to another meant they aren't important for the given releases, and thus, shouldn't be part of it, to me. (Officially, at least.)

    Those [PATCH] issues are mostly issues where the patch is not complete and/or needs improvement. So it's not ready for inclusion. It's marked as PATCH as people know they can continue with someone else's work.

    The real problem are those marked with the "review" tag. Those patches are supposed to be ready, but are waiting for approval of some kind (code quality, gameplay aspects, ...). Depending on the complexity or the multitude of opinions, it's sometimes hard to review them. And it's something only team members can work on to get them included. While those PATCH issues can be continued by anyone.

    Thanks for the precision. The fact is there is so much of them that it must be hard to grasp the ones to review for the dev team, or the ones related to their own work, IMHO.

    For the naval support, it's getting better. The code to let the AI plan a path through the water towards the opponent is getting better.

    Cool news. :) I was wondering: How many sub-projects are you guys working on? From what we discussed, there is naval support, SpiderMonkey upgrade, and the new AI, but what are the other current point of focus?

    Best regards,

  4. Hi everyone, :)

    First of all, congrats for the awesome work done here. This is truly inspiring.

    Special congrats for the current SpiderMonkey upgrade and the new Petra AI. :D

    I've been following this project like a lot of other people I guess, especially looking at commit log on trac, for instance.

    And it's been some times I wanted to ask you something about the milestones there.

    For at least two or three alpha releases now, I keep seeing the ~100 same issues, post-poned from one release to another each time.

    Of course, a few gets solved, a few new appear, a few can't be solved without another one, but overall it's very hard to see what you guys are working on atm.

    Without even speaking about all the [PATCH] issues one can see there that seems to never get to merged into SVN for different reasons.

    I know this is a spare-time projects and all, but I wonder what makes all those issues stay on the latest milestone without anybody doing something for it, or whether they simply should move out of the current milestone so we can see the current development focus, if nobody is going to do so anyway?

    Maybe also are there several parallel milestones, like translation support, and the like?

    Maybe also is there a link I missed?

    Voila. Just wanted to put my two cents in there. ;)

    Best regards,

×
×
  • Create New...