I try to add @Deprecated Annotation to the ODFDOM Doc Layer classes. The question is that we will just re-release ODFDOM 0.8.7. If I add the annotation based on the newest trunk that means we will release a new version different from ODFDOM 0.8.7 and the adoption work must do for Simple API caused by this issue: https://issues.apache.org/jira/browse/ODFTOOLKIT-49 (ODFDOM has moved the style access methods from the package layer OdfFileDom to OdfStylesDom and automatic style access to OdfStylesDom & OdfContentDom after ODFDOM 0.8.7) which I have mentioned in other thread.
What should we do? 2011/9/29 Devin Han <[email protected]> > +1 > OK, I agree for a snapshot release with no functional code change. > > 2011/9/29 Dennis E. Hamilton <[email protected]> > > +1 (non-binding [;<). >> >> -----Original Message----- >> From: Svante Schubert [mailto:[email protected]] >> Sent: Wednesday, September 28, 2011 15:22 >> To: [email protected] >> Subject: Re: Merge of ODFDOM DOC package and Simple API >> >> Am 28.09.2011 17:55, schrieb Rob Weir: >> [ ... ] >> > Could we mark the DOC API's as "deprecated" in our initial release, >> > and point to the replacements in the Simple API? We could do that in >> > the JavaDoc. That will give users the opportunity to migrate, but we >> > don't break their code immediately. Then we can remove the DOC API in >> > a future release. >> > >> > Would that work? >> > >> +1 >> >> We might make the initial release a no functional code change snapshot >> release. >> For us to proof we are able to deliver and sign the users we have >> continued here at Apache. >> >> > > > -- > -Devin > -- -Devin
