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.
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. 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. But, anyway... i was just curious about the patches. You know how it is when everyone at the office says "why doesn't it work".... and I reply "well, there is a bug, I can fix it", then they say "no, we don't want to fork the code", then they say "but, it doesn't work". so, I have to fix it under the covers, or apply patches, but keeping track is a complicated process once you have applied many patches and customized code. Anyway, have fun! Briggs (lovin' nutch every day) 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
