← Back to team overview

openerp-community team mailing list archive

  1. openerp-community team
  2. Mailing list archive
  3. Message #06473

Re: new api, v8 release

  Thread Previous • Date Previous • • Thread Next
While I agree that promising a date without keeping it may put us in a unpleasant situation with some customers, I suggest to not put too much pressure on Odoo SA and let them time to make this right.
As Raphael said, one error in database schema and we will have big problems during the whole V8 duration. There is no sense to want to hold the release date at all cost, some customers may not understand that but ultimately this is for their good.
That said, for the next releases I am also in favor for using RC as most of the open-source projects, this will be far more comfortable and will avoid such reactions from customers. 

Kuddos for the work and the api release.
Yannick.

Le 09/07/2014 10:42, Denis Karataev a écrit :

Josef is right!
We already answered to all our customers about release date that it's 7 July. On this date I had many (not happy) questions, why they don't see any announcement about v8 on Odoo website.
2014-07-09 15:37 GMT+07:00 Josef Kaser <Josef.Kaser@xxxxxxxxxxxx <mailto:Josef.Kaser@xxxxxxxxxxxx>>: 

    Hi,

    OK, thanks for pointing this out, but I don't agree. July 7th was
    announced as the official release date of v8. Nobody, neither
    Fabien nor Antony or anyone else, did mention this release to be a
    RC or a pre-release. An official release is an official release,
    not a RC. So far for the dogmatic part...

    It would be no problem if there would be a roadmap with the
    release dates for RC[1..x] and for the official release, and if
    the roadmap's deadlines would be met.

    Please see it from the partners' and from the customers' perspective:

    -partners may lose potential (and maybe even existing) customers
    because they (the partners) relied on the announced release date

    -customers, especially in the targeted SME market, want to have
    confidence in their software vendors; if they don't have they will
    look for alternatives, and then they are lost for odoo for the
    next five to ten years

    Of course it is one of the most important things to deliver a
    stable and feature rich software. But it is not good if there are
    being raised expectations that are not being fulfilled in the end.

    Just my 2 cents...

    Regards

    Josef
-- 
    Dipl.-Wirt.-Inf. (FH)

    Josef Kaser

    BUSINESS SOLUTIONS

    Consultant

    inoX-tech GmbH

    Gutenbergstr. 8

    94036 Passau

    Tel: +49 851 987 797 68

    Fax: +49 851 987 797 99

    Email: Josef.Kaser@xxxxxxxxxxxx

    Web: http://www.inoX-tech.de

    Registergericht Passau, HRB 6539, Ust-ID: DE814925313

    Geschäftsführung: Michael Döderlein

    *Von:*Nhomar Hernández [mailto:nhomar@xxxxxxxxx
    <mailto:nhomar@xxxxxxxxx>]
    *Gesendet:* Dienstag, 8. Juli 2014 20:01
    *An:* Raphael Valyi
    *Cc:* Josef Kaser; openerp-community
    *Betreff:* Re: [Openerp-community] new api, v8 release

    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
    <https://launchpad.net/%7Eopenerp-community>
    Post to     : openerp-community@xxxxxxxxxxxxxxxxxxx
    <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
    Unsubscribe : https://launchpad.net/~openerp-community
    <https://launchpad.net/%7Eopenerp-community>
    More help   : https://help.launchpad.net/ListHelp




--
Denis Karataev.


_______________________________________________
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

References

  Thread Previous • Date Previous • • Thread Next