This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: proposed deprecation policy/mechanism
Hi -
On Fri, Jun 25, 2010 at 08:24:28PM +0200, Mark Wielaard wrote:
> [...]
> Maybe we should also say something about how often we will create a
> major release. Once around every 3 months?
Yeah.
> > For example, if we're in development between versions
> > 1.2 and 1.3, wrap to-be-deprecated tapset functions in
> > %( systemtap_v <= "1.3" %? function foo() {} %)
> > so as to preserve the tapset function during the life of the 1.3 release.
>
> Would the same hold for probe aliases?
Yes.
> Does this mean that they are still supported when systemtap 1.4 is ran
> with stap --compatible=1.2? If so, then it would mean that we can never
> really remove some functionality.
Right, I guess we need some extra text to describe "really deprecated"
state that would enable us to drop the code after a while.
> > Script language changes that cause earlier valid scripts to become
> > invalid should be opt-in [...]
>
> Do we have any of such language changes at the moment?
No.
- FChE