<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Apr 23, 2014, at 6:23 PM, Alex Afanasyev <<a href="mailto:alexander.afanasyev@ucla.edu">alexander.afanasyev@ucla.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 18px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><br>On Apr 23, 2014, at 5:04 PM, Davide Pesavento <<a href="mailto:davidepesa@gmail.com">davidepesa@gmail.com</a>> wrote:<br><br><blockquote type="cite">On Thu, Apr 24, 2014 at 1:55 AM, Alex Afanasyev<br><<a href="mailto:alexander.afanasyev@ucla.edu">alexander.afanasyev@ucla.edu</a>> wrote:<br><blockquote type="cite"><br>On Apr 23, 2014, at 4:53 PM, Davide Pesavento <<a href="mailto:davidepesa@gmail.com">davidepesa@gmail.com</a>> wrote:<br><br><blockquote type="cite">On Thu, Apr 24, 2014 at 1:02 AM, Alex Afanasyev<br><<a href="mailto:alexander.afanasyev@ucla.edu">alexander.afanasyev@ucla.edu</a>> wrote:<br><blockquote type="cite">We will try to do the change with a transition period, when existing application will still be able to compile against ndn-cxx (there will be additional symlinks created for include, lib, and pkg-config files), but all known applications needs to be updated ASAP after the renaming is complete in the following way:<br><br></blockquote><br>Are you going to release the first version with the compatibility symlinks?<br></blockquote><br>Honestly, not sure about this and we shall make a decision. If we can quickly update all applications (NFD, repo, NLSR, ping, others?), then this will not go into the release. Personally, I prefer not to add symlinks in the initial release.<br><br></blockquote><br>Agreed, but it also depends on the available timeframe. Aren't we<br>already late with the first release?<br><br>Instead of adding symlinks, we could freeze the current ndn-cpp-dev<br>codebase and keep the github repo and docs so that people can still<br>fetch and build the old library. After a while the docs are removed<br>and the ndn-cpp-dev repo is changed to redirect to ndn-cxx. How does<br>that sound?<br></blockquote><br>This sounds good to me. I can also update README.md file for ndn-cpp-dev repo, stating that this library has been renamed and development continues under different name + add the link. After a month or so, we can remove it completely.<br></div></blockquote></div><div><br></div><div>The changes needed seem easy to make. Since all developers are on this list, why not set a deadline, say the end of this Friday, and every app has to finish the changes by then? </div><div><br></div><div>Beichuan</div></body></html>