FYI,

Orange is asking TSC for a Magnesium code-freeze extension. Olivier, would Monday Feb 17th (one week after last proposed day) be enough?

BR/Luis

Begin forwarded message:

From: <olivier.dugeon@...>

Subject: Path Computation Algorithms for Magnesium release?

Date: February 7, 2020 at 2:09:05 AM PST

To: Luis Gomez <ecelgp@...>, Robert Varga <nite@...>, Ajay Lele <alele@...>

Cc: LAMBERT Guillaume IMT/OLN <guillaume.lambert@...>

Dear all,

I propose to publish the rest of my work on Path Computation, so you can have the opportunity to decide or not to include it in the release as we discussed during the last DDF. Note that my first change to implement path computation (see https://jira.opendaylight.org/browse/BGPCEP-858) is ready to be merged.

This week, the change https://git.opendaylight.org/gerrit/c/bgpcep/+/87048 proposed by Robert has been merged. However, this mass change implies at least a  change in the revision date of the API. This was not taken into account, certainly due to lack of time.

During the code review, Robert approved Guillaume's suggestion to change this revision dates and Guillaume proposed the change https://git.opendaylight.org/gerrit/c/bgpcep/+/87454. But, if you look at this change, a large amount of files (778 to be exact) has been modified, what complicates a "manual" analysis. The good news is that jenkins succeeds. That's potentially enough for a simple revision update. But in case of ....  clearly the situation is prone to give us an extra delay after the code freeze.

Everyone is doing their best and is very busy, especially Robert, so I am wondering if it is possible to extend delay before the code freeze for the BGPCEP project in order to have time to finalize the revision of the changes proposed by Orange and the possibility to merge them for the next Magnesium release.

Best Regards,

Olivier

--

 

Olivier Dugeon
Orange Expert, Future Networks
Open Source Referent
Orange/IMT/OLN/WTC/IEE/iTeQ

 

fixe : +33 2 96 07 28 80
mobile : +33 6 82 90 37 85
olivier.dugeon@...

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.