Bundling more plugins into bzrtools

[Jeff Licquia]

Toshio Kuratomi wrote:
> We have a de facto standard in Fedora[1]_ of one tarball one package. 
> There are multiple reasons for this but the number one reason is 
> coordinating release schedules.  If you have twenty upstream projects 
> and one updates with a security fix, you have to respin your package. 

I'm confused.  If you have twenty upstream plugin authors working on a 
unified source base, and one of them has a security update, you still 
have to respin your package, right?

> Note that this differs from one upstream project with multiple parts in 
> that one upstream project on bzr's release schedule might release once 
> or twice a month because people agree to work towards a common release 
> date.  If you are spinning one package which is made up of ten upstreams 
> and just three of those do a single update in that same time frame you 
> are doing more work.

This is a little confusing, also.  I get that *you* have less work, but 
I don't see the savings in the total amount of work.  Someone has to 
herd those ten upstreams into one big thing; it's not going to happen by 
itself.