|
|
Blitz Devel : |
From: Oliver Schoenborn (oliver.schoenborn_at_[hidden])
Date: 2002-10-09 12:59:12
> Theodore Papadopoulo wrote:
> > More generally, what are the rules for comitting.
> > Should we send the patch first on the mailing list
> > to get comments and or approval... In essence, how
> > do we synchronize ??
>
> Let's see, I'm not sure what the process for committing updates should
> be either. How about if you mail your patch to blitz-dev and say "I am
> going to commit this tomorrow unless someone objects."
That sounds good. However, I would say that if a patch involves modifying
several files, a tag should be created so that the patch can be undone once
more extensive testing is done.
> I'd suggest we do this with any patch where we're not confident of the
> technical issues, or if there is a possibility the patch will be
> controversial. Straightforward patches I think can just be committed
> without debate
Keeping in mind that confidence does not eliminate bugs :)
> Also, does anyone know if there is a way to get blitz-dev and
> blitz-bugs emails fed directly into the sourceforge tracking
> system?
I don't know of a way to do that, given that bug submissions must be done via
the web page form. I.e. it doesn't seem like you can use your emailer and send
to e.g. projectname-bugs_at_[hidden], which would allow you to do what you
want. However, the opposite can be done, ie showing sourceforge information
(bugs, news, patches, releases etc) on the home page.
Oliver
_______________________________________________
Blitz-dev mailing list
Blitz-dev_at_[hidden]
http://www.oonumerics.org/mailman/listinfo.cgi/blitz-dev