vBulletin 2.0 Development Team

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • James
    Senior Member
    • Apr 2000
    • 450

    vBulletin 2.0 Development Team

    Hello,

    We recently hired four of the most technically savvy community members to contribute to vBulletin 2.0 coding in order to speed up development. The new programming team now consists of Freddie Bingham, James Frasch, Chris Lambert and Ed Sullivan. John will continue to develop the core code of vBulletin 2.0, but many of the new features and bug fixes will be passed over to the development team for completion.

    Hopefully, having five people working on the product instead of one will speed up development greatly - for those of you who have kept an eye on the vBulletin 2.0 demo site, it'll be clear that a lot has been accomplished over the last few weeks by John alone, but there is still quite a lot of work that needs to be done in order to get the product up to a standard which we would be happy to release into the members area.

    At the moment I'd rather not commit to a release date for version 2.0 until John and the coding team have been working together for a few days. Hopefully once the wheels of the development team are turning smoothly, we'll be able to make an accurate "guesstimate" as to a possible time scale for release. However, it's important to realise that the old "it'll be done when It's done" motto still applies - and we'd rather spend a little more time to develop a perfect product than rush out a version that is packed with bugs and lacks some principal features.

    On the other side of the coin, I know that this version has been a long time in coming, and all our collective efforts are now involved with completing the coding of a first-rate product as soon as humanly possible.

    Note: Please discuss this announcement in this thread.

    All the best,

    James

    [Edited by James on 12-16-2000 at 12:37 PM]
    James Limm
widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...