Beta 2 expiring, Beta 3 watermarks, the world is ending!

Today I’m getting a nice bit of evidence in the difficulty of having a long-running public beta. Turns out there’s a lot of folks who did not upgrade from beta 2 to beta 3 even though beta 3 came out well over a month ago and Flex Builder indicates that it’s going to expire (ETA: looks like maybe we have a bug here since numerous folks are saying they had 44 days left according to FB. We’re investigating). This expiration date is hard-coded, there’s no way to extend it because guess what… we really want you to move to the new beta because feedback on an old beta is pretty useless to us.

OK, fair enough, but what if you were using the charting and ADG and were doing more than experimenting? You purchased Flex Builder 2 and Charting to make sure you had no watermarks, and now beta 3 is showing them and your FB2 serial doesn’t work. Yes, this was an unfortunate side-effect of our scheduling where we had to implement a new serialization scheme. This was originally supposed to happen after our last public beta so that we wouldn’t run into this, but then life happened and we had to put it in earlier. If you have a valid use-case for removing the watermark you can mail me (mchotin at you can guess where.com) and I can get you a serial that will get you through beta 3.

Sorry for the inconvenience! Despite the fact that this is clearly beta software, it’s pretty interesting to see how many folks are already doing production-worthy things with it.

3 Responses to Beta 2 expiring, Beta 3 watermarks, the world is ending!

  1. Tony says:

    Thank you!!! You saved my bacon!!I have been working on a Flex project for 6 months (should be signing off this week) which had to be ported into Flex 3 beta 3 to get around some unresolvable bugs in the Flex 2 framework.Removing the watermarks would be a real life saver 🙂

  2. Jean-Christophe TURIN says:

    And what if we have a demo built in Flex beta2 and that we don’t want to move yet on beta3 because of current demonstration of our next product to investissors? How can we fix eventual bug?… Hopefully, we still can change the clock time on windows 😉 (and it’s working – it’s just that it’s annoying..)

  3. creacog says:

    Similar to Tony – Though I have upgraded to Flex 3 beta 3 and I’m working with AIR beta 3. Since December’s updates my app is broken due to the changes to DragManager. I’m eagerly awaiting the next version (but it looks like there won’t be a B4?) as you already have a fix internally. [my app is written to primarily use the Flex DragManager – no native drag and drop required as yet]your bug ref: SDK-13983I can’t easily regress to beta 2 due to the AIR installer changes.