From mboxrd@z Thu Jan 1 00:00:00 1970 From: Don Slutz Subject: Re: [PATCH for-4.5 v7 0/7] Xen VMware tools support Date: Thu, 16 Oct 2014 08:58:50 -0400 Message-ID: <543FC10A.9070103@terremark.com> References: <1412285417-19180-1-git-send-email-dslutz@verizon.com> <543F9A04020000780003F0EA@mail.emea.novell.com> <543FB59E.8050402@terremark.com> <543FD4A1020000780003F378@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <543FD4A1020000780003F378@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , Don Slutz Cc: Jun Nakajima , Tim Deegan , Kevin Tian , Keir Fraser , Ian Campbell , Stefano Stabellini , George Dunlap , Andrew Cooper , Ian Jackson , xen-devel@lists.xen.org, Eddie Dong , Aravind Gopalakrishnan , Suravee Suthikulpanit , Boris Ostrovsky List-Id: xen-devel@lists.xenproject.org On 10/16/14 08:22, Jan Beulich wrote: >>>> On 16.10.14 at 14:10, wrote: >> On 10/16/14 04:12, Jan Beulich wrote: >>>>>> On 02.10.14 at 23:30, wrote: >>> Just for the record - I do not see this as warranting a release exception. >>> The effort to get this in place was started way too late, and shouldn't >>> be rushed close to or already beyond the feature freeze point. >> Being first posted on Sept 1, 2014: >> >> From: Don Slutz >> To: >> Date: Mon, 1 Sep 2014 11:33:46 -0400 >> Message-ID: <1409585629-25840-1-git-send-email-dslutz@verizon.com> >> Subject: [Xen-devel] [PATCH v2 0/3] Xen VMware tools support >> >> and a feature freeze of 10th September 2014, I would not expect to >> need a release exception. > I hope you didn't mean this seriously: That might have been okay > for a feature that can be expected to not need a lot of discussion > and is relatively limited in the amount of code it touches. But > generally, and particularly for anything larger, please get used to > starting the work and discussion early, not near the end of a > development cycle. Clearly I did not understand this correctly. Sorry about that. I did attempt to start this discussion early (December 13, 2013), but failed (do to other things) to post the v2 until Sept 1, 2014. -Don Slutz > Jan >