common.xml: remove wip from AIS_VESSEL

[peterbarker]

This one has cooked long enough...

[hamishwillee]

Thanks @peterbarker

There are also a whole bunch of enums associated with this -e.g. AIS_FLAGS that have informal wip markup - you can see them in #1228
Can you also tidy those?

I'll make sure there are no objections in dev call tonight.

[hamishwillee]

From devcall - we're trying to stick with the governance model proposal of only "formally" including things in common.xml that are in one stack and with "firm intent" to get in another stack. We think this fits that model - just trying to confirm that this either is or will be supported by MAVSDK as well in the near future. @julianoes @bazfp - can you confirm?

[peterbarker]

From devcall - we're trying to stick with the governance model proposal of only "formally" including things in common.xml that are in one stack and with "firm intent" to get in another stack. We think this fits that model - just trying to confirm that this either

Fair enough. As an alternative we could move it into ardupilotmega.xml.

[hamishwillee]

@julianoes @bazfp - can you confirm #1817 (comment)

Thanks @peterbarker - I think would be good to get into common, we're just trying to 'do the right thing". Either way though, this can't be merged until the associated enums are also updated to remove the "Wip comments".

[bazfp]

From devcall - we're trying to stick with the governance model proposal of only "formally" including things in common.xml that are in one stack and with "firm intent" to get in another stack. We think this fits that model - just trying to confirm that this either is or will be supported by MAVSDK as well in the near future. @julianoes @bazfp - can you confirm?

I have firm intent to get USV features like AIS features into our autonomy + MAVSDK

[hamishwillee]

Thanks @bazfp - sounds great. FMI, any timeframe in mind?

@auturgy You OK to merge? This is good enough for me.

[bazfp]

Thanks @bazfp - sounds great. FMI, any timeframe in mind?

AIS is below some more crucial changes, but may jump up as we have discussed including this on a recent vehicle

[auturgy]

merge

Yup

[hamishwillee]

Agreed merge in devcall based on normal rule of "in one stack" and commitment to get in another.