Fast releases demand binary updates.. (Was: Release schedule for 2006)

Peter Jeremy PeterJeremy at
Fri Jan 6 11:44:45 PST 2006

On Fri, 2006-Jan-06 03:03:18 -0800, Jo Rhett wrote:
>> Bottom line:  Once code exists, then support can be talked about..
>This is bullhockey and you know it.  Once the project is done, we'll
>authorize a budget for it?  Once the season is over we'll know who should
>be on the starting team?

In general, volunteer projects have a surfeit of ideas and a shortage
of real implementations.  The Project is never going to agree to import
an idea without some substance.

>  Yeah, hindsight is sweet.  But this isn't a
>simple change.  It will require very close integration with the installation
>and kernel modules at least (and probably more).  So having some sort of
>consensus that (a) the project has interest and (b) what flavors would be
>acceptable to the existing groups - are both necessary for this project to
>even mumble it's first line of code.

In which case you need to move this thread to freebsd-arch where these
sort of issues are discussed.  You need to clearly define your goals
and suggest a design to meet them.  If your idea has merit, you'll be
able to convince at least one committer to work with you to implement
your design.

Peter Jeremy

More information about the freebsd-current mailing list