Development:Overview - Revision history

Jonathannewman: /* The key players */

2011-03-30T20:21:11Z

The key players

← Older revision		Revision as of 20:21, 30 March 2011
Line 7:		Line 7:
	;Moodle HQ: The mostly-Australian team of developers who are directly funded by the Moodle project to work full-time on core developments. Developers include Martin Dougiamas (moodler), Eloy Lafuente (stronk7), Petr Skoda (skodak), Mathieu Petit-Clair (scyrma), Nicolas Connault, Donsheng Cai, Jérôme Mouneyrac, Helen Foster (wildgirl) and occasionally Jamie Pratt (jamiesensei). Pictures of everyone can be found here: http://moodle.com/hq/.		;Moodle HQ: The mostly-Australian team of developers who are directly funded by the Moodle project to work full-time on core developments. Developers include Martin Dougiamas (moodler), Eloy Lafuente (stronk7), Petr Skoda (skodak), Mathieu Petit-Clair (scyrma), Nicolas Connault, Donsheng Cai, Jérôme Mouneyrac, Helen Foster (wildgirl) and occasionally Jamie Pratt (jamiesensei). Pictures of everyone can be found here: http://moodle.com/hq/.

	;Catalyst: The team of developers working for Moodle clients via Catalyst Ltd in New Zealand, resulting in a lot of core development. ~~Developers~~ include Martin Langhoff, Penny Leach (mjollnir), ~~Matt Clarkson~~, and ~~Donal McMullan~~.		;Catalyst: The team of developers working for Moodle clients via Catalyst Ltd in New Zealand, resulting in a lot of core development. Core developers include Matt Clarkson, Peter Bulmer, Aaron Barnes, Jonathan Harker, Francois Marier, Piers Harding, Dan Marsden, and Simon Coggins. The legacy of former Catalyst core developers includes Martin Langhoff, Penny Leach (mjollnir), Donal McMullan, Luke Hudson, and Jonathan Newman.

	;Open University: The team of developers working on Moodle implementations at Open University in the UK. Developers include Tim Hunt, Sam Marshall, Nick Freear, Thanh Le and Jenny Gray.		;Open University: The team of developers working on Moodle implementations at Open University in the UK. Developers include Tim Hunt, Sam Marshall, Nick Freear, Thanh Le and Jenny Gray.

Tsala: /* Release cycles */ support for stable versions copied from http://moodle.org/mod/forum/discuss.php?d=168021

2011-02-07T15:11:27Z

Release cycles: support for stable versions copied from http://moodle.org/mod/forum/discuss.php?d=168021

← Older revision		Revision as of 15:11, 7 February 2011
Line 33:		Line 33:

	Then it all starts again!		Then it all starts again!

			Moodle HQ is committed to supporting the two most recent stable versions. That is, at any point in time:

			* We work on the next version but don't provide production support
			* We support the most recent stable version with constant bug fixes
			* We support the previous recent stable version, but mostly only serious bugs and security issues
			* We don't support any older versions

	==Quality control==		==Quality control==

Ink-ru: /* See also */ Interwiki

2010-04-21T18:08:08Z

Tsala: category edits

2009-10-19T14:39:03Z

category edits

← Older revision		Revision as of 14:39, 19 October 2009
Line 157:		Line 157:

	[[Category:Developer\|Overview]]		[[Category:Developer\|Overview]]
	[[Category:Quality Assurance]]		[[Category:Quality Assurance\|Overview]]
	[[Category:Processes]]		[[Category:Processes\|Overview]]

Tsala: Category:Processes

2009-10-19T14:37:03Z

Category:Processes

← Older revision		Revision as of 14:37, 19 October 2009
Line 158:		Line 158:
	[[Category:Developer\|Overview]]		[[Category:Developer\|Overview]]
	[[Category:Quality Assurance]]		[[Category:Quality Assurance]]
			[[Category:Processes]]

Tsala: Reverted edits by Liaolliso (Talk) to last version by TimHunt

2009-06-23T07:05:06Z

