Date: Sat, 7 Jan 2006 06:44:36 +1100 From: Peter Jeremy <PeterJeremy@optushome.com.au> To: freebsd-stable@freebsd.org, current <current@freebsd.org> Subject: Re: Fast releases demand binary updates.. (Was: Release schedule for 2006) Message-ID: <20060106194436.GD51452@cirb503493.alcatel.com.au> In-Reply-To: <20060106110318.GF54324@svcolo.com> References: <43A266E5.3080103@samsco.org> <43AB1E65.2030501@mac.com> <20051222221202.GM39174@svcolo.com> <200512231136.12471.doconnor@gsoft.com.au> <20060105092448.GH1358@svcolo.com> <20060105184147.GD69162@funkthat.com> <20060106110318.GF54324@svcolo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060106194436.GD51452>