Stable release requirements?

nedjo - November 9, 2009 - 22:58
Project:Deployment
Version:6.x-1.x-dev
Component:Code
Category:task
Priority:normal
Assigned:Unassigned
Status:active
Description

Is there an idea of what would be needed to get to a stable release?

See #588172: is there a stable release schedule? for prospects for a Services 6.2.x stable release.

#1

heyrocker - November 10, 2009 - 00:16
Status:active» closed

I am quite familiar with that Services thread thanks ;P

I would like to see the following happen for a stable release. Most of these are 'nice to have' however i think the project is very much 'incomplete' without them.

- Ability to deploy without interactive authentication, likely depending on services_oauth #537488: Add the ability to push deployment plans without user input (for instance from cron)

- Make deployment modules be on-demand includes instead (most likely through a plugin mechanism like CTools uses). Right now there is a pretty significant code weight associated with the module which I believe could be seriously alleviated without much effort.

- Support for core Upload module #459192: Deply module isn't work with upload module

- Parent menu item support for Book/Page/etc nodes #599420: menu parent hierarchy issues

- Multilingual support #596204: Multiple language-specific system settings may not be deployed correctly

- Nodereference widget support #596204: Multiple language-specific system settings may not be deployed correctly

- Refactoring UUID module, moving the node/user/comment/etc CRUD functions into their respective modules (although I only want this if I can get the plugin functionality running)

Right now I have no schedule. I have very little time for unsponsored development on the module. I'm trying to keep the queue in shape, but honestly right now I'm a bit more focused on other projects like the D7 port of Services. Additionally, with D7 so close, I am somewhat reluctant to spend significant development without getting into conversion which I predict to be hairy.

If anyone would like to sponsor any of the above development please get in touch, but outside of that I can't promise anything.

#2

heyrocker - November 19, 2009 - 23:20
Status:closed» active

Reopening this thread so it shows up in the queue for those who are interested in contributing to / commenting on any of these issues.

#3

dixon_ - November 20, 2009 - 09:00

I would like to wait with a stable release. Mostly because we will invest some time in this module for a couple of months. We will mainly work with the ability to deploy to other servers than Drupal sites. And that includes a pluggable authentication system for Deploy. Other than that we will try to help out in other relevant issues.

This project will be on part time for a couple of months probably. So I would suggest waiting with a stable release to get some more issues fixed.

#4

dixon_ - November 20, 2009 - 09:27

I would also like to take part in the refactoring of Deploy to be based on CTools. I believe (as you mentioned above) that we can save a lot of code weight and win more flexibility by doing this. Although, I dont know if my schedule will allow this in short terms.

#5

heyrocker - November 20, 2009 - 13:30

There is a reasonably chance that I'll be getting some time to work on a few of these issues in the coming weeks, including making the integration modules into plugins. I'm torn on whether to use CTools for that or not, as I'm not sure I want to assume another dependency and it might be a little overkill. I'll worry about that when we get there though.

 
 

Drupal is a registered trademark of Dries Buytaert.