| 1 |
On Wed, Feb 04, 2004 at 02:27:15PM +0100 or thereabouts, Matt Steven wrote: |
| 2 |
> If Gentoo is going in the direction of providing releases on schedule, |
| 3 |
> ensuring one release has certain versions of certain programs and isn't |
| 4 |
> interfered with by future releases, can it be done without cutting away the |
| 5 |
> flexibility? |
| 6 |
|
| 7 |
Yes, absolutely. Users can choose which method they want to use. |
| 8 |
|
| 9 |
> Are we going to have a gentoo-1.4-enterprise, gentoo-2.0-enterprise etc |
| 10 |
> portage tree, each release being maintained independent of the others? |
| 11 |
|
| 12 |
Not defined yet. |
| 13 |
|
| 14 |
> I think Gentoo does so well at staying up to date because the developers are |
| 15 |
> the users, they all want the latest XYZ so someone writes an ebuild and in a |
| 16 |
> flash there it is. Will there be the same level of volenteer motivation |
| 17 |
> toward maintaining the security patches on a two year old release? |
| 18 |
|
| 19 |
Probably not, but nobody is suggesting supporting one release for 2+ years. |
| 20 |
|
| 21 |
> Making an 'enterprise' Gentoo will require a solid plan of action that will |
| 22 |
> enable people to sell it to management, some sort of guarantee, and I look |
| 23 |
> forward to hearing how all that will work. |
| 24 |
|
| 25 |
See GLEP 19 for one suggestion: |
| 26 |
|
| 27 |
http://www.gentoo.org/proj/en/glep/glep-0019.html |
| 28 |
|
| 29 |
If other folks have different ideas about how to implement this, please |
| 30 |
feel free to share them as well. |
| 31 |
|
| 32 |
--kurt |
Archives