NDT-DEV email list created

["Jeff W. Boote" <>]

This strategy is somewhat messy because I don't believe the version of the 
protocol is differentiated very well from the version of the software. We 
just completed a protocol document and I would assume that you would want to 
tie this new version of the software to the same version of the protocol.

If we come up with a reasonable way to address that issue (I don't know, 
perhaps hyphenate the version so the protocol version is first and then there 
is a software version appended) then this works for releasing.

This does not address the eventual merging of this functionality back into 
the trunk and future releases. For that, I believe we discussed waiting until 
the current code restructuring was complete. (Nov 1 is current scheduled 
timeframe.) Thomas, didn't you say you could merge these changes in at that 
point?

thanks,
jeff

On Aug 22, 2011, at 6:10 AM, Jason Zurawski wrote:

> All;
> 
> On 8/19/11 4:47 PM, thus spake Thomas Gideon:
>> On 08/19/2011 04:39 PM, Tiziana Refice wrote:
>>> 
>>>> To deploy the new client, do we need to contact all the partners
>>>> that are currently embedding the NDT client in their own tools
>>>> (BitTorrent, EETT, FCC, possible others)?
>> 
>> To deploy a new client, we need to coordinate with I2 first to make sure
>> we don't step on any toes in their release process and so my changes get
>> incorporated into subsequent releases. Once we do, we can roll out to
>> our servers which will update the web client on the M-Lab site, too.
> 
> CCing NDT-dev so they are aware.  I believe as long as you choose a version 
> number that reflects this is not the mainline (e.g. something that notes 
> its from an mlab specific branch) you can release the server/applet on your 
> own time.  Jeff can comment if he would prefer to see this done in another 
> way.
> 
> Thanks;
> 
> -jason
> 
>> Deploying on our systems first should not cause any breakages with other
>> existing clients but, yes, we should advise others to make the client
>> changes as soon as possible. The change is pretty trivial, just one
>> extra message during the meta portion of the test.
>> 
>> - --
>> Thomas Gideon
>> Sr. Staff Technologist, Open Technology Initiative
>> New American Foundation