[Reportbug-maint] merging common stuff in python-debianbts?
ben+debian at benfinney.id.au
Sun Jun 15 10:44:20 UTC 2008
Thanks for the feedback, Sandro.
Sandro Tosi writes:
> On Sun, Jun 15, 2008 at 06:36, Ben Finney wrote:
> > I'm most of the way along with a branch that has the following
> > purpose:
> > Move all non-program modules into a Python package directory,
> > 'reportbuglib/', and ensure all imports still work.
> > [...]
> > I expect to have this branch ready to merge into trunk fairly
> > soon. Does anyone have any objection to me doing so?
> My only concern is: do you really think that a package with 200+
> bugs opened need aestetical or architectural changes instead of
I think that one of the reasons the package has so many open bugs for
so long is because the code base needs fixes for numerous
architectural and coding-style problems.
They need to be addressed gradually, so as to minimise disruption and
keep everything working, but leaving them unaddressed makes the entire
code base difficult to maintain.
> Of course, you're the expert here, so I won't argue...
Hardly. What gives you the impression I'm an expert? I'm trying to
make the code easier to maintain for everyone, including myself.
> The only thing that worths be added, is having an arch doc, that
> explains the code structure, relationship and so, a sort of
> high-level overview of the code.
Good idea. I'll add this information to 'README.developers'.
\ “Isn't it enough to see that a garden is beautiful without |
`\ having to believe that there are fairies at the bottom of it |
_o__) too?” —Douglas Adams |
More information about the Reportbug-maint