On Wed, Sep 3, 2008 at 7:11 AM, sda <[EMAIL PROTECTED]> wrote: > On 22:24 Tue 02 Sep , Wido wrote: >> yes, i agree with your idea and i see your point. In fact, i never >> said NOT to do what you said. BUT, it's not the same having a E17 0.10 >> for 3 month than having a new version every two days. That's why i >> said "feature freeze", so distros can have a fully functional and >> stable, for at least 4-6 months or so. For arch or gentoo that is >> trivial, but not for ubuntu or fedora it's not THAT trivial (in a full >> ofitial repo) >> > > can i ask you to copy my response when you make a reply? KainX rejects > all my messages to E-users and E-devel, that's why i'm almost not using > ML's as a source for communication. > > let me also clarify some aspects on distribution policy. the "freeze" > you're talking is a base rule for a release-cycle Linux distributions. > like FC, OpenSUSE and others. it's the package maintainer task (in > general) to "freeze" the snapshot (it could be a release, whatever) and > backport major fixes, security updates etc. to provide a stable working > package. in other words upgrade of versions are only possible for the > packages which not to trigger the rebuild of a whole distro (like 'gcc' > or 'glibc' for example). > > that's why we need not the info that 'svn revision 1234' builds fine, > but that 'svn revision 1234' builds fine and no critical bugs are found > within the "INFO how long this revision has been tested, PC configs, > version of a Linux distro which performed the test" period.
yes but, how can it be achieved when it relies on 7 "non-stable" (as i think they are now) libraries. > > and here's another case. the projects like Enlightenment or MPlayer (the > projects with a solid talented and experiences dev team) are best when > you're using svn/cvs/git/etc. and it's just the best option to provide > the 'current' packages for the major distros. sooner or later this will > be appreciated and recommended to use this 'current' packages (at least > they're should be stable and deliver zero inconvenience to the End > User). > > regards, > sda > > I insist, i'm not saying to stop coding new features, but to have a clear milestone for the core libraries and e so, as you say, package mantainer can put it on repos. And not just one or two, but a lot of then in diferent repos, diferen policys, diferent enviroments -- Wido ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
