You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2013/01/14 10:13:33 UTC

[Apache Bloodhound] #351: Update versions in setup.py files to 0.4.0 for all bloodhound plugins

#351: Update versions in setup.py files to 0.4.0 for all bloodhound plugins
-----------------------+-----------------------
 Reporter:  gjm        |      Owner:  nobody
     Type:  task       |     Status:  new
 Priority:  major      |  Milestone:  Release 4
Component:  dashboard  |    Version:
 Keywords:             |
-----------------------+-----------------------


-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/351>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

Re: [Apache Bloodhound] #351: Update versions in setup.py files to 0.4.0 for all bloodhound plugins

Posted by Ryan Ollos <ry...@wandisco.com>.
On Tue, Jan 15, 2013 at 4:37 AM, Gary Martin <ga...@wandisco.com>wrote:

> [...]
> Is there a particular reason to move away from 1.0 yet?
>

I seem to have sidestepped your question with my earlier reply about 1.0.1
vs 1.1.1. Although I had pasted it into my reply, I had completely
overlooked the comment and had just read the reply by Olemis.

I assumed we would at least upgrade to the latest stable releases as they
come out. Even if I can't point to a specific issue that affects me or
Bloodhound in general, it might affect someone else, and it's nice to have
fewer known issue in our releases. Do you have any specific concerns that
would suggest we wouldn't want to upgrade to at least the 1.0.x releases as
they come out?

Re: [Apache Bloodhound] #351: Update versions in setup.py files to 0.4.0 for all bloodhound plugins

Posted by Ryan Ollos <ry...@wandisco.com>.
On Tue, Jan 15, 2013 at 4:37 AM, Gary Martin <ga...@wandisco.com>wrote:

> [...]
> I wonder if we should consider being a little more specific and call the
> version 1.0-bhN where N is indicative of the number of versions of
> bloodhound with additional changes the trac branch has been through, or
> something like that.
>

Some scheme to track patches on the Trac branch seems valuable,
particularly if we get more than a few patches and have to manage temporary
patches to our Trac branch which will eventually be backed out when those
changes work their way back to the Trac core.

Re: [Apache Bloodhound] #351: Update versions in setup.py files to 0.4.0 for all bloodhound plugins

Posted by Olemis Lang <ol...@gmail.com>.
On 1/15/13, Gary Martin <ga...@wandisco.com> wrote:
> On 14 January 2013 14:52, Olemis Lang <ol...@gmail.com> wrote:
>
>> On 1/14/13, Apache Bloodhound <bl...@incubator.apache.org>
>> wrote:
>> > #351: Update versions in setup.py files to 0.4.0 for all bloodhound
>> plugins
[...]
>> >  * status:  accepted => closed
>> >  * resolution:   => fixed
>> >
>> >
>> > Comment:
>> >
>> >  r1432848 fixes for dashboard, multiproduct and theme
>> >
>> >  r1432859 fixes for search (apparently a downgrade)
>> >
>>
>> Is TRAC_VERSION file in trunk up to date ?
>>
>
> Yes, we have stuck with the 1.0 tagged version for this release although
> there is at least one patch that was applied from trunk.
>
> I wonder if we should consider being a little more specific and call the
> version 1.0-bhN where N is indicative of the number of versions of
> bloodhound with additional changes the trac branch has been through, or
> something like that.
>

afaics , sounds reasonable to me .

> Is there a particular reason to move away from 1.0 yet?
>

0.12.5 , 1.0.1 and 1.1.1 should be scheduled for release this week or
any time soon .

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

Re: [Apache Bloodhound] #351: Update versions in setup.py files to 0.4.0 for all bloodhound plugins

Posted by Gary Martin <ga...@wandisco.com>.
On 14 January 2013 14:52, Olemis Lang <ol...@gmail.com> wrote:

> On 1/14/13, Apache Bloodhound <bl...@incubator.apache.org> wrote:
> > #351: Update versions in setup.py files to 0.4.0 for all bloodhound
> plugins
> > ------------------------+-----------------------
> >   Reporter:  gjm        |      Owner:  gjm
> >       Type:  task       |     Status:  closed
> >   Priority:  major      |  Milestone:  Release 4
> >  Component:  dashboard  |    Version:
> > Resolution:  fixed      |   Keywords:
> > ------------------------+-----------------------
> > Changes (by gjm):
> >
> >  * status:  accepted => closed
> >  * resolution:   => fixed
> >
> >
> > Comment:
> >
> >  r1432848 fixes for dashboard, multiproduct and theme
> >
> >  r1432859 fixes for search (apparently a downgrade)
> >
>
> Is TRAC_VERSION file in trunk up to date ?
>

Yes, we have stuck with the 1.0 tagged version for this release although
there is at least one patch that was applied from trunk.

I wonder if we should consider being a little more specific and call the
version 1.0-bhN where N is indicative of the number of versions of
bloodhound with additional changes the trac branch has been through, or
something like that.

Is there a particular reason to move away from 1.0 yet?

Cheers,
    Gary

Re: [Apache Bloodhound] #351: Update versions in setup.py files to 0.4.0 for all bloodhound plugins

Posted by Olemis Lang <ol...@gmail.com>.
On 1/14/13, Apache Bloodhound <bl...@incubator.apache.org> wrote:
> #351: Update versions in setup.py files to 0.4.0 for all bloodhound plugins
> ------------------------+-----------------------
>   Reporter:  gjm        |      Owner:  gjm
>       Type:  task       |     Status:  closed
>   Priority:  major      |  Milestone:  Release 4
>  Component:  dashboard  |    Version:
> Resolution:  fixed      |   Keywords:
> ------------------------+-----------------------
> Changes (by gjm):
>
>  * status:  accepted => closed
>  * resolution:   => fixed
>
>
> Comment:
>
>  r1432848 fixes for dashboard, multiproduct and theme
>
>  r1432859 fixes for search (apparently a downgrade)
>

Is TRAC_VERSION file in trunk up to date ?

-- 
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article:

Re: [Apache Bloodhound] #351: Update versions in setup.py files to 0.4.0 for all bloodhound plugins

Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#351: Update versions in setup.py files to 0.4.0 for all bloodhound plugins
------------------------+-----------------------
  Reporter:  gjm        |      Owner:  gjm
      Type:  task       |     Status:  closed
  Priority:  major      |  Milestone:  Release 4
 Component:  dashboard  |    Version:
Resolution:  fixed      |   Keywords:
------------------------+-----------------------
Changes (by gjm):

 * status:  accepted => closed
 * resolution:   => fixed


Comment:

 r1432848 fixes for dashboard, multiproduct and theme

 r1432859 fixes for search (apparently a downgrade)

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/351#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

Re: [Apache Bloodhound] #351: Update versions in setup.py files to 0.4.0 for all bloodhound plugins

Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#351: Update versions in setup.py files to 0.4.0 for all bloodhound plugins
------------------------+-----------------------
  Reporter:  gjm        |      Owner:  gjm
      Type:  task       |     Status:  accepted
  Priority:  major      |  Milestone:  Release 4
 Component:  dashboard  |    Version:
Resolution:             |   Keywords:
------------------------+-----------------------
Changes (by gjm):

 * owner:  nobody => gjm
 * status:  new => accepted


-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/351#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker