Kernel Plans - Revision history

Sveinung: /* Upstream Linux kernel */

2009-11-15T22:27:51Z

‎Upstream Linux kernel

2009-07-19T07:21:36Z

-cats

2009-04-14T08:12:40Z

Adding category.

2009-04-14T08:11:21Z

Fix.

2009-04-09T21:36:29Z

Fix.

2009-04-07T02:09:23Z

Kernel-plans moved to Kernel Plans: Less odd title

2009-04-05T05:32:47Z

Fix.

2009-04-05T02:52:51Z

‎Patchwork

2009-04-05T02:52:24Z

‎Issues to solve

2009-04-05T02:52:02Z

‎Patchwork

@@ Line 30: / Line 30: @@
 For the next merge window we wish to send:
-* Basic GTA02 support
+* Basic GTA02 support (Update: sent and [http://lists.openmoko.org/pipermail/openmoko-kernel/2009-November/010695.html included])
 * Touchscreen Driver and filters

@@ Line 58: / Line 58: @@
 * http://ozlabs.org/~jk/projects/patchwork/ (Patchwork)
 * http://patchwork.ozlabs.org (Patchwork in use)
 [[Category:Kernel]]

← Older revision		Revision as of 08:12, 14 April 2009
Line 58:		Line 58:
	* http://ozlabs.org/~jk/projects/patchwork/ (Patchwork)		* http://ozlabs.org/~jk/projects/patchwork/ (Patchwork)
	* http://patchwork.ozlabs.org (Patchwork in use)		* http://patchwork.ozlabs.org (Patchwork in use)
		+
		+
		+	[[Category:Kernel]]
		+	[[Category:System Developers]]
		+	[[Category:Application Developer]]

@@ Line 1: / Line 1: @@
-This document explains the current kernel plan for the GTA01/GTA02 kernel. The idea is to share the motivations behind the actual decisions. This is a draft, and the relevant suggestions will be incorporated into it.
+This document explains the current kernel plan for the GTA01/GTA02 kernel. The idea is to share the motivations behind the actual decisions.
-We would like to try this model for one or two months and if we find we are doing something wrong we will update the plans.
+== Current priority ==
 == Patch review process ==
@@ Line 19: / Line 23: @@
 We know that people like forks and code that does not change often, but the linear model is working with upstream kernel (with a lot more people involved of course).
 == Upstream Linux kernel ==
-We should have very basic GTA02 support upstream soon. Once we get to reach this milestone we will check what drivers can be included.
+For the next merge window we wish to send:
 == Issues to solve ==
@@ Line 28: / Line 42: @@
 === Define how to keep track of the upstream kernel ===
-How to up-level the kernel to latest upstream version? (We can delay this decision for a few days).
+How to up-level the kernel to latest upstream version? (We can delay this decision).
 === Patchwork ===

@@ Line 8: / Line 8: @@
 Otherwise we will allow for two days before applying non-trivial patches to allow for community feedback and for feedback from subsystem maintainers. In the ideal case we would get ACKs from other developers (like "i like this patch") but we don't know if we can count on this.
 == Use tags and not forks for stable kernels ==
 We hope that developers actually care about the development branch. If they care, they will helps us reject patches that will likely cause trouble because it will break things. We will also get more testing.
@@ Line 18: / Line 19: @@
 We know that people like forks and code that does not change often, but the linear model is working with upstream kernel (with a lot more people involved of course).
 == Upstream Linux kernel ==

← Older revision		Revision as of 05:32, 5 April 2009
Line 33:		Line 33:
	=== Patchwork ===		=== Patchwork ===

−	~~Patchwork is~~ a ~~nice system.~~ http://patchwork.~~kernel~~.org ~~It does not replace a mailing list~~ but it ~~helps keep track of pending patches~~. ~~We should~~ use it. (~~Not a priority right now~~).	+	We have a patchwork installation ( http://patchwork.openmoko.org ) requested by Angus but it still have some issues. It would be nice to use it in the future.
		+
		+	See:
		+
		+	* http://ozlabs.org/~jk/projects/patchwork/ (Patchwork)
		+	* http://patchwork.ozlabs.org (Patchwork in use)

← Older revision		Revision as of 02:52, 5 April 2009
Line 33:		Line 33:
	=== Patchwork ===		=== Patchwork ===

−	Patchwork is a nice system. http://patchwork.kernel.org It does not replace a mailing list but it helps keep track of pending patches. We should use it.	+	Patchwork is a nice system. http://patchwork.kernel.org It does not replace a mailing list but it helps keep track of pending patches. We should use it. (Not a priority right now).

← Older revision		Revision as of 02:52, 5 April 2009
Line 30:		Line 30:

	How to up-level the kernel to latest upstream version? (We can delay this decision for a few days).		How to up-level the kernel to latest upstream version? (We can delay this decision for a few days).
		+
		+	=== Patchwork ===
		+
		+	Patchwork is a nice system. http://patchwork.kernel.org It does not replace a mailing list but it helps keep track of pending patches. We should use it.

← Older revision		Revision as of 02:52, 5 April 2009
Line 9:		Line 9:
	Otherwise we will allow for two days before applying non-trivial patches to allow for community feedback and for feedback from subsystem maintainers. In the ideal case we would get ACKs from other developers (like "i like this patch") but we don't know if we can count on this.		Otherwise we will allow for two days before applying non-trivial patches to allow for community feedback and for feedback from subsystem maintainers. In the ideal case we would get ACKs from other developers (like "i like this patch") but we don't know if we can count on this.

−	~~=== Patchwork ===~~

−	~~Patchwork is a nice system. http://patchwork.kernel.org It does not replace a mailing list but it helps keep track of pending patches. We should use it.~~

	== Use tags and not forks for stable kernels ==		== Use tags and not forks for stable kernels ==