Rick Hillegas wrote: > >> >> Looks like we agree this issue could be solved when the real need >> arises... I noticed Rick included this issue as one of the reasons >> for codefreeze delay. Rick, do you think this issue is more serious? >> > My issue is that, as of mid-March, metadata changes have been blocked > pending resolution of two issues: > > 1) Agreement on our upgrade policy vis-a-vis metadata. > 2) Fixing the upgrade tests. > Now I understand your concern... As far as I know, upgrade tests now pass with 10.2 trunk, though need some manual testing steps. Looks like we are making progress on upgrade policy for metadata. Someone suggested a Wiki to capture knowledge so far. That is a great idea. With the original freeze date for 10.2 being changed, it is my personal feeling that this "blockage" of metadata work should be lifted. In my opinion, the blockage to solve pending issues made sense when we were real close to the proposed 10.2 timeframe. Not anymore. Also proposing patches and solutions would make us understand issues so we could evolve the proposal.
Any one have objections to continuing metadata work now? I agree with you the blockage is bad... Satheesh > We are now almost three weeks into this blockage. A lot of useful work > is backed up behind these issues. Every week of delay pushes back the > code freeze. > > Regards, > -Rick > > >
