Personally, I'd be in favor of removing the old viewers from trunk immediately. It doesn't make sense to me to keep code in trunk that isn't going to be part of a future release. trunk is not meant to be a stable code base. It's meant to be a next-generation code base on which new releases will be based. If we don't intend to make the old viewer a part of a future release, then it needs to be removed from trunk. If people are still using the old viewer, then that's what the 1.1 branch is for.
On a side note, it also goes against every fiber of my being to ignore any bugs, and I sincerely hope we will not decide to ignore the bugs in the next release the way we have ignored them in the last release. It's hard for people to trust the stability of our next-generation code when the code that we're calling "stable" (1.1.0) has a bunch of bugs, by our own admission, and when we're deciding to abandon the stable branch. That isn't the way healthy open source projects behave. On 9/30/11 7:32 AM, Pierre Ossman wrote: > There's a bunch of bugs in the tracker for the old viewers. Should we > pay attention to those or should we start pointing people towards the > new viewer? If the latter, then I guess we should also consider > removing the old ones from trunk. ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
