Thorsten Haude wrote:

Interesting, I would have said that as a rule, the code is supposed to
be single-branched (releases excepted), but now that I think about it
this might just be an impression formed in my first days when CVS was
more a source for anguish and possible embarrassment than a tool.

I think branching is branching, no matter what tool you use. I'm all for changing the policy if it means more development.

Note if we go down this path, it does mean that the non-Linux builds will likely wither and die due to lack of interest. Without somebody to make sure that snazzy feature X works on AIX, the AIX port will die.

I'm unsure what to think about this. Part of me thinks that NEdit sole reason for survivial is not that it's the best editor for Linux, but the best editor when you don't have Linux. Making it Linux-only might kill it: the Linux people won't use it because they want kate/gedit/emacs and then it will be broken for non-Linux.

But, maybe the way forward *is* fork it so that Linux can move forward, and the older versions can stay alive somehow in maintenance mode. It's far easier to do this if the code is colocated in one repository than if it really is forked.
--
NEdit Develop mailing list - [email protected]
http://www.nedit.org/mailman/listinfo/develop

Reply via email to