Reverted edits by Liaolliso (talk) to last version by Tim Hunt

← Older revision		Revision as of 07:05, 23 June 2009
Line 34:		Line 34:
	Then it all starts again!		Then it all starts again!

	==~~质量控制~~==		==Quality control==

	~~焦点问题跟踪是可持续质量控制过程的一个重要部分~~. ~~它涉及到问题~~(bugs)~~的报告，改进和新特性的想法~~. ~~不像大多数的私有软件程序，Moodle 焦点问题的报告信息和追踪信息对任何人都是开放的~~. Moodle ~~的焦点追踪系统叫做~~ [[Tracker]].		Issue tracking is an important part of a continuous quality control process. It involves reporting of problems (bugs), ideas for improvement and new features. Unlike most proprietary software programs, Moodle issue reporting and tracking information is open to everyone. Moodle's issue tracking system is called the [[Tracker]].

	~~当需要测试的时候，所有的Moodle 使用者都被鼓励成为活跃的参与者~~. ~~任何拥有Tracker用户帐号的人都可以创建，查看，评论，投票和监控bugs~~.		All Moodle users are encouraged to be active participants when it comes to testing. Anyone with a Tracker user account can create, view, comment on, vote, and watch bugs.

	===~~测试者~~===		===Testers===

	~~测试者主要负责校验由开发者做的一些改变的准确性~~. ~~测试者根据他们的领域经验选择他们想测试的bug~~,~~并使用QA~~ Assignee field ~~来证明他们的测试身份~~.		Testers are responsible for verifying the accuracy of changes made by developers. Testers choose which bugs they want to test, according to their area of expertise, and use the QA Assignee field to identify themselves as the tester.

	~~如果bug通过了测试，测试者就把bug的状态从~~'resolved'~~更改为~~'closed'. ~~如果没有通过测试，或者bug修改的不完整，测试者将重新打开这个bug~~.		If the bug passes testing, then the tester changes the status of the bug from 'resolved' to 'closed'. If the bug fails testing, or if the fix is incomplete, then the tester reopens the bug.

	~~当针对某个特定版本的所有~~"blocker" ~~bug都关闭的时候，一个Moodle的发行版被认为是准备好了~~.		A Moodle release will be deemed ready when all "blocker" bugs fixed for a particular version have been closed.

	~~===每周的代码检查===~~

	~~每个星期二(所有的时区), 测试者和核心开发者将停止开发新代码，并着重去检查在上周对稳定发行版本的改变(从Code Level和Interface Level去检查).~~		===Weekly Code Review===

	~~这个过程目的在于提高最新下载包的质量以及发现任何可能由于修复老bug而产生的新bug~~.		Every Tuesday (all time zones), testers and core developers stop developing new code and focus on reviewing changes made to the stable releases in the past week (both at a code level and an interface level).

	~~最新的稳定包被标记为 MOODLE_19_WEEKLY (这些标记在每周的代码检查结束后将被更新)~~.		This process is intended to improve the quality of the latest download packages and to catch any new bugs that might have been created while fixing old ones.

	参考 [[Development:Weekly Code Review]] ~~以获得更多细节~~.		The latest stable packages are tagged as MOODLE_19_WEEKLY (these tags are updated after the weekly review is over).

			See [[Development:Weekly Code Review]] for more details.

	==Coding Standards==		==Coding Standards==

Liaolliso: /* Quality control */

2009-06-23T06:10:02Z

Quality control

