Changes

== Bugzilla Roadmap ===== Introduction ===The trunk is open for development for ~6 months, meaning that we accept bug fixes, enhancements, new features and risky code changes during this time. But 6 months is a ''short'' period and if we want something to be done on time when we freeze for the next release, some coordination is required.

==API = So why this roadmap? ===Well, to quickly summarize the main reasons, we could say:* There is nothing more frustrating than working on a patch which will get no attention and will remain in the review queue for months, if not for years. Having clear objectives about what we want in the coming months will permit us to avoid such unfortunate situations. If we want something, we won't let it languish in the queue for months.* Everyone is busy, but everyone wants to see things being done, and preferably as quickly as possible. Having clear objectives will make our work more efficient, as we know where the few free hours we have for writing patches will be most useful. This follows closely from the previous point, and we mention it here because we want to use our precious free time efficiently.* Having deadlines and assigned developers will also offer a better coordination between developers. Working on some fields which conflict with someone else's work is again a waste of time, and having to unbitrot patches may take as long as writing the patch for the first time. Also, having an assigned developer per field should help in getting the work done, especially if this developer is a reviewer too. Indeed, ''assigned'' doesn't mean that he has to do the job alone, but that he is the person to contact when someone is interested in helping. He should also be able to say what work remains in the area of responsibility, and how far we are along in the process.

