Deprecation checklist and cycle (Was: Removing SCons.Sig breaks bootstrap.py)

anatoly techtonik <[email protected]>
Newsgroups gmane.comp.programming.tools.scons.devel
Message-ID <CAPkN8x+5Tts4ETSMqJeb0HMh_yWEVzQ8hP6GsH-K3V-3C79dJA@mail.gmail.com>
Is there a document that lists deprecation cycle and checklist to
go while deprecating and removing features? SCons documentation
used to be perfectly maintained in the past and it would be nice to
see the process continued.

In particular, I would add a point to accompany commits that are
removing features to corresponding talks and information. Does that
sound good?

https://bitbucket.org/scons/scons/pull-requests/445/default/diff

On Sun, Apr 16, 2017 at 9:17 PM, Bill Deegan <bill-cJFiu+DHMVC5azolltMz9laTQe2KTcn/@public.gmane.org> wrote:
> k. that's easy to fix.
> Probably need to add a bootstrap.py step to one of the buildbot workers.
> -Bill
>
> On Sat, Apr 15, 2017 at 10:53 PM, Gaurav Juvekar <[email protected]>
> wrote:
>>
>> Hi,
>>
>> Rev 5b4cf5aec6d3 which removes SCons.Sig seems to break bootstrap.py with
>> error
>> could not find `src/engine/SCons/Sig.py' in search path:
>>
>> Rev f214c734fc32 works properly.
>>
>> --
>> Regards,
>> Gaurav Juvekar
>> _______________________________________________
>> Scons-dev mailing list
>> [email protected]
>> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>
>
>
> _______________________________________________
> Scons-dev mailing list
> [email protected]
> https://pairlist2.pair.net/mailman/listinfo/scons-dev
>



-- 
anatoly t.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.