← Older revision		Revision as of 06:10, 23 June 2009
Line 34:		Line 34:
	Then it all starts again!		Then it all starts again!

	==~~Quality control~~==		==质量控制==

	~~Issue tracking is an important part of a continuous quality control process~~. ~~It involves reporting of problems~~ (bugs)~~, ideas for improvement and new features~~. ~~Unlike most proprietary software programs, Moodle issue reporting and tracking information is open to everyone~~. Moodle~~'s issue tracking system is called the~~ [[Tracker]].		焦点问题跟踪是可持续质量控制过程的一个重要部分. 它涉及到问题(bugs)的报告，改进和新特性的想法. 不像大多数的私有软件程序，Moodle 焦点问题的报告信息和追踪信息对任何人都是开放的. Moodle 的焦点追踪系统叫做 [[Tracker]].

	~~All Moodle users are encouraged to be active participants when it comes to testing~~. ~~Anyone with a Tracker user account can create, view, comment on, vote, and watch bugs~~.		当需要测试的时候，所有的Moodle 使用者都被鼓励成为活跃的参与者. 任何拥有Tracker用户帐号的人都可以创建，查看，评论，投票和监控bugs.

	===~~Testers~~===		===测试者===

	~~Testers are responsible for verifying the accuracy of changes made by developers~~. ~~Testers choose which bugs they want to test~~, ~~according to their area of expertise, and use the QA~~ Assignee field ~~to identify themselves as the tester~~.		测试者主要负责校验由开发者做的一些改变的准确性. 测试者根据他们的领域经验选择他们想测试的bug,并使用QA Assignee field 来证明他们的测试身份.

	~~If the bug passes testing, then the tester changes the status of the bug from~~ 'resolved' to 'closed'. ~~If the bug fails testing, or if the fix is incomplete, then the tester reopens the bug~~.		如果bug通过了测试，测试者就把bug的状态从'resolved'更改为'closed'. 如果没有通过测试，或者bug修改的不完整，测试者将重新打开这个bug.

	~~A Moodle release will be deemed ready when all~~ "blocker" ~~bugs fixed for a particular version have been closed~~.		当针对某个特定版本的所有"blocker" bug都关闭的时候，一个Moodle的发行版被认为是准备好了.

			===每周的代码检查===

	~~===Weekly Code Review===~~		每个星期二(所有的时区), 测试者和核心开发者将停止开发新代码，并着重去检查在上周对稳定发行版本的改变(从Code Level和Interface Level去检查).

	Every Tuesday (all time zones), testers and core developers stop developing new code and focus on reviewing changes made to the stable releases in the past week (both at a code level and an interface level).		这个过程目的在于提高最新下载包的质量以及发现任何可能由于修复老bug而产生的新bug.

	~~This process is intended to improve the quality of the latest download packages and to catch any new bugs that might have been created while fixing old ones~~.		最新的稳定包被标记为 MOODLE_19_WEEKLY (这些标记在每周的代码检查结束后将被更新).

	~~The latest stable packages are tagged as MOODLE_19_WEEKLY (these tags are updated after the weekly review is over).~~		参考 [[Development:Weekly Code Review]] 以获得更多细节.

	~~See~~ [[Development:Weekly Code Review]] ~~for more details~~.

	==Coding Standards==		==Coding Standards==

TimHunt: Reverted edits by Liaolliso (Talk) to last version by Stronk7

2009-06-23T05:59:25Z

Reverted edits by Liaolliso (talk) to last version by Eloy Lafuente (stronk7)

