On 2/15/07, <b class="gmail_sendername">Boris Mann</b> <<a href="mailto:boris@bryght.com">boris@bryght.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 2/15/07, Khalid Baheyeldin <<a href="mailto:kb@2bits.com">kb@2bits.com</a>> wrote:<br>> I really do not like the idea of different and conflicting versions of the<br>> same<br>> project being maintained in different releases by different teams.
<br><br>You mean kind of like Drupal core is today?</blockquote><div><br>Not quite a correct analogy. The Drupal core team does not "fork" Drupal<br>in different directions, and the version numbers indicate features + API
<br>compatibility.<br><br>Someone who was using tinymce 4.7 and happens to upgrade to tinymce<br>5.x-1.x will get a big surprise over 5.x-1.1 for example. The migration path<br>may be totally broken.<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Either moxie becomes what tinymce was, and let <a href="http://drupal-id.com">drupal-id.com</a> do his his<br>> thing with what is now tinymce and tinymce plus, or we talk him into<br>> focusing<br>> on one or the other of those latter two.
<br><br>Did I mention Drupal-ID is out of the equation? In the end, there can<br>be only one (/cue Highlander theme music).</blockquote><div><br>Can't remember the music on that one, but Sir Sean was awesome.<br></div>
<br>But, if <a href="http://drupal-id.com">drupal-id.com</a> is out (I assume "out" means you guys leave him a sandbox<br>on 5.x-1.x, and go with 5.x-2.x), then what is the fuss about? He can still commit<br>to your branch if he wants to, unless he is banned, and I don't think we want to
<br>that (at least not now).<br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> This forking of the same project by release will only confuse users and will
<br>> be a support nightmare.<br><br>But that's our problem as maintainers, not yours. Forking by project<br>is probably worse.</blockquote><div><br>What about the users who will download tinymce. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Note to other potential commenters: unless you are signing up to help<br>maintain TinyMCE, it's Allie, myself, Steve, and Kevin hashing this<br>out (publicly, no less :P).</blockquote><div><br>Sorry for interfering, but I am concerned about features and upgrade path
<br>from older tinymce versions, and about user confusion.<br><br>Should I hold off commenting until the team has a plan?<br><br>Feel free to correct the misconceptions I (or others) have.<br></div></div>-- <br><a href="http://2bits.com">
2bits.com</a><br><a href="http://2bits.com">http://2bits.com</a><br>Drupal development, customization and consulting.