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 2012/08/12 00:56:17 UTC

[Apache Bloodhound] #160: Use UNIQUE Bloodhound release number in plugins metadata

#160: Use UNIQUE Bloodhound release number in plugins metadata
-------------------------+-----------------------
 Reporter:  olemis       |      Owner:  nobody
     Type:  enhancement  |     Status:  new
 Priority:  trivial      |  Milestone:  Release 2
Component:  dashboard    |    Version:
 Keywords:  version      |
-------------------------+-----------------------
 In [https://dist.apache.org/repos/dist/release/incubator/bloodhound
 /apache-bloodhound-incubating-0.1.0-RC1.tar.gz first release candidate]
 there's a mismatch between version numbers used in plugins (e.g.
 [http://svn.apache.org/repos/asf/incubator/bloodhound/trunk/bloodhound_dashboard
 dashboard] ''1.0.0'' ,
 [http://svn.apache.org/repos/asf/incubator/bloodhound/trunk/bloodhound_theme
 theme] ''1.0.1'', and
 [http://svn.apache.org/repos/asf/incubator/bloodhound/trunk/bloodhound_multiproduct
 multiproduct] ''0.0.1'') and release number ''0.1.0rc1''. It will be
 easier to use the same version numbers for all of them.

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

Re: [Apache Bloodhound] #160: Use UNIQUE Bloodhound release number in plugins metadata

Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#160: Use UNIQUE Bloodhound release number in plugins metadata
--------------------------+-----------------------
  Reporter:  olemis       |      Owner:  gjm
      Type:  enhancement  |     Status:  review
  Priority:  trivial      |  Milestone:  Release 3
 Component:  dashboard    |    Version:
Resolution:               |   Keywords:  version
--------------------------+-----------------------

Comment (by gjm):

 This seems fine although I am not sure of the reason for keeping the
 historical versions. This also either needs to be turned into a recurring
 task or part of a release script.

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

Re: [Apache Bloodhound] #160: Use UNIQUE Bloodhound release number in plugins metadata

Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#160: Use UNIQUE Bloodhound release number in plugins metadata
--------------------------+-----------------------
  Reporter:  olemis       |      Owner:  gjm
      Type:  enhancement  |     Status:  review
  Priority:  trivial      |  Milestone:  Release 3
 Component:  dashboard    |    Version:
Resolution:               |   Keywords:  version
--------------------------+-----------------------

Comment (by gjm):

 r1412030 updates the versions to 0.3.0

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

Re: [Apache Bloodhound] #160: Use UNIQUE Bloodhound release number in plugins metadata

Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#160: Use UNIQUE Bloodhound release number in plugins metadata
--------------------------+-----------------------
  Reporter:  olemis       |      Owner:  nobody
      Type:  enhancement  |     Status:  new
  Priority:  trivial      |  Milestone:  Release 2
 Component:  dashboard    |    Version:
Resolution:               |   Keywords:  version
--------------------------+-----------------------

Comment (by olemis):

 Attached patched are aimed at setting package version number to ''0.2.0''
 in ''Bloodhound'' plugins ''setup.py'' files

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

Re: [Apache Bloodhound] #160: Use UNIQUE Bloodhound release number in plugins metadata

Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#160: Use UNIQUE Bloodhound release number in plugins metadata
--------------------------+-----------------------
  Reporter:  olemis       |      Owner:  gjm
      Type:  enhancement  |     Status:  review
  Priority:  trivial      |  Milestone:  Release 3
 Component:  dashboard    |    Version:
Resolution:               |   Keywords:  version
--------------------------+-----------------------
Changes (by olemis):

 * owner:  olemis => gjm
 * status:  accepted => review


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

Re: [Apache Bloodhound] #160: Use UNIQUE Bloodhound release number in plugins metadata

Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#160: Use UNIQUE Bloodhound release number in plugins metadata
--------------------------+-----------------------
  Reporter:  olemis       |      Owner:  gjm
      Type:  enhancement  |     Status:  closed
  Priority:  trivial      |  Milestone:  Release 3
 Component:  dashboard    |    Version:
Resolution:  fixed        |   Keywords:  version
--------------------------+-----------------------
Changes (by gjm):

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


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

Re: [Apache Bloodhound] #160: Use UNIQUE Bloodhound release number in plugins metadata

Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#160: Use UNIQUE Bloodhound release number in plugins metadata
--------------------------+-----------------------
  Reporter:  olemis       |      Owner:  olemis
      Type:  enhancement  |     Status:  accepted
  Priority:  trivial      |  Milestone:  Release 2
 Component:  dashboard    |    Version:
Resolution:               |   Keywords:  version
--------------------------+-----------------------
Changes (by olemis):

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


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

Re: [Apache Bloodhound] #160: Use UNIQUE Bloodhound release number in plugins metadata

Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#160: Use UNIQUE Bloodhound release number in plugins metadata
--------------------------+-----------------------
  Reporter:  olemis       |      Owner:  gjm
      Type:  enhancement  |     Status:  review
  Priority:  trivial      |  Milestone:  Release 3
 Component:  dashboard    |    Version:
Resolution:               |   Keywords:  version
--------------------------+-----------------------

Comment (by olemis):

 Replying to [comment:4 gjm]:
 > This seems fine although I am not sure of the reason for keeping the
 historical versions.

 I'm not sure I understand what you mean .

 > This also either needs to be turned into a recurring task or part of a
 release script.

 fwiw ... +1

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