Feature freeze request

Quoting myself from the previous freeze:

Given the imminent arrival of Kamael, it’s necessary to request a feature freeze from you guys. This essentially means:

  • No new feature/major change gets in until we branch Interlude into a tag release. (stuff like an skills engine rewrite should be a nono, for example). We’d essentially look towards leaving the Interlude Core and Datapack as stable as possible.
  • Missing SQL stuff would be ok if they’re not going to require major testing, but you’d better please hurry up/keep commits to a minimum on this. (a missing drop or buylist would be ok, but not Julian’s new spawnlist system f.e.)
  • Bugfixes are generally fine.
  • Hopefully in the forthcoming days we’ll be able to tag Interlude and put Kamael contents into the trunk in order to continue moving on. We just need to wait for core’s latest tests and cleanup. Luckily the changes needed from our side are not major this time.

    As an end note for the impressive amount of work we’ve put into the release of the Interlude core and datapack, I sincerely want to thank and congratulate each and everyone of you that in a way or another, to a minor or greater extent, helped to take our product up to where it has arrived so far. Let’s keep up the good work.

    Share and Enjoy:
    • Digg
    • del.icio.us
    • Facebook
    • Google Bookmarks
    • LinkedIn
    • Meneame
    • Reddit
    • StumbleUpon

    Post a Comment

    You can use these XHTML tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>