I was in the exact same boat a while back. You may be interested in this thread:
(http://groups.google.com/group/django-users/browse_thread/thread/69ad3da32daeb963/f54e6695f76fe73f#f54e6695f76fe73f). I have been trying to get some momentum started on this front, but haven't had any luck. I agree that things have been awfully quiet on the development trunk, especially when there is so much code that should be reviewed and merged. I can only assume that the developers that call the shots are busy with there personal interests at the moment. Many may respond to your question with something that says " It needs real world testing", or "It will get done when it gets done", both of which are a joke in my opinion. Most of the projects have already seen allot of testing by the developers themselves, and quite a few developers have taken the time work with them. I wounder if Django itself went through a formal code review and Q/A cycle before it was released? If so, who was the independant firm that cerified it? I think it just worked good enough and was pushed out. The folks that are on the "when it's ready" band wagon should realize that software is never done. Or are you still using punch cards? Trying to test and develop against so many branches isn't practical. For example, you could start writing an application on the RLP branch, and would like to start using the schema evolution code. This is a problem because that functionality isn't in the RLP branch. This leaves you with two options: 1)Rip out the RLP code that you just worked hard to create and then work with the schema evolution branch, or, 2) Merge the two branches. But merging the two is really getting out of line because it would be a branch of two development branches that are built off of a development branch . You also get stuck with trying to manage several version of Django. Now here is an idea t that will blow your mind. Why don't we just merge these projects with the main development trunk, and allow everyone to work with this code during there normal development cycle. Then when we run into issues/bugs they can be fixed in a cohesive environment. It should be obvious that everyone would benefit by using the same code base. When you think about it, isn't a development trunk meant for developing new features and working out the kinks. --Nick Pavlica --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users -~----------~----~----~----~------~----~------~--~---
