I also think that the next release should be from what is now the branch, which means that it should be merged. But the problem I see is that it will be used for the nightly builds from that point on. So I thin k we first have to make a final solution/decision how we want to handle the transition from old style file URL fields to the new files.
On 28 Nov 2007, at 12:17 AM, Adam R. Maxwell wrote: > This is mainly a question for Christiaan, I guess, but what do you > all think about merging the fileview branch back to the trunk? > Should we do another release first, or just go for it? I don't > recall any critical fixes since the last release. > > My problem is that I keep going back-and-forth in actual usage; > today I made a bunch of file content searching changes on the > branch that probably should have been on the trunk...just because I > was using the branch at the time. Opinions? There was zero > feedback on the build that I posted, either because no one tried it > or everyone hated it. > > -- > adam > > ---------------------------------------------------------------------- > --- > SF.Net email is sponsored by: The Future of Linux Business White Paper > from Novell. From the desktop to the data center, Linux is going > mainstream. Let it simplify your IT future. > http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 > _______________________________________________ > Bibdesk-develop mailing list > Bibdesk-develop@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bibdesk-develop ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Bibdesk-develop mailing list Bibdesk-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bibdesk-develop
