I'm having second thoughts about the wisdom of merging VR and VR2 into VR3, 
for the following reasons:

1. The code bases are significantly different, despite similarities.

2. Most people will strongly prefer one or the other.

3. There is no great need for the merger.  In fact, it's possible to enable 
both at once, and nothing awful will happen.

4. Keeping the plugins separate will allow independent development.

Unless I hear convincing reasons to do otherwise, I am going to close #303 
and move the VR3 code to the attic.


You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to