Bugzilla:Roadmap: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
(Plan for Bugzilla 5.2)
Line 1: Line 1:
= Bugzilla Roadmap =
= Bugzilla Roadmap =


== legend ==
== 5.2 Release ==
 
* Optional CPAN requirements used by BMO
* [p1] Most Important
* Support for Perl 5.10.0
* [p4] Least Important
* Non-invasive enhancements from master
 
* Reversion of multiple aliases
== API ==
 
* [p2] rest redesign
** redesign endpoints, drawing heavily from bzapi's design
** investigate using oauth with api-keys instead of user/pass
 
== UI/UX ==
 
* [p3] responsive design
** tables for layout --> divs
** show_bug only
* [p3] user roles / show_bug alternatives
** required: responsive design
** initially javascript to hide/show selected fields
* [p3] migrate from yui2 to yui3 or jquery
** propose splitting the bug and work:
*** a line-for-line yui2 --> yui3 migration
*** then change to more modern js (csp, etc)
* [p4] show/edit mode
** requires: responsive design
** default to show
** hide fields without values set
** edit to show all fields
* [p4] markdown support
** requires custom markdown library
** limited markdown code only (no html, no image embedding)
** glob has a functional POC
* migrate sandstone skin upstream, make default
** split to match upstream css assets
** replace mozilla branding
** license?
** retain skin specific header and footer, or rework all skins to use sandstone's html?
 
== Performance ==
 
* [p1] memcached
* [p1] api throttling
** required: memcache
** cache REST requests with memcache
** prevent too-frequent polling with identical requests, and accidental DDOS
** a 5 minute cache of duplicate bzapi requests would have a 25% hit rate
** [p2] new relic integration
* build standard system for logging
** currently just write to apache's error log, access via syslog
** need to log all api calls, which aren't currently visible (POSTs)
** log to database table, in background process?
* [p4] explore consolidation of stylesheets at checksetup time, minimising javascript
** requires an "is development" setting in localconfig
 
== Push BMO Customisations into Upstream Bugzilla ==
* [p1] inline history
* [p1] component watching
* [p2] securemail
* [p2] user activity report
** needs a webservice endpoint
* [p2] patchreader
** uninit warnings need to be resolved first
* [p3] profile.creation_ts
* [p3] administration reports and tools
* [p4] migrate tools from command line scripts to cgi
** create an "admin's toolbox"?
* [p4] project honeypot integration
* [p4] anti-spam
 
== Community Engagement / Ecosystem ==
* focus on documentation
* identify a point of contact for new contributors (mentors)
* reach out to known contributors
* clearly set expectations (code review times, etc)
* regular meetings with agendas and summaries
* code review guidelines, especially with regards to new contributors
* extensions and dashboards database
** proper database app, with filters etc
* investigate migrating off mod_perl to fastcgi
** revisit plack
* documentation
** separation of documentation into target audiences (user guide, admin/install guide, hacking guide, api consumer guide)
** hosting of both upstream and site specific docs
 


You can also look at the old roadmaps for Bugzilla [[Bugzilla:Roadmap_3.0|3.0]], [[Bugzilla:Roadmap_3.2|3.2]], and [[Bugzilla:Roadmap_4.2|4.2]].
You can also look at the old roadmaps for Bugzilla [[Bugzilla:Roadmap_3.0|3.0]], [[Bugzilla:Roadmap_3.2|3.2]], and [[Bugzilla:Roadmap_4.2|4.2]].


[[category:Bugzilla|R]]
[[category:Bugzilla|R]]

Revision as of 17:23, 11 May 2017

Bugzilla Roadmap

5.2 Release

  • Optional CPAN requirements used by BMO
  • Support for Perl 5.10.0
  • Non-invasive enhancements from master
  • Reversion of multiple aliases

You can also look at the old roadmaps for Bugzilla 3.0, 3.2, and 4.2.

Retrieved from "https://wiki.allizom.org/index.php?title=Bugzilla:Roadmap&oldid=1170992"