Am Freitag, 30. Juni 2006 00:43 schrieb Vlad Seryakov: > I am not going to argue, it is just old ns_cache used to have all > functionality and was very popular and useful. Now we have more limited > ns_cache_XXX family and standalone ns_cache does not work anymore. > I do not see who benefits from all this.
This is something that should not happen. It might have happend because a) there is a desire to straighten and improve code and logic of the "legacy" where appropriate (good!) b) there is a desire to include new functionality (good!) c) there is the need to use existing applications with naviserver "as is" and incompatibilities are to avoid. This is also a signal to new naviserver users (good!) and while a,b,c are desirable for themselves it's not always easy or possible to achieve everything at once. We should solve the reliance on a working HEAD so nobody is forced to code in god mode. Tagging could be used more often. So it is possible for everyone of us to tell others things like "I use naviserver-pre-5.0-1 (...) for 3 weeks now in production and everything works" - and of course rollback if there is need. There could at a minimum be one branch that allows everyone to implement and try new functionality that may even break usage for n days. Of course everyone can develop locally but than this effort is invisible and/or it just leads to monster commits. There would be no need to discuss everything everytime as the main branch is not affected; a merge can then be discussed without haste: "I refactored the whole xyz part - give it a try". So the ball keeps rolling at full speed. Bernd.
