Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: 
 <CAJpvC4L0xJiOQHqY=suNSCwxNwOc0bL2+cK9aTB6zvri1OMy_Q@mail.gmail.com>
References: 
 <CAGMZAuOGjWHdSAZ5rTv9kZCVjnwY_YWSUzEkjbFtC6=qv-tb5A@mail.gmail.com>
	<CAJpvC4+g7N=_4XsAx2wFr__M86GALZd_7A1GcP=UgTQ5dcMcrw@mail.gmail.com>
	<CAGMZAuOuRkP1cV1+YPpC1k-+Q-912ZAPRfE5EwtF7nDRJg8b5A@mail.gmail.com>
	<CAJpvC4+v+gqaL6GZhuF3YCMM00mUe7S8UQqKqgn1G4HbLa=P6w@mail.gmail.com>
	<CAGMZAuN=avK4qrN93qOUph2K59UDeX4JRB1=ijfToh8hxYd8Nw@mail.gmail.com>
	<CAJpvC4L0xJiOQHqY=suNSCwxNwOc0bL2+cK9aTB6zvri1OMy_Q@mail.gmail.com>
Date: Mon, 28 Jan 2013 10:22:16 +0100
Message-ID: 
 <CAJSKAsiBiCDoMZwPFGxVwnBMmGB4O-jzJnEZoCqAjc6wpwUekQ@mail.gmail.com>
Subject: Re: Approach to track of plugin upgrades WAS: svn commit: r1437357 -
 /incubator/bloodhound/branches/bep_0003_multiproduct/bloodhound_multiproduct/multiproduct/api.py
From: =?UTF-8?Q?Peter_Ko=C5=BEelj?= <peter@digiverse.si>
To: bloodhound-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=e89a8fb1edaa3077ac04d455d09c

--e89a8fb1edaa3077ac04d455d09c
Content-Type: text/plain; charset=ISO-8859-1

I got a bit confused with the wording so would like to clarify:

1. Plugin should have one or one per component
BaseEnvironmentSetupParticipant correct (as not one per version)?
2. The BaseEnvironmentSetupParticipant::get_db_setup_contributors() speaks
of db scripts but actual upgrades are contained in modules. Should this
actually be get_upgrade_modules()?
3. What is the benefit of having new tables separate from the free db
upgrades?
4. If we have special support for db upgrades, have you considered having
something for ini files as well (I imagine plugins will be adding
new/updating configuration entries as well)

Looks great otherwise,
Peter

PS to Olemis: Whenever I leave your links to Blog EN/Blog ES in my replay,
Apache rejects my emails as SPAM.

On 26 January 2013 00:12, Jose Angel Franco Navarro <jangel.franco@gmail.com
> wrote:

> Hi everyone!
>
> I have just finished a first version for BEP-0005 documentation.
>
> https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0005
>
> Best regards,
> Franco.
>

> 2013/1/23, Olemis Lang <olemis@gmail.com>:
> > This is it https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0005.
> > It's all yours .
> > ;)
> >
> > On 1/23/13, Jose Angel Franco Navarro <jangel.franco@gmail.com> wrote:
> >> You may create the wiki page,
> >>
> >> I will make some time to explain everything down there.
> >>
> >> Best regards,
> >>
> >> Franco.
> >>
> >> 2013/1/23, Olemis Lang <olemis@gmail.com>:
> >>> On 1/23/13, Jose Angel Franco Navarro <jangel.franco@gmail.com> wrote:
> >>>>
> >>> [...]
> >>>>
> >>>> Sorry I couldn't meet the *briefly* condition  :-(
> >>>>
> >>>
> >>> Yeah I noticed . Let's do this . I'll create a new Bloodhound
> >>> Enhancement Proposal for you to explain how this works . You'll have a
> >>> whole wiki page to explain us probably with diagrams , images , etc
> >>> ... (only if necessary ;) and mention how that could be reused in
> >>> multi-product , search and other plugins besides dashboard , which is
> >>> the current target .
> >>>
> >>> @franco : Would you find some time to write this down for us ? Just
> >>> let me know to create that wiki page , please .
> >>>
> >>> However , notice that this doesn't mean your proposal will be
> >>> automatically accepted . In fact it may be rejected if it does not
> >>> satisfy the expectations of the project after further assessment ...
> >>> somehow .
> >>>
> >>> --
> >>> Regards,
> >>>
> >>> Olemis.
> >>>
> >>>
>

--e89a8fb1edaa3077ac04d455d09c--