DEVONthink 2.0 spotlight: Beta tester community seeded

I promised to keep you all updated on the progress we make with DEVONthink 2.0. Today I am proud to tell you that we have just seeded the very first beta of DEVONthink Pro Office 2.0 to the closed beta testers group. Some features are still missing, especially interface-wise, but it’s already stable enough and useable. And while we continue adding the planned functionality it’s now up to our great beta tester community to put it through its paces.

16 Responses to “DEVONthink 2.0 spotlight: Beta tester community seeded”

  1. physicistjedi says:

    How can we get in the beta team? I am a long time DTP user and looking forward to 2.0.

  2. pemmax says:

    Eric can you add me to this beta team? Please 😉

  3. Ced says:

    Oh please, please, let me in !

  4. Ted Pearlman says:

    Eric, if you don’t make me a beta tester right now, I’m going to pour jello on my head.

  5. Jorge says:

    I would like to join to the beta team. I’m planning to write a review about the new version on my blog! Thanks!

  6. Doug says:

    I’ll give it a go. I seem to be testing a good deal of software later. I find 1.5.x indispensable. No else like on Mac or PC.

  7. Eric says:

    For the moment, we have closed the beta group as everyine is already testing intensively and we’re barely managing the feedback stream. But there will be a public beta period later this year that will also give you access to more functions that have not yet been implemented.

  8. Alex says:

    Can you post some photos of the new interface ‘enhancements’ – PLEASE !

    ( Or just release some teaser screen grabs for us out of the loop users anxiously awaiting version two for months upon months, upon months… )

  9. JRPars says:

    Terrific news! And Eric, under no circumstances should you ever even think about putting me on the beta team. I would absolutely refuse any invitation to contribute my extensive expertise, superior sensibilities, and genuine genius to such an endeavor. I am, however, anxiously awaiting arrival.

  10. David says:

    With the interest shown towards Version 2 is there any indication as to how long the Beta testing will take and then the final corrections before the release please?

    David

  11. Josh in California says:

    Excellent! I’ve been dying to see what DT 2.0 is like.

  12. Eric says:

    @David: No, it all depends on how many issues we find and how much time we can spend on adding what we want to add before we enter the public beta phase.

  13. Ryuji Suzuki says:

    > Eric #12

    You previously firmly promised that the version 2 would be released in 2008. You didn’t say exact date in 2008, but you said 2008. Is this still honored? I hope so.

  14. Eric says:

    @Ryuji: Our plans have not changed even though with every found bug it’s getting harder. It may mean that we need to cut features from the public beta which definitely will come in 2008. However, found bugs mean a more stable application.

  15. Ryuji Suzuki says:

    Thanks. You previously promised that the production version 2.0 would come out in 2008, so this already sounds like slipping behind. I’d strongly prefer to have DT2.0 with somewhat reduced feature set now and look forward to see the extra features in 2.1. I’m teaching a class on various aspects/applications of digital document management, and if DT2.0 won’t come in time, or if I don’t have enough time to familiarize myself with DT2.0, I have no other option than use other softwares.

  16. Eric says:

    @Ryuji: We could publish 2.0 today but it would not be good. We’re standing for quality software and so we’re ironing out the bugs *before* we release a software. Version 2.0 will be available to the public in 2008 but it may have the “public beta” label because it does not contain all *promised* features. But it will be stable and reliable or we would not release it to the public.

Leave a Reply

Note: Blog comments are for commenting on a post. They are unsuitable for proper customer support, honestly. Please consider writing to our support team instead.