openerp-community team mailing list archive
-
openerp-community team
-
Mailing list archive
-
Message #04773
Re: Branch Saas and stable 7.0
Well, as I have said, it's only a maintained module of an old approach, but
here it is:
http://bazaar.launchpad.net/~pedro.baeza/serviciosbaeza-openerp-addons/7.0/files
I have improved my OE skills a lot since them ;)
Regards.
2014-02-01 Antony Lesuisse <al@xxxxxxxxxxx>
> Please send a link to the source code. I will check it.
>
>
> On 02/01/2014 03:30 PM, Pedro Manuel Baeza Romero wrote:
>
>> Hi, Antony,
>>
>> I worked some time ago (on v6.0) in two modules called
>> /account_periodical_invoicing/ and /sale_recurring_orders/ that play with
>>
>> these concepts. I have been maintining them up to v7, but they work in an
>> isolated way and with some incomplete concepts (for example. analytic
>> entries
>> generation for incoming revenue analysis).
>>
>> I have adquired a lot of experience with terms (monthly, daily, yearly,
>> etc),
>> payment types (pre-payment, post-payment), natural or real periods (what
>> you
>> call prorrata temporis, I think), discounts, fixed or variable price,
>> etc, so,
>> if you want, I can collaborate with that development. Please contact me
>> if you
>> think so.
>>
>> Regards.
>>
>>
>> 2014-02-01 Antony Lesuisse <al@xxxxxxxxxxx <mailto:al@xxxxxxxxxxx>>
>>
>>
>> Yes this feature is quite small it's located in
>> account_analytic_analysis.py
>> recurring_* feilds and account.analytic.invoice.line.
>>
>> We plan to improve this feature a bit to allow choosing between SO or
>> invoice, discount on lines, and optional pro-rata temporis invoicing
>> on lines.
>>
>>
>> On 02/01/2014 01:48 PM, Yannick Buron wrote:
>>
>> Thanks Anthony, I hope that theses precisions will also be useful
>> to
>> others
>> and help understand your development process. So saas branch are
>> really the
>> future V8, really interesting.
>>
>> About my case, unfortunately I can't wait for V8 but it's clear it
>> would be
>> safer to stick to OCB branch. Maybe I'll follow the Raphael
>> advice (thanks
>> Raphael :) ), and try to extract and backport the feature.
>>
>> Yannick.
>>
>> Le 31/01/2014 21:00, Raphael Valyi a écrit :
>>
>> On Fri, Jan 31, 2014 at 3:57 PM, Yannick Buron
>> <yannick.buron@xxxxxxxxx <mailto:yannick.buron@xxxxxxxxx>
>> <mailto:yannick.buron@gmail.__com
>>
>> <mailto:yannick.buron@xxxxxxxxx>>> wrote:
>>
>> Dear OpenERP Community,
>>
>> As we can see on launchpad, theses days a new saas-3
>> branch
>> has been
>> created by OpenERP SA, following their process described
>> here :
>> http://help.openerp.com/__question/36712/what-is-the-__
>> difference-between-trunk-saas-__1-and-saas-2-versions-in-__launchpad/
>> <http://help.openerp.com/question/36712/what-is-the-
>> difference-between-trunk-saas-1-and-saas-2-versions-in-launchpad/>.
>>
>>
>> My concern is, I need to use a feature which is actually
>> only
>> available
>> in the saas branch, the recurring invoicing. I'm using
>> actually the OCB
>> branchs for this project.
>>
>> I'd like to know if the publication of this saas-3 means
>> that
>> the stable
>> 7.0 will also be updated, either with the code from
>> saas-2
>> branch or
>> saas-3. In general, is the position of OpenERP SA to
>> update
>> the stable
>> branch with features from saas from time to time or do we
>> have to wait
>> for the next major version (here V8) to get the early
>> features which are
>> in Saas?
>>
>> Thank you for your opinions, following them I'll decide
>> either to go on
>> Saas branch or wait for stable 7.0 (and then upgrade to
>> OCB
>> branch when
>> it'll be updated). If you know a good community module
>> which
>> allow the
>> recurring invoices (And please, not subscription module
>> :) ),
>> this could
>> also allow me to stay on OCB branch.
>>
>> Best Regards,
>> Yannick Buron.
>>
>>
>> Hello Yannick,
>>
>> during this period of time when OpenERP trunk is said to be
>> too
>> unstable to
>> be deployed outside of a SaaS, my advise is to use
>> git-subtree to
>> extract
>> key features as individual modules that can be backported
>> alone
>> without too
>> much effort (pre-pended in your addons-path then). For
>> instance, I
>> think
>> this is absolutely the case with recurring invoice while it
>> wouldn't be
>> reasonnable for quant based stock management.
>>
>> I explained the idea and gave 2 examples here of such
>> backport.
>> Please don't
>> hesitate to suggest pull request if you see room for
>> improvement
>> or re-synch
>> with upstream.
>> https://lists.launchpad.net/__openerp-community/msg04122.__
>> html
>>
>> <https://lists.launchpad.net/openerp-community/msg04122.html>
>>
>> Again, I'm all behind sticking with bzr with OCA and core of
>> OpenERP, right
>> now, it's just that I think git is so much more appropriate
>> for these
>> synchronized extractions.
>>
>> Regards.
>>
>> --
>> Raphaël Valyi
>> Founder and consultant
>> http://twitter.com/rvalyi <http://twitter.com/#%21/__rvalyi
>> <http://twitter.com/#%21/rvalyi>>
>> +55 21 2516 2954 <tel:%2B55%2021%202516%202954>
>> www.akretion.com <http://www.akretion.com> <
>> http://www.akretion.com/>
>>
>>
>>
>>
>> _________________________________________________
>> Mailing list: https://launchpad.net/~__openerp-community
>> <https://launchpad.net/~openerp-community>
>> Post to : openerp-community@lists.__launchpad.net
>> <mailto:openerp-community@xxxxxxxxxxxxxxxxxxx>
>> Unsubscribe : https://launchpad.net/~__openerp-community
>> <https://launchpad.net/~openerp-community>
>> More help : https://help.launchpad.net/__ListHelp
>> <https://help.launchpad.net/ListHelp>
>>
>>
>>
References