[petsc-dev] Pushing non-working code

[Sean Farley]

On Sat, Feb 2, 2013 at 5:17 PM, Hong Zhang <hzhang at mcs.anl.gov> wrote:
> I agree with Matt on this issue.
>
> 'petsc-dev' means 'dev', that a developer should be able to push on-going work
> after he/she does local tests and is willing to fix the warning/bug as soon as
> the problems appear. Personally, I am unable to write a bug/waring free code,
> not matter how much effort and time to put into it.

Hong, the solution is pretty simple: work in your own repository
(http://bitbucket.org/hzhangIIT/petsc-dev) and others (Jed, Karl, me,
etc.) will pull the changes from you once they have been smoothed out.

As a side note, 'dev' does not simply give you a pass to write broken
code as just a check point. You are basically shirking your own
repsonsibility and putting the burden on other developers.