Good point. I think deprecating them and using a attribute on the package export to indicate that it is likely to change would be a good idea.
Alasdair 2010/1/26 David Jencks <[email protected]>: > I'd love to see a release of aries-blueprint in particular. I wonder if it > would be a good idea to mark "deprecated" some of the interfaces such as > NamespaceHandler that aren't yet in a spec and might change but will be used > by lots of people? On the other hand geronimo-blueprint got released > without such markings. > > thanks > david jencks > > On Jan 26, 2010, at 9:34 AM, Jeremy Hughes wrote: > >> There's been a lot of activity lately so I'd like to propose we do a >> release so we can get some wider user feedback. I think we should give >> it a version of 0.1 and stick to versions <1 while we're in the >> Incubator. >> >> Then there is the question of whether to independently version the >> high level modules or keep them lock-step. For now I think we should >> keep them lock-step until we feel a need to change that. >> >> What does everyone think? >> >> Thanks, >> Jeremy > > -- Alasdair Nottingham [email protected]
