Moving ecommerce to specialpurpose

[David E Jones-3]

This was discussed a while back around the time that specialpurpose  
was introduce, and pos and other things were moved there, but we  
decided on not doing it at the time because of concerns about non-
backward-compatible impact.

Since we are getting ready to do a release branch, probably in a  
couple of weeks, now might be a good time for it.

The probably impact will be for anything that refers to "applications/
ecommerce", and that will have to change to "specialpurpose/
ecommerce". That includes patches, custom code, etc. Most things that  
treat ecommerce just like any other component (especially using the  
component://ecommerce/... syntax) will not be affected by this.

Unless there are major objections I'll plan on doing this sometime in  
the next couple of days.

-David

[Ashish Vijaywargiya]

+1

On Fri, Mar 13, 2009 at 12:26 PM, David E Jones
<[hidden email]> wrote:

>
> This was discussed a while back around the time that specialpurpose was
> introduce, and pos and other things were moved there, but we decided on not
> doing it at the time because of concerns about non-backward-compatible
> impact.
>
> Since we are getting ready to do a release branch, probably in a couple of
> weeks, now might be a good time for it.
>
> The probably impact will be for anything that refers to
> "applications/ecommerce", and that will have to change to
> "specialpurpose/ecommerce". That includes patches, custom code, etc. Most
> things that treat ecommerce just like any other component (especially using
> the component://ecommerce/... syntax) will not be affected by this.
>
> Unless there are major objections I'll plan on doing this sometime in the
> next couple of days.
>
> -David
>
>

[guo weizhan]

+1

2009/3/13 Ashish Vijaywargiya <[hidden email]>

> +1
>
> On Fri, Mar 13, 2009 at 12:26 PM, David E Jones
> <[hidden email]> wrote:
> >
> > This was discussed a while back around the time that specialpurpose was
> > introduce, and pos and other things were moved there, but we decided on
> not
> > doing it at the time because of concerns about non-backward-compatible
> > impact.
> >
> > Since we are getting ready to do a release branch, probably in a couple
> of
> > weeks, now might be a good time for it.
> >
> > The probably impact will be for anything that refers to
> > "applications/ecommerce", and that will have to change to
> > "specialpurpose/ecommerce". That includes patches, custom code, etc. Most
> > things that treat ecommerce just like any other component (especially
> using
> > the component://ecommerce/... syntax) will not be affected by this.
> >
> > Unless there are major objections I'll plan on doing this sometime in the
> > next couple of days.
> >
> > -David
> >
> >
>

[Jacques Le Roux]

+1

Jacques

From: "David E Jones" <[hidden email]>

>
> This was discussed a while back around the time that specialpurpose  
> was introduce, and pos and other things were moved there, but we  
> decided on not doing it at the time because of concerns about non-
> backward-compatible impact.
>
> Since we are getting ready to do a release branch, probably in a  
> couple of weeks, now might be a good time for it.
>
> The probably impact will be for anything that refers to "applications/
> ecommerce", and that will have to change to "specialpurpose/
> ecommerce". That includes patches, custom code, etc. Most things that  
> treat ecommerce just like any other component (especially using the  
> component://ecommerce/... syntax) will not be affected by this.
>
> Unless there are major objections I'll plan on doing this sometime in  
> the next couple of days.
>
> -David
>

[Pranay Pandey-2]

+1

This change will be good.

Thanks & Regards

--

Pranay Pandey

On Mar 13, 2009, at 12:26 PM, David E Jones wrote:

This was discussed a while back around the time that specialpurpose was introduce, and pos and other things were moved there, but we decided on not doing it at the time because of concerns about non-backward-compatible impact.

Since we are getting ready to do a release branch, probably in a couple of weeks, now might be a good time for it.

The probably impact will be for anything that refers to "applications/ecommerce", and that will have to change to "specialpurpose/ecommerce". That includes patches, custom code, etc. Most things that treat ecommerce just like any other component (especially using the component://ecommerce/... syntax) will not be affected by this.

Unless there are major objections I'll plan on doing this sometime in the next couple of days.

-David

[David E Jones-3]

Okay, this is now moved...

-David


On Mar 13, 2009, at 12:56 AM, David E Jones wrote:

>
> This was discussed a while back around the time that specialpurpose  
> was introduce, and pos and other things were moved there, but we  
> decided on not doing it at the time because of concerns about non-
> backward-compatible impact.
>
> Since we are getting ready to do a release branch, probably in a  
> couple of weeks, now might be a good time for it.
>
> The probably impact will be for anything that refers to  
> "applications/ecommerce", and that will have to change to  
> "specialpurpose/ecommerce". That includes patches, custom code, etc.  
> Most things that treat ecommerce just like any other component  
> (especially using the component://ecommerce/... syntax) will not be  
> affected by this.
>
> Unless there are major objections I'll plan on doing this sometime  
> in the next couple of days.
>
> -David
>