Thanks Jacques for your reply and raising concerns. It seems that, I was
not clear enough. Let me try to rephrase what we are doing. If you observe
then Pranay has created new hierachy for each release like 14.12, 15.12 ...
so on.
For each release we have the user stories, and we are adding UATs f
What comments are you looking for? It either works or it doesn't.
A couple of things to consider:
- Is there really a good reason to delete a WorkEffort record when changing
its status should be sufficient?
- Maybe it doesn't work now because the data model has changed since it was
introduced?
-
If there was a change to be made, it should have been to work on moving
ecomseo into ecommerce. There's not really any good reason for both of
them to exist when the only differences between the webapps are the web.xml
files.
Regards
Scott
On 23 January 2017 at 10:44, Jacques Le Roux
wrote:
>
OK, I'll answer your questions step by step. I just need time...
Jacques
Le 22/01/2017 à 22:01, Scott Gray a écrit :
1. Ask for input
2. Get no responses except a -1
3. Wait for a few months
4. Proceed anyway without further discussion
In future it might be quicker to just skip step 1.
Regard
1. Ask for input
2. Get no responses except a -1
3. Wait for a few months
4. Proceed anyway without further discussion
In future it might be quicker to just skip step 1.
Regards
Scott
On 23 January 2017 at 02:06, Jacques Le Roux
wrote:
> Done, I have added links for developers
>
> Jacques
>
>
Done, I have added links for developers
Jacques
Le 18/01/2017 à 09:45, Jacques Le Roux a écrit :
I have done the change for R16.11.
BTW, trunk demo has no official link, should we not add one (not official?)
somewhere in the site or the wiki?
Jacques
Le 22/09/2016 à 14:07, Jacques Le Roux
I created https://issues.apache.org/jira/browse/OFBIZ-9185 please comment
Thanks
Jacques
Le 19/01/2017 à 21:35, Jacques Le Roux a écrit :
Hi,
I looked closely and I do not understand how the deleteWorkEffort service can work. Especially when a Workeffort has an established relationship
with
Thanks Rishi,
This is interesting, do you envision a mean to automate these tests and run
them frequently?
Say either on each build (using BuildBot for instance), or on another frequency if they happens to be at term longer than our commit frequency would
support.
So the question is do you p