openerp-community team mailing list archive

[Yann Papouin <yann.papouin@xxxxxxxxx>]

Really nice to have some news about current developments.

Antony, are you planning a "bug hunt" or "bug cleaning" event or something
like this before releasing this new version ?
Because, there are so many "confirmed" / "fix committed" bugs assigned to
openerp-dev-*, it would be disappointing to see them set as "Won't Fix"
after the new release with a pasted message like "As per our bug management
policy we can not consider bug [...]"

About the NIH syndrome that you exposed, I also have a request:
Create a launchpad bug report for each new OPW branch to avoid reporters
loosing time by creating a new report and a branch with a merge proposal
that already exists as an opw.


2014-01-28 Antony Lesuisse <al@xxxxxxxxxxx>

> Thanks for the feedback, we will do a RD blog as soon as we have converted
> our website to the new openerp website module.
>
> I think the openerp cms will help us a lot to communicate with the
> community, as we will be able to easily share our internal documents (such
> as tasks and projects) on the public website.
>
>
> On 01/27/2014 08:54 AM, Alexandre Fayolle wrote:
>
>> I totally agree with Holger and Ferdinand.
>>
>> What about an OpenERP development blog ? This is something quite common in
>> open source projects, and it has benefits over mails (collaborative
>> edition,
>> archives, searchability, visibility). However, if you go in this
>> direction,
>> please make sure ths blog is updated by techies, not suits (iow, what, I
>> as a
>> developer, care about is technical information, not commercial brochures
>> with
>> nice looking pictures :-) )
>>
>> Thanks for the great looking upcoming v8
>>
>> Alexandre
>>
>> On 24/01/2014 23:57, Ferdinand Gassauer wrote:
>>
>>> On 2014-01-24 22:10, Holger Brunn wrote:
>>>
>>>> Anthony,
>>>>
>>>> I'm very thankful for your mail just explaining (by naming) branches.
>>>> If you
>>>> write this kind of mails every couple of months just to keep us (the
>>>> people
>>>> who are eager to see openerp developing) updated, you'll even forecome
>>>> some of
>>>> the discussions we had.
>>>> Please, keep doing that regularly. It might even make sense to hire a
>>>> person
>>>> who does just that: keep the community up to date on what goes on
>>>> codewise.
>>>>
>>> IMO this info should be posted  on a web page
>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>
>>>
>>> --
>>> Ferdinand
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>
>>
>> --
>> Alexandre Fayolle
>> Chef de Projet
>> Tel : + 33 (0)4 79 26 57 94
>>
>> Camptocamp France SAS
>> Savoie Technolac, BP 352
>> 73377 Le Bourget du Lac Cedex
>> http://www.camptocamp.com
>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
> _______________________________________________
> 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
>