On 7/4/07, Briggs <[EMAIL PROTECTED]> wrote: > Well, I do not believe that nutch should not hit a 1.0 until it is > truly stable. Using a version number as a selling point is what > makes people use to using beta branded software (google, ms, my > company, and everyone else are all guilty) as production software with > even worse EULAs.
IMHO 1.0 is the right way to go. Andrzej has summerized the reasons very well. I just like to add one more thing when I meet real world customers they often ask "is the product 1.0 ?" i.e. will there be Major API changes? I believe 1.0 will make more "wider usage" of Nutch in corporate segments i.e. large doc set, different types etc. > I would have like to have seen a plan, or feature list that shows what > nutch 1.0 is suppose to satisfy. I would also love to become part of > the nutch dev team. I have torn many pieces of it apart already and > have a pretty darn good idea of how it works. > Start submitting great patches and you will soon be a part of the team :-) > One thing I would love to do in the future of nutch is to get rid of > all the custom '*-config.xml" files and replace it with a more > standard (well, more accepted) DI container (such as spring or > hivemind [probably hivemind]). It would be nice to be able to > configure each component within nutch in this way. I think it would > really help in "componentizing" the apis (fetcher, indexer, generator > etc) so that they can have more implemenations and making plugins more > manageable. > I kind of like the way config works actually. Its not a hassle at all. Yes when you are doing testing etc you would like to change things in a easy way. But in production you don't change these values. Again you might have a great idea so submit a patch please. Regards Rajesh > > > > > > On 7/4/07, Andrzej Bialecki <[EMAIL PROTECTED]> wrote: > > Nuther wrote: > > > Hi, Andrzej. > > > > > > You wrote 4 июля 2007 г., 11:56:25: > > > > > >> Doug Cutting wrote: > > >>> Will the next release really be 1.0 or will it be 0.10? > > > > > >> Really 1.0. > > > > To elaborate a bit - IMHO we shouldn't stay at 0.x releases any longer, > > because it gives a false impression that Nutch is far from being usable. > > > > I know there is a fashion in OSS community to keep release numbers below > > 1.0, perhaps because commercial software usually inflates version > > numbers without any solid reasons. However, we shouldn't over-compensate > > for this by staying below 1.0 forever. Also, 0.x numbers hamper IMHO the > > use of relatively mature OSS software in commercial projects - it's more > > difficult to convince managers that software of 0.x vintage is any good > > at all. > > > > So, the reason I pushed for the change in numbering was that as it is > > now, Nutch is relatively stable and suitable for serious use. It might > > not be as full of features as one might wished, but that's what the 1.0 > > release implies - it's usable, with some limitations. > > > > > > > > > > > Will it be soon? :) > > > > I'm pretty sure it will be some time after the vacation period is over, > > not earlier ;) > > > > > > -- > > Best regards, > > Andrzej Bialecki <>< > > ___. ___ ___ ___ _ _ __________________________________ > > [__ || __|__/|__||\/| Information Retrieval, Semantic Web > > ___|||__|| \| || | Embedded Unix, System Integration > > http://www.sigram.com Contact: info at sigram dot com > > > > > > > -- > "Conscious decisions by conscious minds are what make reality real" > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Nutch-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nutch-developers
