On Wed, 2009-10-28 at 23:54 +0100, Øyvind Harboe wrote:
> > Is this for 0.3.0 or 0.4.0?  I have ~50 patches and at least one or two
> > will probably have minor conflicts with yours.  I also am looking at
> > doing a ton more cleanup like the stuff you have done, but I am waiting
> > until a) we ship 0.3.0 and b) I get my current series in the tree.
> > If I had continued, I'd probably have a stack of at least 200 by now, so
> > there is no question about the opportunities to do this kind of work.
> > The question is when we should merge them.

I misread David's post.  I didn't realize it has already been pushed.

I am becoming fairly discouraged by the ongoing high-pace use of the
central repository, seeing this type of commit pushed without sufficient
review period.  Are we trying for 0.3.0, or not?!?

> I would like to see:
> 
> - 0.3 out of the door. Shut down sf master for anything but
> bugfixes as of friday 30. to wed 4.? Cut release nov 5.?

At present, I do not see what the point is.  We might just as well cut
the current master.  I think the quality will hardly be unchanged, until
we implement better processes.

> - that we can agree that major features are developed in public
> branches on repo.or.cz and then applied to sf when they
> are as ready as they are going to be. Communication can be
> via the mailing list and explicit posts.

I think that I would rather see us dump SF.net as the primary repository,
switching to a site that does not _require_ central administration for 
clones of the repository.  I continue to be adamant that pushes to the
main tree should be done with machine-like rigor (i.e. scripts only).

> W.r.t. testing I believe that we have to push changes to sf master
> before they are tested beyond the few developers working on
> a particular feature branch.

That might be true, but the voice of those "few" developers deserve to
be heard before unleashing new patches on the public.

Cheers,

Zach
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to