Hi Jeremy, I think we have already agreed in the weekly chat on this. Perhaps the meeting minutes are not explaining it enough. We agreed to deprecate a methods and vars, and at least keep them for one more Woden release. In this way, our smart IDEs will complain about the deprecations and we, in Axis2 team, will be able to correct them. It is far more better than just getting a compilation error.
And when you deprecate methods or variables, please put some additional info, inside @deprecated to, to direct user to use the new methods or attributes and their locations. Anyway, do not please try to penalize us for depending on a milestone release. We definitely want to use the component and you also might like that to be used. If sudden things like, just removing methods happens then we in Axis2 are in trouble which is not good for both of the communities. Thanks, Chinthaka Jeremy Hughes wrote: > On 11/7/06, Lawrence Mandel <[EMAIL PROTECTED]> wrote: > [snip] >> 3.Development Discussion - All >> >> Chinthaka: I had a problem when I moved up from M6 to a snapshot. A >> method >> has been removed. > > Surely that is the nature of using snapshots. When you want stability > you use the milestone release itself and you do that consciously - ie > when you move from M5 to M6 you build and test in a sandbox and > resolve any issues - you don't rely on the automated build machine to > get it right. > >> John: Would it be OK if we keep the method for one milestone of Woden? >> Chinthaka: That would be better. At least we'd get a deprecation notice. > > How will we know we can remove the deprecated methods. Axis2 could > still be relying on the deprecated methods when we remove them. > > In some cases we might have to remove methods where the design changes > sufficiently that means we can't keep the method in situ. While this > would be unacceptable for a v1.0->v1.1 delivery I think it's fine > while we are in the middle of developing v1.0. > > Howabout a hybrid approach. Include a date in the filename of the > SNAPSHOT file so that you (Axis2 community) can choose when to move up > to a new SNAPSHOT level - doing all the changes and testing in a > sandbox you need. You get the control and the frequent updates (more > frequent than milestone builds :-) > >> Lawrence: I don't want this to slow down Woden development. We haven't >> even >> had a release yet. >> Arthur: How about if we build Axis2 and fix anything we break? >> Chinthaka: That will likely lead to problems. I'll see what we can do >> on the >> Axis2 side to reduce the problems for these changes but I think keeping >> deprecated methods for one Woden milestone will work. >> Lawrence: We should announce all major changes on the woden-dev list. > > Cheers, > Jeremy > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
signature.asc
Description: OpenPGP digital signature
