Releasing Bugzilla to CPAN

Max Kanat-Alexander mkanat at
Fri Apr 2 04:25:06 UTC 2010

On 03/31/2010 09:51 PM, Gabor Szabo wrote:
> Let's look at Catalyst, while it is a framework and not an application.
> IT installs to the system and then you run a separate script that will copy
> (and generate) the necessary file in your application directory.

	Yeah, but Catalyst, being a framework, is essentially a library, and
something that developers use, not that end users use.

>>        No, actually, we recommend that even normal users upgrade using CVS,
>> currently, which will be bzr for 3.7 and above. All the tarballs we send
>> out retain the "CVS" directories currently, and will likely retain the
>> ".bzr" directory (probably as a lightweight checkout) too.
> ... that sounds crazy.

	Well, I understand how you feel about that, but sometimes when you're
new on a project, the way that the project operates might seem strange,
since you are unfamiliar with it or its userbase. The thing to do isn't
to insult the methodology of the system out of hand, but to instead
spend some time getting familiar with the system and its existing
userbase before you make decisions about what should and shouldn't be done.

> I don't understand why do you recommend upgrade via CVS and why do you
> distribute the files that belong to the version control system.

	Because many, many people customize Bugzilla, and thus the simplest
series of step-by-step instructions that are most likely to allow for
smooth point-release upgrades for everyone, regardless of their
situation, involve upgrading via CVS. CVS (and bzr) have much better
merge behavior than just "patch", and we don't even provide patches for
upgrades between major releases.

Competent, Friendly Bugzilla and Perl Services. Everything Else, too.

More information about the developers mailing list