[U-Boot-Users] Enforcement of coding standards

[Wolfgang Denk]

In message <20030307083407.GN16290 at pengutronix.de> you wrote:
>
> Understandable - would it help if we had something like a stable and
> unstable branch? 

I tried this twice (internally). It does not help. I prefer  to  have
one tree, and to stabilize it for each "release".

> I mean, the problem is that for the short time you are perfectly right
> with your arguments. But long term some parts of the code definitely
> have to be cleaned up or everybody will be lost. 

Well, yes and no. Yes, you are right, and it is often  pretty  simple
for  isolated  code.  Cleaning up one ethernet driver or the code for
one specific RTC will not cause many problems. But  don't  touch  the
init  sequence  rashly,  or bigger sub-systems like I2C or PCI. There
are LOTS of things to consider.

> For the moment I don't really care about the huge rest of the code; the
> things I'm working on are currently mostly PXA related and I consider
> the PXA port still being code under construction.

Indeed. Just go on there.

> Perhaps some kind of a release plan would be helpful for the project,
> now that the code seems to work for several people. One could make
> checklists for a release, something like 
> 
> 	board 	compiles	tested	maintainer	tested-by ... 
> 	foo	x		x	Fridolin Tux	Erich Tux
> 	...

Fine. We can save the  "compiles"  column  because  usually  I  don't
accept any changes that don't compile.

But then - look at the MAINTAINERS file for the long list of orphaned
boards. What do we do with those?

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
A father doesn't destroy his children.
	-- Lt. Carolyn Palamas, "Who Mourns for Adonais?",
	   stardate 3468.1.