When should we remove the "services" code?

[Scott Wilson <sc...@gmail.com>]

Hi everyone,

In 0.9.1 we deprecated "services" (aka categories) and related functionality (widget default types etc) as these are more properly the concern of a widget store (such as the Apache Rave widget repository, or the widget store that will be developed by a group of projects at http://code.google.com/p/widgetstore/ )

The question I have is when should we actually *remove* the deprecated code?

Personally I think 0.9.1 is quite a solid release, QA-wise, and so anyone who needs some sort of services support could stay on 0.9.1 until they are ready. In which case we can remove the code now ready for 0.9.2. 

However, there isn't going to be a long gap before we release 0.9.2 as the major new additions (templating system, oAuth) are already in place and ready to test.

What do you think? Is anyone using the services feature or relying on it for integration with other platforms?

- S

PS: I've had a quick look, and removing services will eliminate ~16 source files and around 800 lines of code...

Re: When should we remove the "services" code?

[Scott Wilson <sc...@gmail.com>]

On 19 Nov 2011, at 18:02, Ross Gardler wrote:

> Sent from my mobile device, please forgive errors and brevity.
> On Nov 19, 2011 5:21 PM, "Scott Wilson" <sc...@gmail.com>
> wrote:
>> 
>> Hi everyone,
>> 
>> In 0.9.1 we deprecated "services" (aka categories) and related
> functionality (widget default types etc) as these are more properly the
> concern of a widget store (such as the Apache Rave widget repository, or
> the widget store that will be developed by a group of projects at
> http://code.google.com/p/widgetstore/ )
>> 
>> The question I have is when should we actually *remove* the deprecated
> code?
>> 
>> Personally I think 0.9.1 is quite a solid release, QA-wise, and so anyone
> who needs some sort of services support could stay on 0.9.1 until they are
> ready. In which case we can remove the code now ready for 0.9.2.
>> 
>> However, there isn't going to be a long gap before we release 0.9.2 as
> the major new additions (templating system, oAuth) are already in place and
> ready to test.
> 
> Personally I don't like removing features in a point release. I'd say it
> should be removed in 0.10
> 
> I agree that 0.9.1 is solid, perhaps a 0.9.2 out the door quickly which
> officially deprecated the GUI and defines the API features and gives 100%
> the W3C test results. Next target should be removal of the deprecated code
> and provision of a full API and command line tool at 0.10.

That makes more sense.

I've rejigged the roadmap in Jira to give us a 0.10.0 release point after 0.9.2 and put the removal of service code and adding the command line tool against 0.10.0.

> 
> Ross
> 
>> 
>> What do you think? Is anyone using the services feature or relying on it
> for integration with other platforms?
>> 
>> - S
>> 
>> PS: I've had a quick look, and removing services will eliminate ~16
> source files and around 800 lines of code...
>> 
>> 

Re:When should we remove the "services" code?

[Ross Gardler <rg...@opendirective.com>]

Sent from my mobile device, please forgive errors and brevity.
On Nov 19, 2011 5:21 PM, "Scott Wilson" <sc...@gmail.com>
wrote:
>
> Hi everyone,
>
> In 0.9.1 we deprecated "services" (aka categories) and related
functionality (widget default types etc) as these are more properly the
concern of a widget store (such as the Apache Rave widget repository, or
the widget store that will be developed by a group of projects at
http://code.google.com/p/widgetstore/ )
>
> The question I have is when should we actually *remove* the deprecated
code?
>
> Personally I think 0.9.1 is quite a solid release, QA-wise, and so anyone
who needs some sort of services support could stay on 0.9.1 until they are
ready. In which case we can remove the code now ready for 0.9.2.
>
> However, there isn't going to be a long gap before we release 0.9.2 as
the major new additions (templating system, oAuth) are already in place and
ready to test.

Personally I don't like removing features in a point release. I'd say it
should be removed in 0.10

I agree that 0.9.1 is solid, perhaps a 0.9.2 out the door quickly which
officially deprecated the GUI and defines the API features and gives 100%
the W3C test results. Next target should be removal of the deprecated code
and provision of a full API and command line tool at 0.10.

Ross

>
> What do you think? Is anyone using the services feature or relying on it
for integration with other platforms?
>
> - S
>
> PS: I've had a quick look, and removing services will eliminate ~16
source files and around 800 lines of code...
>
>