Closed (won't fix)
Project:
AutoPilot
Version:
5.x-2.0-beta4
Component:
Miscellaneous
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
24 Dec 2008 at 21:27 UTC
Updated:
6 Jan 2009 at 19:48 UTC
The AutoPilot module has been deprecated by it's creators. It's not working correctly, apparently never has, and it needs someone to take it over and give it some love so that it doesn't stagnate. The maintainers would happily hand over the autopilot project to the right candidate, so if that's you, please reply to this issue in the affirmative so the community doesn't loose forward momentum on such a good idea.
Comments
Comment #1
IncrediblyKenzi commentedQuite the opposite.. The autopilot module works for what it does (moving code between systems). The issue at hand is more that it doesn't do what the community as a whole is demanding. Rather than try to eke that out ourselves, we'd like to give the community the opportunity to make Autopilot fit into what its vision of build management really is.
On that note, we've had some great success in integrating third party build and software lifecycle management tools into drupal. For example, maven and drupal play rather nicely together, and that, combined with coding and sofware lifecycle management best practices have gone a long way for us on several projects, and we'll be publishing documentation to that effect coming soon.
That being said, we'd love it if someone else in the community could take over Autopilot, as it is in the best interests of the community that AutoPilot not get silo-ed into providing a singular function that is only useful to a handful of people.
Comment #2
senpai commentedAaron said it best. ^^
So Aaron, is Maven going to be the next big thing?
Comment #3
senpai commentedGetting this out of my issue queue.
______________________________
Senpai