I am delighted to see Autopano continue to progress!
But, like "phototrek," I agree that being vague is better than being wrong when it comes to promises. I have worked
in software development environments and I well understand that making accurate predictions can often be nearly impossible. There is a reason
that "The Big Boys" habitually target quarters (three month spans
) in their announcements.
Not that a small developer needs quite such a wide safety net.
If the developer(s) here hope
that something will be done in a week, I urge them to say in public "3 to 8 weeks." If they think
(feel confident) that something will be done in a week, I urge them to say in public something like "If all goes well, this may be ready in 2 weeks. But if unforeseen problems come up, it could be as long as 6 weeks or even more."
Then, most important: post a "course correction" update if necessary. Post it early, not at week three when "2" weeks was promised.
If the earliest was said to be "2 weeks," and as you approach 14 days it becomes clear that that will NOT happen... PLEASE TELL US. Even if you've said "2 weeks to 2 months" surely you must know
that all us eager people will have marked on their calendar not the 2 month point, but the earlier one!