Hi Dmitry,

> My take is that at first in order to support something new we need to have a
> clear reason (business reason) to do that for us and for our partners and
> customers because we are going to dedicate time and efforts to it and also
> our customers would require to do the same (in a less scale but in any case,
> no one wants to touch working system if only there is sth beneficial out
> there). In line with it we also need to decide about whether we want to
> support both or not.
Makes sense. It clearly must be based on what's good for the product.  And of
course the "good for the product" should be tied to what's good for users,
customers, partners and the community.

> In regards to particular case I think that we need to do it because we want
> to be in a new Ubuntu LTS release and in Universe.
Absolutely. Not only this, but also users installing it from sources or
simply developing will find a barrier if our required JDK is not in the
default repositories.

> In respect to maintaining both versions it looks they are very good
> compatible and do not collide so I would reach an agreement with QA about
> test cycle of it and based on that make a stamp that we are OK. After that
> will only do automated tests of that configuration that you have already
> conducted during first evaluations.
Looks good. I've prepared a document that summarizes our efforts and
plans:
http://wiki.openbravo.com/wiki/ERP/2.50/OpenJDK_support_plan

Please feel free to suggest changes or make them directly.



Regards,

Juan Pablo


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Openbravo-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openbravo-development

Reply via email to