Page "Proposals/BEP-0012" was changed by sifa_sensay Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0012?action=diff&version=11> Revision 11 Changes: -------8<------8<------8<------8<------8<------8<------8<------8<-------- Index: Proposals/BEP-0012 ========================================================================= --- Proposals/BEP-0012 (version: 10) +++ Proposals/BEP-0012 (version: 11) @@ -61,25 +61,29 @@ Therefore, each of these features can be added to the BloodhoundThemePlugin as an individual component. This will work well since the client-side functionality (i.e. the JavaScript parts) can be added directly in each individual feature and the server-side request handling can also be handled in individual components within the BloodhoundThemePlugin. Moreover, the user will able to enable/disable each feature since they are implemented individually into the BloodhoundThemePlugin. -== How to Use This Template #howto +== Implementation -<BEPs may include further sections. This is an example.> +Timeframe -Quick edits will consist in following the instructions inside angle brackets (i.e. **<** **>**) . That should be everything needed to write new BEPs. To be more informed about advanced considerations please read the [wiki:/Proposals general content guidelines] and the [wiki:/Proposals/Formats/WikiFormatting WikiFormatting BEP guidelines] . If there is no point in including one of the sections in this document then feel free to remove it. +May 19 – June 8 +• Implement the Keyword Suggest Component for BloodhoundThemePlugin. -== Backwards Compatibility #backwards-compatibility +June 8 – July 8 +• Implement the Autocomplete Users Component for BloodhoundThemePlugin. +• Research the Trac Query API -<All BEPs that introduce backwards incompatibilities must include a section describing these incompatibilities and their severity. The ''BEP'' must explain how to deal with these incompatibilities. ''BEP'' submissions without a sufficient backwards compatibility treatise may be rejected outright. > +July 3 +• Midterm Evaluation -== Reference Implementation #reference-implementation +July 8 – August 8 +• Implement the duplicate ticket feature to work with the ticket Query API +• Add support for the multiproduct API -< The reference implementation **must** be completed before any ''BEP'' is given status **Final**, but it need not be completed before the ''BEP'' is accepted. It is better to finish the specification and rationale first and reach consensus on it before writing code. The final implementation **must** include test code and documentation appropriate for either the wiki pages in ''Bloodhound'' users guide or an specific wiki page in the [http://issues.apache.org/bloodhound issue tracker] . > +August 8 – August 16 +• Refactor code, finish test and documentation -<In order to list tickets related to a given proposal edit sample text provided below by including the appropriate **<BEP number>**. Target tickets have to be tagged with `bep-<BEP number>` keyword. Do not forget to remove curly braces so that the tickets list will be actually rendered.> - -{{{ -[[Widget(TicketQuery, query="keywords=~bep-<BEP number>&col=id&col=summary&col=status&col=priority&col=milestone", title=BEP <BEP number> ticket summary)]] -}}} +August 18 +• Final Evaluation == Resources #resources -------8<------8<------8<------8<------8<------8<------8<------8<--------
-- Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0012> Apache Bloodhound <https://issues.apache.org/bloodhound/> The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'Proposals/BEP-0012' page. If it was not you, please report to .
