This group is locked. No changes can be made to the group while it is locked.
- [opendaylight-dev] [OpenDaylight Discuss] TWS on reorganizing the OpenFlow projects
Re: [opendaylight-dev] [OpenDaylight Discuss] TWS on reorganizing the OpenFlow projects
toggle quoted messageShow quoted text
The last question is basically, should we merge openflowjava and openflowplugin into one project? leave them apart? or pick a different splitting point?
That was basically the focus of the 3-5 mails before mine above.
On Thu, May 12, 2016 at 9:53 AM, Alexis de Talhouët <adetalhouet@...>
On May 12, 2016, at 9:43 AM, Colin Dixon <colin@...
So, did the TWS on this topic actually happen? I think it didn’t
Correct it didn’t, last TWS focused on phased release and semantic versioning.
, but it probably should in the near future. It sounds like there's two (or maybe three) orthogonal questions here:
1.) Should the tightly entwined OpenFlow projects be collocated under a single openflow project like we did with integration and releng? I'd say that's pretty clearly a yes, but we need to decide when and what impact it will have.
Thanh and Andy, do you have any comments there? Also, I don't remember if we got to keep group-level isolation of artifact names after we do that, which would be important to understand.
2.) Do we want to move related, but not-so-entwined projects into that too? These would be OF config and TTP for now. I'd argue yes, but I'm not going to fight a war for it.
+1, those are openflow-related projects, and are tied to openflow. I believe it makes sense having them under the same umbrella.
3.) Do we want to keep the separation between the OpenDaylight forwarding model and OpenFlow plugin? This is more involved and I think could be punted forward, but my general take is that the division we actually wound up with was different than that and maybe less useful.
I’m not sure to get the question here so I will at careful at further discussion.
Join email@example.com to automatically receive all group messages.