← Back to team overview

openerp-community team mailing list archive

Re: new api, v8 release

 

We merged some last schema and api changes:

- in crm, rename type and channel to the google analytic terminology we now have:

crm.tracking.campain (old type)
crm.tracking.source
crm.tracking.medium (old channel)

with a mixin to save those fields on crm.lead and sale.order. This is required to track google adwords campains on lead generation and e-commerce shopping carts.

- on purchase.order chaging the date into a datetime (not sure it's merged yet).

- remove the "any type" field from the new api.

I left report_webkit but we will only merge bugfixes in 8.0 and i will remove it from master soon, along with the rml report engine.

Simon is working on the packaging, the setup/package.py will allow anyone under linux to build the tgz, deb (for debian stable), rpm (for Redhat 7 or Centos 7) and even the exe (using wine). MacOS X packaging is also planned. The goal is to improve those packages to get them accepted in the various linux distributions (debian first).

The rest is only bugfixes.

We are still migrating internally, I will keep you posted about our migration, once our migration is done we will migrate the saas and allow new user to create database on 8.0.

Then we will bless the packages and tag the release.

You can already safely start working on 8.0, 90% of the diff from v7 to v8 has already been battle tested on our saas, only the new api and wms may still have bugs. So the stabilization period will be much shorter compared to v7.

We wait for your feedback.

On 07/08/2014 08:00 PM, Nhomar Hernández wrote:

2014-07-08 12:37 GMT-04:30 Raphael Valyi <rvalyi@xxxxxxxxx
<mailto:rvalyi@xxxxxxxxx>>:

    So I would say, please let's don't be dogmatic about a release date. It's
    bad to be 6 months late on release schedule (as it was for v7 initially
    announced much earlier), but it's much better to be a little late and have
    early adopter test deeply and report bugs and contribute fixes before
    freezing things for 18 months. So please no pressure to release exactly on
    date. Some good complex projects do 6 RC's before declaring something
    stable and there is no magic, unless you have a test coverage of 100% with
    very clear specifications (which we don't have), it's about the only way
    to have something both "stable" and usable for later.


Agreed 100% with Raph.

- This release can be seen as "RC-2" for v8.0 (the merge of new API).
- I hope we can test the new API too making some migrations of our own modules
to avoid what we live in v5 (do you remember, bad views parsing, incomplete
orm, slow property fields and so on?, new incomplete fetures).

Then KUDOS for thsi pre-release, and for the tag for us it is excellent (at
least for me) ;-)

Regards.

--
--------------------
Saludos Cordiales

Nhomar G. Hernandez M.
+58-414-4110269
Skype: nhomar00
Web-Blog: http://geronimo.com.ve <http://geronimo.com.ve/>
Servicios IT: http://vauxoo.com <http://vauxoo.com/>
Linux-Counter: 467724
Correos:
nhomar@xxxxxxxxxxxxxx <mailto:nhomar@xxxxxxxxxxxxxx>
nhomar@xxxxxxxxxx <mailto:nhomar@xxxxxxxxxx>
twitter @nhomar


_______________________________________________
Mailing list: https://launchpad.net/~openerp-community
Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openerp-community
More help   : https://help.launchpad.net/ListHelp



Follow ups

References