ReleaseEngineering:PyCon2010 - Revision history

Lukasblakk: /* Attending */

2010-03-09T00:47:39Z

Attending

← Older revision		Revision as of 00:47, 9 March 2010
Line 3:		Line 3:

	==Attending==		==Attending==
	* catlee [https://wiki.mozilla.org/User:Catlee/~~PyCon2010~~ Notes]		* catlee [https://wiki.mozilla.org/User:Catlee/Pycon2010 Notes]
	* lsblakk (Feb 17th - 25th) [https://wiki.mozilla.org/User:Lukasblakk/PyCon2010 Notes]		* lsblakk (Feb 17th - 25th) [https://wiki.mozilla.org/User:Lukasblakk/PyCon2010 Notes]

2010-03-09T00:46:36Z

← Older revision		Revision as of 00:46, 9 March 2010
Line 3:		Line 3:

	==Attending==		==Attending==
	* catlee		* catlee [https://wiki.mozilla.org/User:Catlee/PyCon2010 Notes]
	* lsblakk (Feb 17th - 25th)		* lsblakk (Feb 17th - 25th) [https://wiki.mozilla.org/User:Lukasblakk/PyCon2010 Notes]

	==Dev Sprints - Possible Bugs==		==Dev Sprints - Possible Bugs==

2010-01-26T13:46:26Z

Dev Sprints - Possible Bugs

← Older revision		Revision as of 13:46, 26 January 2010
Line 34:		Line 34:
	\|-		\|-
	\| {{bug\|519229}} \|\| purge_builds.py shouldn't count the current build directory as "used" \|\| \|\|		\| {{bug\|519229}} \|\| purge_builds.py shouldn't count the current build directory as "used" \|\| \|\|
			\|-
			\| \|\| statusdb (build on top of work done for schedulerdb) \|\| \|\|
	\|}		\|}

2010-01-07T22:46:47Z

Dev Sprints - Possible Bugs

@@ Line 26: / Line 26: @@
 |-
 | {{bug|493988}} || Break factory.py into separate files based on class/function || ||
 |}

2010-01-07T22:39:04Z

Dev Sprints - Possible Bugs

← Older revision		Revision as of 22:39, 7 January 2010
Line 22:		Line 22:
	\|-		\|-
	\| {{bug\|494161}} \|\| all of Mercurial automation should be tagged \|\| low to medium \|\|		\| {{bug\|494161}} \|\| all of Mercurial automation should be tagged \|\| low to medium \|\|
			\|-
			\| {{bug\|485363}} \|\| setting enable_l10n = False in config.py does not completely disable l10n \|\| low to medium \|\|
			\|-
			\| {{bug\|493988}} \|\| Break factory.py into separate files based on class/function \|\| \|\|
	\|}		\|}

2010-01-07T22:36:31Z

Dev Sprints - Possible Bugs

← Older revision		Revision as of 22:36, 7 January 2010
Line 20:		Line 20:
	\|-		\|-
	\| {{bug\|475902}} \|\| buildbot's "Stop build" doesn't work for unit test, aborts current test only \|\| low to medium \|\|		\| {{bug\|475902}} \|\| buildbot's "Stop build" doesn't work for unit test, aborts current test only \|\| low to medium \|\|
			\|-
			\| {{bug\|494161}} \|\| all of Mercurial automation should be tagged \|\| low to medium \|\|
	\|}		\|}

2010-01-07T22:33:00Z

Dev Sprints - Possible Bugs

← Older revision		Revision as of 22:33, 7 January 2010
Line 7:		Line 7:

	==Dev Sprints - Possible Bugs==		==Dev Sprints - Possible Bugs==
	The developer sprints give us an opportunity to work with the Python programming community, both experienced and new developers, on projects that currently aren't getting enough love from the ~~releng~~ team.		The developer sprints give us an opportunity to work with the Python programming community, both experienced and new developers, on projects that currently aren't getting enough love from the RelEng team.

	PyCon's [http://us.pycon.org/2010/sprints/call-for-projects/ Call for Sprints] will get you inspired to come up with ideas for how Mozilla's Release Engineering team can get involved and get the most out of these days.		PyCon's [http://us.pycon.org/2010/sprints/call-for-projects/ Call for Sprints] will get you inspired to come up with ideas for how Mozilla's Release Engineering team can get involved and get the most out of these days.

	Please add any bugs here that you think ~~might be appropriate to put into~~ a developer sprint:		Please add any bugs here that you think could use a developer sprint:

	{\| class='sortable' style="border:1px solid black" border="1px"		{\| class='sortable' style="border:1px solid black" border="1px"

2010-01-07T22:31:21Z

Dev Sprints - Possible Bugs

← Older revision		Revision as of 22:31, 7 January 2010
Line 8:		Line 8:
	==Dev Sprints - Possible Bugs==		==Dev Sprints - Possible Bugs==
	The developer sprints give us an opportunity to work with the Python programming community, both experienced and new developers, on projects that currently aren't getting enough love from the releng team.		The developer sprints give us an opportunity to work with the Python programming community, both experienced and new developers, on projects that currently aren't getting enough love from the releng team.

			PyCon's [http://us.pycon.org/2010/sprints/call-for-projects/ Call for Sprints] will get you inspired to come up with ideas for how Mozilla's Release Engineering team can get involved and get the most out of these days.

	Please add any bugs here that you think might be appropriate to put into a developer sprint:		Please add any bugs here that you think might be appropriate to put into a developer sprint:

2010-01-07T22:28:45Z

PyCon 2010

@@ Line 1: / Line 1: @@
 =PyCon 2010=
 ==Dev Sprints - Possible Bugs==
-{{bug|475902}}
+The developer sprints give us an opportunity to work with the Python programming community, both experienced and new developers, on projects that currently aren't getting enough love from the releng team.

2010-01-07T22:23:32Z

Created page with '=PyCon 2010= ==Dev Sprints - Possible Bugs== {{bug|475902}}'

New page

=PyCon 2010=

==Dev Sprints - Possible Bugs==
{{bug|475902}}