.
As you can guess, I am troubled about the relation between releases and the
trunk and demos in OFBiz.
Would you prefer to not have the specialpurpose components in R13.07 demo?
If they are not in the 13.07.01 release it creates a bit of a mismatch between
the demo and what you actually get
and demos in OFBiz.
Would you prefer to not have the specialpurpose components in R13.07 demo?
If they are not in the 13.07.01 release it creates a bit of a mismatch between
the demo and what you actually get.
Otherwise I would have no problem.
It's also Jacopo's opinion, I don't know if it's
On Oct 24, 2014, at 9:58 AM, Jacques Le Roux jacques.le.r...@les7arts.com
wrote:
I guess at some point the disabled specialpurpose components in trunk will
end in Attic.
Not necessarily: a disabled component could be a specialized version (e.g. for
a specific industry or for a specific
the relation between releases
and the trunk and demos in OFBiz.
Would you prefer to not have the specialpurpose components in R13.07
demo?
If they are not in the 13.07.01 release it creates a bit of a
mismatch between the demo and what you actually get.
Otherwise I would have no problem.
It's
On 24/10/2014 6:52 AM, Jacopo Cappellato wrote:
On Oct 24, 2014, at 9:58 AM, Jacques Le Roux jacques.le.r...@les7arts.com
wrote:
I guess at some point the disabled specialpurpose components in trunk will end
in Attic.
Not necessarily: a disabled component could be a specialized version
Le 30/09/2014 08:47, Jacopo Cappellato a écrit :
Also, since (by design) the specialpurpose components there could be
incompatible components (i.e. specialpurpose/a causes side effects in
specialpurpose/b), or alternative components (i.e. specialpurpose/a is a
different implementation of the
On Oct 23, 2014, at 2:07 PM, Jacques Le Roux jacques.le.r...@les7arts.com
wrote:
I agree about the idea, but this applies only to releases or checked out
code. Because there are no ways for users to enable/disable a component in
demos, moreover demos are shared.
Could you please explain
Le 23/10/2014 15:01, Jacopo Cappellato a écrit :
On Oct 23, 2014, at 2:07 PM, Jacques Le Roux jacques.le.r...@les7arts.com
wrote:
I agree about the idea, but this applies only to releases or checked out code.
Because there are no ways for users to enable/disable a component in demos,
On 23/10/2014 10:39 AM, Jacques Le Roux wrote:
Le 23/10/2014 15:01, Jacopo Cappellato a écrit :
On Oct 23, 2014, at 2:07 PM, Jacques Le Roux
jacques.le.r...@les7arts.com wrote:
I agree about the idea, but this applies only to releases or checked
out code. Because there are no ways for users
demos because they can be there. But they are not maintained in the R13.07 branch (but
ecommerce) only in trunk.
As you can guess, I am troubled about the relation between releases and the
trunk and demos in OFBiz.
Would you prefer to not have the specialpurpose components in R13.07 demo
the specialpurpose components in R13.07
demo?
It is a bit odd and certainly goes against most product release
strategies wherein the current release is the recommended download
and carries whatever warranty that the project offers in terms of
testing and rapidity of bug fixes and the trunk
(but
ecommerce) only in trunk.
As you can guess, I am troubled about the relation between releases and the
trunk and demos in OFBiz.
Would you prefer to not have the specialpurpose components in R13.07 demo?
It is a bit odd and certainly goes against most product release strategies
wherein
be there. But they are not maintained in the R13.07 branch (but
ecommerce) only in trunk.
As you can guess, I am troubled about the relation between releases and the
trunk and demos in OFBiz.
Would you prefer to not have the specialpurpose components in R13.07 demo?
It is a bit odd
and demos in OFBiz.
Would you prefer to not have the specialpurpose components in R13.07 demo?
It is a bit odd and certainly goes against most product release strategies wherein the current release is the recommended download and carries
whatever warranty that the project offers in terms of testing
to not have the specialpurpose components in R13.07 demo?
It is a bit odd and certainly goes against most product release strategies wherein the current
release is the recommended download and carries whatever warranty that the project offers in terms
of testing and rapidity of bug fixes and the trunk
to not have the specialpurpose components in R13.07 demo?
It is a bit odd and certainly goes against most product release strategies wherein the current
release is the recommended download and carries whatever warranty that the project offers in terms
of testing and rapidity of bug fixes
the relation between releases
and the trunk and demos in OFBiz.
Would you prefer to not have the specialpurpose components in R13.07
demo?
It is a bit odd and certainly goes against most product release
strategies wherein the current release is the recommended download
and carries whatever
and demos in OFBiz.
Would you prefer to not have the specialpurpose components in R13.07 demo?
It is a bit odd and certainly goes against most product release strategies wherein the current release is the recommended download and carries
whatever warranty that the project offers in terms of testing
in the
R13.07 branch (but ecommerce) only in trunk.
As you can guess, I am troubled about the relation between
releases and the trunk and demos in OFBiz.
Would you prefer to not have the specialpurpose components in
R13.07 demo?
It is a bit odd and certainly goes against most product release
the specialpurpose components in R13.07
demo?
If they are not in the 13.07.01 release it creates a bit of a mismatch
between the demo and what you actually get.
Otherwise I would have no problem.
Ron
It is a bit odd and certainly goes against most product release
strategies wherein
in my opinion it is better to run the demo on the exact copy of the release
branch.
Jacopo
On May 30, 2014, at 2:28 PM, Jacques Le Roux jacques.le.r...@les7arts.com
wrote:
Hi,
For the R13.07 demo I think we should set an external property from trunk
into specialpurpose for some (those
Also, since (by design) the specialpurpose components there could be
incompatible components (i.e. specialpurpose/a causes side effects in
specialpurpose/b), or alternative components (i.e. specialpurpose/a is a
different implementation of the same features of specialpurpose/b) or
components
Hi,
For the R13.07 demo I think we should set an external property from trunk into
specialpurpose for some (those which make sense) components.
I created this svn external property:
specialpurpose/assetmaint/
https://svn.apache.org/repos/asf/ofbiz/trunk/specialpurpose/assetmaint
23 matches
Mail list logo
