python-quantities-developers team mailing list archive

[Darren Dale <dsdale24@xxxxxxxxx>]

On Tue, Jul 21, 2009 at 10:54 PM, Tony S Yu<tonyyu@xxxxxxx> wrote:
> Hey Darren,
>
> I just submitted a bug report relating to wrong uncertainty values when
> dividing by an UncertainQuantity. I know a few projects prefer an email to
> go to list whenever a bug is posted; is this the case here?

I don't think it is necessary to report it in both places, the bug
report at launchpad should be fine. I think I might be able to set it
up so launchpad automatically informs the dev list when a bug is
reported.

> Also, I was wondering, do you prefer merge proposals for all patches, or is
> that only necessary for major changes.

I would prefer moving to merge proposals for everything, so we can
keep track of whats been merged and what hasn't. I think there is even
a trick to automatically link a branch to a bug report, using the
--fixes flag (see bzr help bugs). Lets register bugfix branches as
"bug-XXXXXX", and feature branches like "ufunc-array-prepare", and
drop "quantities" from the branch names.

> One last thing, I assume it's ok to delete the branch I made for the
> documentation bug I submitted, correct?

When a branch is merged into say the trunk, and the trunk is pushed to
launchpad, it will automatically change the status of the merged
branch from "active" to "merged", and will not be shown in the list of
active branches at launchpad. I think we should probably hold onto
merged branches for a little while. If a bug were reopened, for
example, that branch would be the natural place to continue working.

Darren