Upcoming Releases Schedule...
minimarmot at gmail.com
Sat Sep 20 03:01:26 UTC 2008
On Fri, Sep 19, 2008 at 10:38 PM, Jo Rhett <jrhett at netconsonance.com> wrote:
> On Sep 19, 2008, at 7:07 PM, Aragon Gouveia wrote:
>>> To get a business to commit resources to a project there must be an
>>> actual goal.
>>  The FreeBSD project would have to commit resources too. Its community
> Of course. This is what the requirements analysis is ;-)
>> For (a), (b), and (z), this is where you come in. Define the goal. Make
>> plan to get there. Assess the effort involved. Convince your employer
>> (a), (b) and (z) is worth it to him/her and that the result of (z) will
>> convince the FreeBSD project to commit the resources needed to integrate
>> If they're happy, start working on (z) and bring it to the FreeBSD project
>> when you think it's ready.
> Of course. If this was something that could be done without working with
> the freebsd developers, do you think I would put up with this kind of abuse?
> I'd much rather have something I could just go and do ;-)
> The issue is that nobody is willing to answer the question: "what resources
> are too limited to provide longer support? How can we help?"
Jo, I think this is the clearest way you have stated your point yet, and
it is quite definitely the crux of the issue:
What resources does re@ not have, that releases are supported
for these short times? I have never run a release, so I can't be much
more specific that ``man-hours'' -- someone else should chime in
and say what those hours would be spent on, if they were there.
I think this is a great opportunity for the project, and a few pointers
for how one could maintain an independent support of older releases
would give the rest of us a great resource.
More information about the freebsd-stable