Restart the release cycle then and delay the release. Don't break the rules. If the rules are wrong then change them instead of breaking them. There will always be features that would "be nice" to have in a release.
Casper
-----Original Message----- From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Ged Murphy Sent: 14. december 2005 11:55 To: ReactOS Development List Subject: Re: [ros-dev] getfirefox
Ge van Geldorp wrote:
From: Ged Murphy
Although we're in feature freeze, do you think it's worth including the getfirefox utility to the 0.2.9 branch?
I agree that getfirefox is totally awesome :D but I might not be completely objective on it. I always copy fixes I made to trunk to the branch, but as you noticed, we're in feature freeze and getfirefox is not a fix, it's a new feature, hence I didn't copy it. Then again, the risk to stability in the branch is minimal. I think WaxDragon should decide on this, I can live with it either way.
My main reason for wanting to break the rules just his once, is that I think we would gain a lot of feedback from users having firefox within their grasp. With us working towards the 0.3.0 release, I think it would be a good thing to get lots of feedback as it needs to be stable by that time, being one of the major show stoppers.
However, I too can live with either decision :)
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev