Let's deprecate functions now in field.info.inc. We can remove them after July 1. Obvious ones are field_info_field_by_ids(), field_info_field_by_id ...
Question is if we can move even more functions or not.
See also discussion in IRC
<swentel> xjm: we're in the process in killing much procedural functions in Field API. There's one file in field.module (field.info.inc) which still contains a lot of procedural functions which we could move to the FieldInfo class. Thing is, can we mark them deprecated now and still remove them after july 1st ?
<swentel> yched: ^ looping in
<xjm> swentel: IF the new API is already in place
<xjm> swentel: it is even conceivable we could add methods that wrap the procedural functions, then flip it after code freeze, so long as the param/return/etc. are the same
<swentel> xjm: it is, afaics, they just all become static methods on a class which is also available in the container. I can double check to make sure of course.
<andypost> they should all not sure static
<swentel> well, maybe not all, a couple :)
<xjm> swentel: as effulgentsia put it, we can deprecate anything that we're in the process of converting if the public API is the same, but what we can't do is say "deprecated in favor of a new API that doesn't exist yet; it will be nicer, trust us!"
<andypost> swentel, suppose we should just move code before 1jul and mark deprecated
<swentel> xjm: oh no, they are already really dumb wrappers right now. It's really just a matter of moving.
<swentel> xjm: I'll recheck again with yched to see what we'll do in the end. Can I paste your answers in the issue ?
<xjm> andypost, swentel: think of it as: the API afterf July 1 needs to maintain BC with the API as of July 1, minus anything marked deprecated. And sure.
<yched> yeah, I think they are pretty much all wrappers around either FieldInfo or plugin managers
<xjm> swentel, yched: Ideally your @deprecateds will be accompanied by @see to the new methods
<yched> swentel: there is field_info_collate_types() which is still about "old style / non plugin" field types, but that's being taken care of
<yched> swentel: and, well, it's also about "old style / non plugin" storage backends :-/
<yched> Ideally your @deprecateds will be taken behind the barn and shot in the head. With humanity.