Re:So little good advice (formatted) (Score 3, Interesting)

Sorry to read that there's such a high noise/signal ratio for the replies to your problem here. I was involved in a similar situation to yours (timeline slightly longer, but same demands on developers), and here's what we decided we learned afterwards:

1. when this project fails, there will be a scapegoat, so make sure you're not it
2. do your absolute best to NOT gripe about the situation with coworkers at the office; negativity is always seen negatively (in other words - be fake happy)
3. don't throw down ultimatums unless you're prepared to stand behind them
4. on the other hand, try to organize a very carefully worded notice of recommendations for improving the situation, and get all of the developers there to agree on it, and sign it

On number 4: Try to make the list positive (tough, I know). Nobody (esp managers) like to be told they're wrong. And be sure that no one person is listed in a leadership position, to avoid being labeled as the 'rabble rouser'. This means delivering a printed letter anonymously, not via somebody's e-mail account. I know this is paranoid, but the person who delivered our list got the short stick...

Good luck with this situation, I feel for you.

To all of you who claimed your jobs require you to work long hours - suck it up. Nobody is making you work there.