← Older revision		Revision as of 05:59, 23 June 2009
Line 1:		Line 1:
	~~很多人问moodle的开发是怎么操作的~~.~~本页面将给你一个概览，帮助你理解许多其它的开发文档。~~		A lot of people ask how the development of Moodle operates. This page should give you a working overview that should help in understanding a lot of other developer documentation.

	==~~关键角色~~==		==The key players==

	;Martin Dougiamas: Martin ~~是Moodle项目的开发负责人~~. ~~通常他试着推行民主，推广精华知识，但是他也偶尔在一些事情上做是否可执行决定~~.		;Martin Dougiamas: Martin is the lead developer of Moodle. Generally he tries to facilitate democracy and meritocracy but occasionally has to make executive decisions on things.

	;Moodle HQ: ~~大部分是澳大利亚人的一个开发者团队，由Moodle项目提供资金，进行全职的moodle核心开发~~. ~~团队成员包括~~ Martin Dougiamas (moodler), Eloy Lafuente (stronk7), Petr Skoda (skodak), Mathieu Petit-Clair (scyrma), Nicolas Connault, Donsheng Cai, Jérôme Mouneyrac, Helen Foster (wildgirl) and occasionally Jamie Pratt (jamiesensei). ~~每个人的头像可以在这里找到~~: http://moodle.com/hq/.		;Moodle HQ: The mostly-Australian team of developers who are directly funded by the Moodle project to work full-time on core developments. Developers include Martin Dougiamas (moodler), Eloy Lafuente (stronk7), Petr Skoda (skodak), Mathieu Petit-Clair (scyrma), Nicolas Connault, Donsheng Cai, Jérôme Mouneyrac, Helen Foster (wildgirl) and occasionally Jamie Pratt (jamiesensei). Pictures of everyone can be found here: http://moodle.com/hq/.

	;Catalyst: ~~一个在新西兰的Catalyst Lid的开发团队，为Moodle的客户工作，进行许多核心开发。团队成员包括~~ Martin Langhoff, Penny Leach (mjollnir), Matt Clarkson, and Donal McMullan.		;Catalyst: The team of developers working for Moodle clients via Catalyst Ltd in New Zealand, resulting in a lot of core development. Developers include Martin Langhoff, Penny Leach (mjollnir), Matt Clarkson, and Donal McMullan.

	;Open University: ~~在英国Open University的一个主要负责Moodle安装实施的开发团队~~. ~~团队成员包括~~ Tim Hunt, Sam Marshall, Nick Freear, Thanh Le and Jenny Gray.		;Open University: The team of developers working on Moodle implementations at Open University in the UK. Developers include Tim Hunt, Sam Marshall, Nick Freear, Thanh Le and Jenny Gray.

	~~现在还有许多其它的人通过不同的方式来为moodle项目做贡献~~, ~~上面这些只是主要负责核心开发的团队。参考~~[http://moodle.org/cvs the full list of people with write access to Moodle]		There are many other people contributing to Moodle in many ways, these are just the main groups currently working on core development. See [http://moodle.org/cvs the full list of people with write access to Moodle]

	==Moodle 版本==		==Moodle versions==

	~~Moodle大概每6个月或更长时间发行一个主版本，没有固定的日程。每个主版本将使Moddle的主版本号增加0~~.1. ~~在每个稳定分支上的次版本~~ (~~没有新的特性增加~~, ~~只是一些bug修改~~) ~~可能在任何时间发生~~,~~不管在任何时候，只要足够的bug修复经过验证即可~~.~~完整的细节可以在~~ [[Release notes]] 看到.		Moodle major releases occur roughly 6 months or more apart, on no fixed schedule. Each major release increments the version number by 0.1. Minor releases (no new features, just fixes) on each stable branch can occur at any time, whenever enough bug fixes have been made to justify them. The full details can be seen in the [[Release notes]].

	~~目前的开发版可以在CVS的trunk~~(i.e. HEAD)~~上找到~~, ~~稳定的分支版本将会分散出现在每个主版本中~~(e.g. MOODLE_18_STABLE).		The current development version is always on the trunk of CVS (i.e. HEAD), while stable branches are split off for every major version (e.g. MOODLE_18_STABLE).

	~~==我们怎样开发 Roadmap==~~

	[[Roadmap]] 列出将在下个版本中开发的特性. 这个列表主要源于在Moodle[[Tracker]]里在一些焦点问题上的大量投票，所以请为你想要的特性投票! 其它的包括公开讨论以及在Moodle Moots和Moodle论坛的特性请求也会对此列表有所影响。		==How we develop the Roadmap==

	~~==发行周期==~~		The [[Roadmap]] lists the features being developed for the next version. This list is derived mostly from the issues with large numbers of votes in the Moodle [[Tracker]], so please vote for what you want! Other influences include general discussion and feature requests at Moodle Moots and in the Moodle forums.

	~~通常一个周期这样工作:~~		==Release cycles==
	;Rapid Development: 几个月长时间的开发，主要为Moodle的HEAD版本添加代码.同时, 所有不涉及数据库改变以及基本核心改变的bug修复代码将会移植到最新的两到三个稳定分支版本.
	;Head Freeze: 在某种情况下，Martin Dougiamas 可能会宣布冻结新工作而去稳定核心代码. 所有的数据库改变和主要核心的改变需要获得Martin的明确允许. 所有的开发者应该封装他们在新特性上的工作，并修复在新代码中的bug。这段时间可能会有1到2个星期.
	;Beta period: 一旦HEAD版本变的相当稳定, Martin 将宣布一个BETA版本，被标记为MOODLE_XX_BETA (e.g. MOODLE_19_BETA).安装包会每日从最新版本生成以便通过跟踪进行更广泛的测试和反馈。Freeze将继续，测试和bug修复也将继续. 这个测试时间将花费2到6个星期
	;Major release: 当核心代码通过所有测试，我们就可以转向这个版本，MOODLE_XX_BETA标记将会被用来标记当前version作为一个分支，然后一个名叫MOODLE_XX_STABLE的新的稳定分支就产生了。包创建了，该发行版也将会被宣布。

	~~然后，所有的又按照这个周期重新开始~~!		Generally a cycle works like this:
			;Rapid Development:Long period of several months adding code to the HEAD version of Moodle. At the same time, all fixes that don't involve database changes or radical core changes are backported to the last two or three stable branches.
			;Head Freeze:At some point Martin Dougiamas declares a freeze on new work for a while to stabilise the core. All database changes and all major core changes need to have explicit permission from Martin. All developers should be wrapping up work on new features and fixing bugs in new code. This period may be 1 or 2 weeks.
			;Beta period:Once the HEAD version becomes fairly stable, Martin declares a BETA version and this point is marked on HEAD as MOODLE_XX_BETA (e.g. MOODLE_19_BETA). Install packages are generated daily from the latest version for wider testing and feedback via the tracker. The freeze continues, testing and bug fixing continues. This testing period may be anywhere from 2 to 6 weeks.
			;Major release:When the core code passes all the testing we can throw at it, the MOODLE_XX_BETA flag is moved up to mark the current point as a branch point, and a new stable branch named MOODLE_XX_STABLE is created. Packages are created, and the release is announced.

			Then it all starts again!

	==Quality control==		==Quality control==

Liaolliso: /* 发行周期 */

2009-06-23T05:32:59Z

发行周期

← Older revision		Revision as of 05:32, 23 June 2009
Line 27:		Line 27:
	通常一个周期这样工作:		通常一个周期这样工作:
	;Rapid Development: 几个月长时间的开发，主要为Moodle的HEAD版本添加代码.同时, 所有不涉及数据库改变以及基本核心改变的bug修复代码将会移植到最新的两到三个稳定分支版本.		;Rapid Development: 几个月长时间的开发，主要为Moodle的HEAD版本添加代码.同时, 所有不涉及数据库改变以及基本核心改变的bug修复代码将会移植到最新的两到三个稳定分支版本.
	;Head Freeze: 在某种情况下，Martin Dougiamas 可能会宣布冻结新工作而去稳定核心代码. 所有的数据库改变和主要核心的改变需要获得Martin的明确允许. 所有的开发者应该封装他们在新特性上的工作，并修复在新代码中的bug。这段时间可能会有1到2个星期.~~（吃饭中，保存一下）~~		;Head Freeze: 在某种情况下，Martin Dougiamas 可能会宣布冻结新工作而去稳定核心代码. 所有的数据库改变和主要核心的改变需要获得Martin的明确允许. 所有的开发者应该封装他们在新特性上的工作，并修复在新代码中的bug。这段时间可能会有1到2个星期.
	;Beta period: 一旦HEAD版本变的相当稳定, Martin 将宣布一个BETA版本，被标记为MOODLE_XX_BETA (e.g. MOODLE_19_BETA).安装包会每日从最新版本生成以便通过跟踪进行更广泛的测试和反馈。Freeze将继续，测试和bug修复也将继续. 这个测试时间将花费2到6个星期		;Beta period: 一旦HEAD版本变的相当稳定, Martin 将宣布一个BETA版本，被标记为MOODLE_XX_BETA (e.g. MOODLE_19_BETA).安装包会每日从最新版本生成以便通过跟踪进行更广泛的测试和反馈。Freeze将继续，测试和bug修复也将继续. 这个测试时间将花费2到6个星期
	;Major release: 当核心代码通过所有测试，我们就可以转向这个版本，MOODLE_XX_BETA标记将会被用来标记当前version作为一个分支，然后一个名叫MOODLE_XX_STABLE的新的稳定分支就产生了。包创建了，该发行版也将会被宣布。		;Major release: 当核心代码通过所有测试，我们就可以转向这个版本，MOODLE_XX_BETA标记将会被用来标记当前version作为一个分支，然后一个名叫MOODLE_XX_STABLE的新的稳定分支就产生了。包创建了，该发行版也将会被宣布。

Liaolliso: /* 发行周期 */

2009-06-23T05:24:15Z

发行周期

← Older revision		Revision as of 05:24, 23 June 2009
Line 27:		Line 27:
	通常一个周期这样工作:		通常一个周期这样工作:
	;Rapid Development: 几个月长时间的开发，主要为Moodle的HEAD版本添加代码.同时, 所有不涉及数据库改变以及基本核心改变的bug修复代码将会移植到最新的两到三个稳定分支版本.		;Rapid Development: 几个月长时间的开发，主要为Moodle的HEAD版本添加代码.同时, 所有不涉及数据库改变以及基本核心改变的bug修复代码将会移植到最新的两到三个稳定分支版本.
	;Head Freeze: 在某种情况下，Martin Dougiamas 可能会宣布冻结新工作而去稳定核心代码. 所有的数据库改变和主要核心的改变需要获得Martin的明确允许. ~~所有的开发者应该封装他们在新特性上的工作，并修复在新代码中的bug。这段时间可能会有一到两个星期~~.（吃饭中，保存一下）		;Head Freeze: 在某种情况下，Martin Dougiamas 可能会宣布冻结新工作而去稳定核心代码. 所有的数据库改变和主要核心的改变需要获得Martin的明确允许. 所有的开发者应该封装他们在新特性上的工作，并修复在新代码中的bug。这段时间可能会有1到2个星期.（吃饭中，保存一下）
	;Beta period:~~Once the HEAD version becomes fairly stable~~, Martin ~~declares a BETA version and this point is marked on HEAD as MOODLE_XX_BETA~~ (e.g. MOODLE_19_BETA). Install packages are generated daily from the latest version for wider testing and feedback via the tracker. The freeze continues, testing and bug fixing continues. This testing period may be anywhere from 2 to 6 weeks.		;Beta period: 一旦HEAD版本变的相当稳定, Martin 将宣布一个BETA版本，被标记为MOODLE_XX_BETA (e.g. MOODLE_19_BETA).安装包会每日从最新版本生成以便通过跟踪进行更广泛的测试和反馈。Freeze将继续，测试和bug修复也将继续. 这个测试时间将花费2到6个星期
	;Major release:When the core code passes all the testing we can throw at it, the MOODLE_XX_BETA flag is moved up to mark the current point as a branch point, and a new stable branch named MOODLE_XX_STABLE is created. Packages are created, and the release is announced.		;Major release: 当核心代码通过所有测试，我们就可以转向这个版本，MOODLE_XX_BETA标记将会被用来标记当前version作为一个分支，然后一个名叫MOODLE_XX_STABLE的新的稳定分支就产生了。包创建了，该发行版也将会被宣布。

	~~Then it all starts again~~!		然后，所有的又按照这个周期重新开始!

	==Quality control==		==Quality control==

← Older revision		Revision as of 18:08, 21 April 2010
Line 159:		Line 159:
	[[Category:Quality Assurance\|Overview]]		[[Category:Quality Assurance\|Overview]]
	[[Category:Processes\|Overview]]		[[Category:Processes\|Overview]]

			[[ru:Development:Краткий обзор]]