Hi James,
Le 30/11/2017 à 16:30, James Yong a écrit :
+1 to using Flat Grey theme as the default for the upcoming release for the
reason given by Jacques
Was trying out on Visual Theme selection.
Saw some rough edges on the OFBiz logo for Tomahawk & Flat Grey themes.
Actual OFBiz logo seen in the application for Tomahawk & Flat Grey themes
doesn't tally with the logos in the screenshots.
Yes I have opened https://issues.apache.org/jira/browse/OFBIZ-9990 for that
I'll see if I can fix it before switching (Anyway we need to use the new logo)
I have also opened somehow related https://issues.apache.org/jira/browse/OFBIZ-9924 to "Make the general.SystemPropertyValue same than the related
property in general properties"
BTW, I'll maybe before fix http://markmail.org/message/nvgzvs4twqlwdoep and
then, use rather Rainbow Saphir
It's not totally clear in my mind at the moment, maybe those are not specific
to Rainbow Saphir and we can use it as default
WIP...
Thanks
Jacques
Regards,
James Yong
On 2017-11-30 23:02, Jacques Le Roux <jacques.le.r...@les7arts.com> wrote:
Should we keep Tomahawk as the default in trunk or change before freezing for
R17.12?
We know Tomahawk does not support RTL languages and we have a such users base
using demos (I see it every time I use demos).
There is still work to do for Rainbow[1], so maybe the old Flat Grey?
Jacques
[1] http://markmail.org/message/nvgzvs4twqlwdoep
Le 30/11/2017 à 08:39, Nicolas Malin a écrit :
Nice, the end of the years will be hardest :)
Nicolas
Le 29/11/2017 à 11:06, Jacopo Cappellato a écrit :
Ok, thanks for all the feedback guys!
Let's plan to create the branches before the end of the year.
Jacopo
On Tue, Nov 28, 2017 at 7:54 PM, Taher Alkhateeb <slidingfilame...@gmail.com
wrote:
I think Rishi makes a good point. OFBIZ-9501 is a big task but it
would be nice to create the release after the majority of data is
moved. Rishi is already progressing in this task I think it might be
worth waiting a little bit to have a clean datamodel component.
On Tue, Nov 28, 2017 at 7:20 PM, Rishi Solanki <rishisolan...@gmail.com>
wrote:
Jacopo,
Thanks for heads-up, I have OFBIZ-9501 with me, and I think it should be
part of new release. As the data movement will impact on ease of
debugging
and maintenance. I'm planning to move most seed and seed-initial data by
this weekend.
This should not impact the release date, because If community allow to
commit after release cut then we can migrate the changes to new release
after that as well. I'm saying this because I have already move few
components data to data model component like party, content and work
effort. So for the release the data consistency should be there at least
for seed and seed-initial data.
If community not allowing to move data after release cut then I would say
to hold for few days, so that we can make the data pattern consistent.
Also
may be others may have more tickets/bugs with them.
Kind Regards,
--
Rishi Solanki
Sr Manager, Enterprise Software Development
HotWax Systems Pvt. Ltd.
Direct: +91-9893287847
http://www.hotwaxsystems.com
www.hotwax.co
On Tue, Nov 28, 2017 at 9:12 PM, Jacopo Cappellato <jacopo.cappellato@
hotwaxsystems.com> wrote:
It's the end of November and we are close to the deadline for the
creation
of the 17.11 branches: how do we feel about it?
Let me know if you want me to proceed, otherwise we will create the
branches in December and they will be named 17.12
Regards,
Jacopo
On Thu, Oct 12, 2017 at 6:09 PM, Nicolas Malin <
nicolas.ma...@nereide.fr>
wrote:
Hi,
Agree to create the release 17.11 with a separate products framework &
plugins.
It's woulb be nice to create this release one week after the next
community days :)
Nicolas
Le 10/10/2017 à 09:35, Jacopo Cappellato a écrit :
Hi all,
I think it is time to start thinking about if, when, how we should
create
the new release branch out of the trunk. Actually, for the first
time,
we
should probably create two branches: one for the framework and one
for
the
plugins.
What do you think?
In my opinion we could try to get all the changes we want to have in
the
trunk to be included in the branch by end of November: this means
that
the
the creation of the branch could happen at the end of November.
If this is the case then the names could be:
release17.11-framework
release17.11-plugins
The above is for the release *branches* only, not for the actual
releases.
We could decide at a later point if the actual releases will be
shipped
as
two separate products (e.g. "Apache OFBiz Framework 17.11.01" and
"Apache
OFBiz Plugins 17.11.01") or merged into one (e.g. "Apache OFBiz
17.11.01").
Best regards,
Jacopo
