Sami Siren wrote: > 2007/3/29, Andrzej Bialecki <[EMAIL PROTECTED]>: >> >> Sami Siren wrote: >> >> > IMO we should have had a 0.9-rc1 tag, apply patch to trunk, have >> > 0.9-rc2 tag and so on until we are satisfied. >> > >> > Then when we're actually satisfied create tag for 0.9 (copy from rc >> > that got promoted). >> > >> > What is the benefit of using a branch before a release? >> >> That you don't withhold other development while waiting for rc1, >> rc2, rcN, ... - other patches, including disruptive ones and those that >> introduce new features, can be applied in the meantime to trunk/ . > > > Nutch trunk has "kind of" being in a state where no modifications are > allowed fow quite a long time already before Chris started his work. If the > branch is done based on those argumnents it should have been done a > long time ago.
I'm not arguing about the past - the project had so few active people at that time that it didn't matter. However, now that the project became more active again, and there are people willing and able to work on new functionality, we shouldn't hinder their work. We are discussing what is the best course of the action for future releases, in order to avoid such long freeze periods on the trunk/ . -- Best regards, Andrzej Bialecki <>< ___. ___ ___ ___ _ _ __________________________________ [__ || __|__/|__||\/| Information Retrieval, Semantic Web ___|||__|| \| || | Embedded Unix, System Integration http://www.sigram.com Contact: info at sigram dot com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Nutch-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nutch-developers
