+(non-binding) On Wed, Dec 10, 2014 at 2:08 AM, John Chambers <[email protected]> wrote:
> +1 binding > > Thanks > > John > On 6 Dec 2014 11:32, "Gary Martin" <[email protected]> wrote: > > > On 04/12/14 04:32, Ryan Ollos wrote: > > > (Resending as this didn't seem to go through last evening) > > > > > > > > >> Hi everyone, > > >> > > >> I would like to initiate the vote for releasing Apache Bloodhound 0.8. > > >> > > >> Please find the change log for this proposed release below: > > >> > > >> * i18n internationalization. > > >> * Quick Create Ticket form sets product based on context and forwards > > >> values to the ticket form when "More fields" is selected. > > >> * Fixed caching issue that prevented product-scope trac-admin > commands > > >> from taking effect immediately. > > >> * Improved presentation of the Products page. > > >> * Improvements to ticket timeline (comments section). > > >> * BloodhoundSearch now supports Whoosh >= 2.5.1 (upgraded from > 2.4.1). > > >> * Fixed several errors in BloodhoundRelations validation logic. > > >> * Bootstrap template for the Roadmap and Edit Product views. > > >> * Bloodhound installer support for MySQL database. > > >> * Product edits were always reported as anonymous. > > >> * Quick Create Ticket displays the last created ticket for a short > time > > >> after it is created. > > >> * Numerous other important fixes and minor enhancements. > > >> > > >> > > >> * Not fixed for this release > > >> * Cache is not properly refreshed for resources including wiki > pages, > > >> components and permissions; leading to stale data being displayed > > >> after INSERTs and DELETEs (#614, #620, #681, #719, #748). > > >> * Products cannot be deleted (#517). > > >> * Duplicate relation is not added when batch modifying tickets > (#761). > > >> * TicketDeleter component can't be used with BloodhoundTheme (#427). > > >> * No product-scope permission checks on the global dashboard (#572). > > >> * Inconsistencies in query views when running PostgreSQL (#730). > > >> > > >> The release candidate artifacts consist of source release as a tar.gz > > >> archive along with the associated MD5 and GPG signature. > > >> These can be found at: > > >> https://dist.apache.org/repos/dist/dev/bloodhound/ > > >> > > >> The archive is based on the tag: > > >> https://svn.apache.org/repos/asf/bloodhound/tags/0.7 > > >> > > >> For this release, the archive differs from the tag in that the Trac > > >> "contrib", "doc" and "sample-plugins" directories has been removed > from > > >> the archive. > > >> The files in that directory currently lack license headers. The issue > > will > > >> be resolved when the Trac 1.0.2 release is integrated for Release 9 of > > >> Bloodhound. > > >> > > >> Please vote: > > >> [ ] +1 Release this package as Apache Bloodhound <version number> > > >> [ ] +0 Don't care > > >> [ ] -1 Do not release this package (please explain) > > >> > > >> The vote is open for a minimum of 72 hours. > > >> > > > > +1 (binding) > > > > Cheers, > > Gary > > > > -- > > > 5 reasons your Hadoop needs WANdisco > <http://www.wandisco.com/system/files/documentation/5-Reasons.pdf> > > Listed on the London Stock Exchange: WAND > <http://www.bloomberg.com/quote/WAND:LN> > > THIS MESSAGE AND ANY ATTACHMENTS ARE CONFIDENTIAL, PROPRIETARY, AND MAY BE > PRIVILEGED. If this message was misdirected, WANdisco, Inc. and its > subsidiaries, ("WANdisco") does not waive any confidentiality or privilege. > If you are not the intended recipient, please notify us immediately and > destroy the message without disclosing its contents to anyone. Any > distribution, use or copying of this e-mail or the information it contains > by other than an intended recipient is unauthorized. The views and > opinions expressed in this e-mail message are the author's own and may not > reflect the views and opinions of WANdisco, unless the author is authorized > by WANdisco to express such views or opinions on its behalf. All email > sent to or from this address is subject to electronic storage and review by > WANdisco. Although WANdisco operates anti-virus programs, it does not > accept responsibility for any damage whatsoever caused by viruses being > passed. > -- *Thimal Kempitiya <http://www.facebook.com/thimalk> UndergraduateDepartment of Computer Science and Engineering University of Moratuwa.*
