Search results

=== Technical Breaktrough === **Technical

[[Category:User documentation]] [[Category:Documentation]]

[[Category:User documentation]] [[Category:Documentation]]

=== Technical === {{FAQ|question=Where can I find documentation to help me understand Adempiere's code?|answer=See [http://downloads.source

==Documentation== ==Technical Specifications==

=== Technical Requirements === ...maybe a module to manage approval amounts - bringing here the comment for documentation purposes for future improvements:

...gs are prefered but we will switch to IRC if we have to many participants (technical problems) #*The teams will define the details like documentation templates, how acceptance criteria and testcases should be documented etc.

#* Which elements do we use? (scenarios, documentation, tests)''' #*The Technical Team can stick to Jira.

#*Technical team reviews #'''Technical team reviews'''

[22.02.2012 17:36:25] Perez Juarez, Victor: 2.-create the wiki page documentation for the contribution [22.02.2012 17:36:55] Perez Juarez, Victor: 3.- request the peer review to technical team and define a deadline

...#Concept_Template_Suggestion Concept Template Suggestion] as template for documentation/concept that contributions applying for inclusion shall use #*Tobias will add technical details and publish the anouncement on behalf on the PMC teams

Mike will write a document how to get a JIRA account so non-technical people can follow bug fixing ...axa): Karsten, I emailed it to you .. perhaps you can add to a page .. too technical for me!

[9:50:27 AM] Michael Judd: is there a template to assess the FR from a technical and function perspective? I beleive it was proposed for the FT/TT to revie ...rez Juarez: 4.-when the we include the new features then we need create de documentation and example for new fuctionality and release the new versión

[5:25:09 AM] Steven Sackett (Adaxa): too technical for old accountant :-( [5:29:19 AM] Victor Perez Juarez: We are mount booktype to write we documentation

#*Volunteers for Technical [06:51:42] Teodor Sarca: why not starting with those that have documentation + code completed

#**End user documentation is still missing (work in progress, Mark promised to finish it..) #**did a technical review regarding "Sales Management": http://www.adempiere.com/Sales_Managem

#*The TT/FT must have a documentation based on which the decision to integrate a functionality can be taken. ...(http://www.adempiere.com/Functional_Team#Concept_Template) is perhaps too technical biased and not appropriate for functional testing; nevertheless we will con

...luded going forward it must have proper test case scenario, test cases and documentation to be considered. ...n the 3.8.0 release depending on priorities driven by business governance, technical attributes, and the Release Manager.

[06:17:49] Steven Sackett (Adaxa): thats technical .. let u decide :-) [06:44:51] suman ravuri: Adempiere best practices documentation

#*Technical team reviews #'''Technical team reviews'''