You can also look at the old * [p3] responsive design** tables for layout --> divs** show_bug only* [Bugzillap3] user roles / show_bug alternatives** required:Roadmap_3.0 | roadmap for Bugzilla 3.0]responsive design** initially javascript to hide/show selected fields* [p3] migrate from yui2 to yui3 or jquery** propose splitting the bug and the [[Bugzillawork:Roadmap_3.2 | roadmap *** a line-for Bugzilla 3.2-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 = Our priorities ===Here is what you were waiting for: the roadmap for Bugzilla 3.4 and beyond. Tasks reported in the table are not ordered by priority as some of them may be relatively independent. The first Bugzilla version which has the corresponding features implemented is also indicated.

{| class="fullwidth-table" border="1" cellpadding="10" cellspacing="0"* [p1] memcached!Task* [p1] api throttling!Related bugs** required: memcache!Fully implemented on** cache REST requests with memcache!Assigned developer(s)!Requirements|** prevent too-frequent polling with identical requests, and accidental DDOS! colspan="** a 5" | Bugzilla 3.4minute cache of duplicate bzapi requests would have a 25% hit rate|-| <span id="timezone">Allow users to choose what time zone to display times in</span>| <strike>** [https://bugzilla.mozilla.org/show_bug.cgi?id=182238 Bug&nbsp;182238p2]</strike>new relic integration| August 26, 2008| LpSolit| none|-| <span id="webservices">Implement Bug.search() * build standard system for WebServices</span>logging| <strike>[https://bugzilla.mozilla.org/show_bug.cgi?id=398281 Bug&nbsp;398281]</strike>| January 22** currently just write to apache's error log, 2009| mkanat| noneaccess via syslog|-| <span id="custom">Ability ** need to restrict custom fields to products log all api calls, which aren't currently visible (like flagsPOSTs)</span>| <strike>[https://bugzilla.mozilla.org/show_bug.cgi** log to database table, in background process?id=371995 Bug&nbsp;371995]</strike>| February 8, 2009| mkanat| none|-| <span id="enter_bug">Improvements for enter_bug's UI</span>| <strike>* [https://bugzilla.mozilla.org/show_bug.cgi?id=376673 Bug&nbsp;376673p4]</strike>| February 11explore consolidation of stylesheets at checksetup time, 2009minimising javascript| mkanat| none|-! colspan=** requires an "5is development" | Bugzilla 3.6setting in localconfig|-| <span id="set_flag">Implement $bug->set_flags() and $attachment->set_flags()</span>| <strike>[https://bugzilla.mozilla.org/show_bug.cgi?id=415541 Bug&nbsp;415541]</strike>| August 5, 2009| LpSolit| none|-! colspanPush BMO Customisations into Upstream Bugzilla ="5" | Bugzilla 4.0|-| <span id="query">Simplify the query.cgi UI</span>| <strike>* [https://bugzilla.mozilla.org/show_bug.cgi?id=450301 Bug&nbsp;450301p1]</strike>inline history| June 6, 2010| pyrzak* [p1] component watching| none|-| <span id="bug.pm">Use Bug.pm to write changes and new bugs to the database</span>| <strike>* [https://bugzilla.mozilla.org/show_bug.cgi?id=122922 Bug&nbsp;122922p2]</strike> <strike>securemail* [https://bugzilla.mozilla.org/show_bug.cgi?id=418342 Bug&nbsp;418342p2]</strike>user activity report| June 18, 2010** needs a webservice endpoint| mkanat| <strike>Implement $bug->set_flag() and $attachment->set_flag()</strike>|-| <span id="ws-bugupdate">Bug.update support in WebServices</span>| <strike>* [https://bugzilla.mozilla.org/show_bug.cgi?id=415813 Bug&nbsp;415813p2]</strike>patchreader| July 12, 2010| mkanat, dkl** uninit warnings need to be resolved first| <strike>* [https://bugzilla.mozilla.org/show_bug.cgi?id=418342 Bugzilla::Bug::set_allp3]</strike>|-! colspan="5" | Bugzilla 4profile.2creation_ts|-| <span id="search.pm">Search.pm should not depend on the CGI</span>| <strike>* [https://bugzilla.mozilla.org/show_bug.cgi?id=398308 Bug&nbsp;398308p3]</strike>| July 15, 2010| mkanat| none|-| <span id="retire">Retire old versions, components administration reports and milestones</span>tools| <strike>* [https://bugzilla.mozilla.org/show_bug.p4] migrate tools from command line scripts to cgi?id=77193 Bug&nbsp;77193]</strike>| August 30, 2010| dkl| none|-! colspan=** create an "5admin's toolbox" | Bugzilla 4.next|-?| <span id="object.pm">Most Bugzilla modules should use Object.pm</span>| [https://bugzilla.mozilla.org/show_bug.cgi?id=355838 Bug&nbsp;355838] * [https://bugzilla.mozilla.org/show_bug.cgi?id=297791 Bug&nbsp;297791p4]project honeypot integration| ---| LpSolit, mkanat| <strike>* [[#bug.pm|Use Bug.pm to write changes and new bugs to the databasep4]]</strike>|anti-spam| <span id="webservices">Improvements to WebServices</span>| [https://bugzilla.mozilla.org/show_bug.cgi?id=278032 Bug&nbsp;278032]| ---| Noura| [[#object.pm|Most Bugzilla modules should use Object.pm]]|-| <span id="branches">Bugzilla needs to deal better with branches<Community Engagement /span>| [https://bugzilla.mozilla.org/show_bug.cgi?idEcosystem ==55970 Bug&nbsp;55970]| ---* focus on documentation| mkanat* identify a point of contact for new contributors (mentors)| none* reach out to known contributors|-* clearly set expectations (code review times, etc)| <span id="hci">Improve Bugzilla usability</span>* regular meetings with agendas and summaries| [https://bugzilla.mozilla.org/show_bug.cgi?id=490786 Bug&nbsp;490786]* code review guidelines, especially with regards to new contributors| ---* extensions and dashboards database| ---** proper database app, with filters etc| none* investigate migrating off mod_perl to fastcgi|-** revisit plack| <span id="mssql">MS-SQL Support</span>* documentation| [https:** separation of documentation into target audiences (user guide, admin//bugzilla.mozilla.org/show_bug.cgi?id=285122 Bug&nbsp;285122]install guide, hacking guide, api consumer guide)| ---** hosting of both upstream and site specific docs| mockodin| none|-| <span id="inter-bugzilla">Inter-You can also look at the old roadmaps for Bugzilla Integration Capabilities</span>| [https[Bugzilla://bugzillaRoadmap_3.mozilla0|3.org/show_bug.cgi?id=123130 Bug&nbsp;1231300]<br> [https://bugzilla.mozilla.org/show_bug.cgi?id=134294 Bug&nbsp;134294]| ---| alexeiser, dkl| <strike>[[#bugBugzilla:Roadmap_3.pm2|Use Bug3.pm to write changes and new bugs to the database2]]</strike><br>, and [[#webservices|Improvements to WebServices]]|-| <span id="index.cgi">Make Bugzilla's index.cgi (home page) useful for logged-in users</span>| [https://bugzillaRoadmap_4.mozilla.org/show_bug.cgi?id=130835 Bug&nbsp;130835]2| ---| pyrzak| none|-| <span id="openid">Support OpenID as a an account source and login verification method</span>| [https://bugzilla4.mozilla.org/show_bug.cgi?id=294608 Bug&nbsp;2946082]| ---| dwm| none|-| <span id="tokens">Use tokens to authenticate email senders</span>| [https://bugzilla.mozilla.org/show_bug.cgi?id=419203 Bug&nbsp;419203]| ---| LpSolit| none|-| <span id="bugmail">Refactor Bugzilla::Bugmail into real objects</span>| [https://bugzilla.mozilla.org/show_bug.cgi?id=301447 Bug&nbsp;301447]| ---| manu| none|-| <span id="defaults">Ability to specify defaults for custom fields</span>| [https://bugzilla.mozilla.org/show_bug.cgi?id=351899 Bug&nbsp;351899]| ---| mkanat| none|}