Unfortunately, for whatever different reasons, we're having a lot of trouble pulling things together. Regardless of what the reasons are, we can't let this continue to kill the development momentum that geeqie's been building over the past many months. Consider that in June of 2009, there were 68 commits made to the geeqie repository. This has dropped to just 6 in November and 7 in December. Basically, we're dead in the water.
That said, we need to get 1.0 out the door. Despite having a lot of incomplete translations and documentation, we've still done a ton of work that other folks should have access to. There's more work to be done, undoubtedly, but what's there now is still pretty good and very usable. Maybe 1.0 won't be quite as awesome as we'd hope, but there is life after 1.0 — right now, we need the opportunity to keep developing and keep improving things, rather than sitting in a never-ending release freeze. We need to be able to accept contributions of code before the contributors get frustrated and move on to other things. In short, I would strongly suggest that we set a 1.0 release date sometime in January, preferably early rather than late January, and stick to it. It might not be the quality of release we were hoping for, but at this point, it's more important to be able to continue moving forward than to try to make this release perfect, which will never happen. --xsdg ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Geeqie-devel mailing list Geeqie-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geeqie-devel
