I'd say a branch, yeah, that would be a good idea.. I wonder what Tom thinks.. we don't want to create another branch like 0.96 and 0.97 where we had to backport everything, but only have a single branch for the tkhtml version, and every once in a while (once a week or month) do a merge from the trunk to that branch so that branch gets all the changes, but the tkhtml change stays in that branch.. then once it's done, we can merge that branch to the trunk, and since we did incremental merges, the differences will be small and we'll only get the tkhtml changes (otherwise we might get a lot of conflicts)..
KKRT On Fri, Dec 01, 2006 at 01:44:40PM +1300, majinsoftware wrote: > maby start another version of amsn with tkhtml like 0.98 that can slowly be > modified as the new feature come out in tkhtml and keep the 0.97b developing > separately. then you will be able to download 0.98 and see what progress is > being made as well as keeping 0.97b if you want latest functional client. > ------------------------------------------------------------------------- > 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 > _______________________________________________ > Amsn-devel mailing list > Amsn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amsn-devel ------------------------------------------------------------------------- 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 _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
