-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Vik wrote: [...] > So at that point i have say 3 files modified for 1st bug fix and say 2 files > for bug 2 which is not yet completely done.
Use a local source control system on your machine. Have two branches: development and production. Do all your work in the development branch, and only push the changes into the production branch when they're ready to deploy. That way you have complete control over what gets deployed independently of what happens to be in your development branch, and if you do things right, you also have the ability to recreate your application as it was during any stage of its lifecycle. (For example, if you push out a change with a bug in it, you can *undo* the change and deploy the application as it was before you introduced the bug.) A source control system is basically a must for any serious development, particularly if there's more than one developer; I typically use Subversion (SVN), CVS or git, all of which are free. Eclipse in particular has superb SVN and CVS integration that make them both a joy to use. If you don't like those, there are dozens of others. - -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ │ "People who think they know everything really annoy those of us who │ know we don't." --- Bjarne Stroustrup -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFKqZZ5f9E0noFvlzgRApxoAJ0ZSmMcyilcNgxkrAOpmg9uAI4zPQCfdTv6 MDci+8u8UHn5GRJLVXSGlZM= =KlKD -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en -~----------~----~----~----~------~----~------~--~---
