+ 1
Bilgin
On Mar 26, 2009, at 6:19 PM, David E Jones wrote:
I'm thinking we should delay the release branch for a couple of
weeks. Some reasons:
1. more opportunity to collaborate with the PRC on the press release
2. time to find and fix more issue relating to the new security
policy
This will let that a framework-only installation will be usable by users.
They will be able to login and configure their home portal page
choosing between the framework resourced portlets.
-Bruno
2009/3/27 David E Jones :
>
> I apologize, I thought we had discussed this and based on replies that
+1
--
Ashish Vijaywargiya
David E Jones wrote:
I'm thinking we should delay the release branch for a couple of weeks.
Some reasons:
1. more opportunity to collaborate with the PRC on the press release
2. time to find and fix more issue relating to the new security policy
of no fields subm
David,
I’m very exciting about the new features and counting days for this release,
thanks for your effort.
2009/3/27 David E Jones
>
> I apologize, I thought we had discussed this and based on replies that
> there was a general understanding of what the point of a portal component in
> the fr
I apologize, I thought we had discussed this and based on replies that
there was a general understanding of what the point of a portal
component in the framework would be.
The general idea is to have a webapp that is part of the framework
that any user can go to and see a "home" screen so
Jacopo,
I don't konw you will commit OFBIZ-1235 to this branch until I read this
list. I think I should get more time to do this and try my best to finish
this in this weekend, then you have enough time to review the code.
2009/3/27 Jacopo Cappellato
> I agree,
>
> hopefully this will give m
Hi David,
this sounds fine...thanks for taking the lead in this, excellent!
I do not quite understand what idea you have moving the myportal into
the framework because it think most of it is already there?
regards
Hans
On Thu, 2009-03-26 at 10:19 -0600, David E Jones wrote:
> I'm thinking we sh
I plenty agree too
I'm just sorry to say to Adrian that I will soon begin to make a lot of changes
https://issues.apache.org/jira/browse/OFBIZ-2243
Jacques
From: "Adrian Crum"
I agree also.
I still need to finish the security UI move -
https://issues.apache.org/jira/browse/OFBIZ-1868.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I agree with you, I had assumed that a filter could be used that did not
include certian new feature so the list would only have those things
that have been agreed on like here in the ml.
maybe that is beyond the ability of the Jira and should be liste
This is a good tool to use. Just one small point of clarification: the
decision on when to release will have nothing to do with what is in
Jira. Because there is no top-down management of OFBiz, and we have
not decided to take on the burden of the practice of voting about
which features w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
someone set up a jiras list for the release.
https://issues.apache.org/jira/browse/OFBIZ/fixforversion/12313602
those jiras that need to be completed.
How about creating jiras for all these
then someone can be pointed to it as things they can do to hel
I agree also.
I still need to finish the security UI move -
https://issues.apache.org/jira/browse/OFBIZ-1868.
I've been working on it a little each weekend. Progress was slow at
first because of all the massive changes to the trunk during the last
few months, but things seem to have settled
I agree,
hopefully this will give me the time to commit the code that Guo
Weizhan is working on in OFBIZ-1235.
Jacopo
On Mar 26, 2009, at 5:19 PM, David E Jones wrote:
I'm thinking we should delay the release branch for a couple of
weeks. Some reasons:
1. more opportunity to collabora
I'm thinking we should delay the release branch for a couple of weeks.
Some reasons:
1. more opportunity to collaborate with the PRC on the press release
2. time to find and fix more issue relating to the new security policy
of no fields submitted to service-backed events in the URL, ie th
14 matches
Mail list logo