On Sat, 28 Aug 2010 17:49:55 -0500 "Edward K. Ream" <[email protected]> wrote:
> On Sat, Aug 28, 2010 at 2:42 PM, zpcspm <[email protected]> wrote: > > I would suggest to use the term "deprecate" instead of "retire" or > > "remove". > > > > This is how I see it. If the next stable version will be the last one > > supporting tk - release it, then create a branch right after the > > official release and leave it unchanged. > > A branch will not be needed. Indeed, the code could stay the same, > except for two or three places. Rather, it is the docs that would > change: newbies would think that only Qt exists. Existing users would > be free to use Tk and Tk plugins. I'm not sure if zpcspm meant a branch or a tag, or perhaps they're the same thing in bzr..., no, they're not, so perhaps a tag make as much sense as a branch. But I think zpcspm's point was that you can then point people who must use Tk to the branch/tag/revision at which Tk support was best, because it's only going to go down hill from here. So people using that revision would miss out on everything that happens after it, but it's better than nothing for people who must use Tk. And my baseless assumption is that there are people for whom only Tk and not Qt are available, probably running non-linux unixes on non-PC hardware. So, perhaps a tag rather than a branch, but it sounds like a good idea to me. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
