On Thu, Oct 05, 2006 at 05:41:06AM -0700, Jerry Hedden wrote: > Jerry D. Hedden proposed: > > I'm considering a one line addition to the threads module > > to > overload the string value of a thread to return its > > ID: > > '""' => sub \&tid > > Nicholas Clark remarked: > > I do not wish the *default* behaviour of any part of a > > maintenance release to be incompatible (with the exception > > of bug fixes). > > Jonathan Stowe remarked: > > I guess that most people wouldn't object to the change > > going into blead and essentially the CPAN version can do > > what it wants within reason, but the requirement to not > > change the default behaviours of stuff in maint is always > > going to hold you back > > I think I get it now. The issue isn't about adding the > feature. It just that when added, it shouldn't get > propagated into maint. That should be easy. I'll make a > patch for blead, and the maint pumpking can opt not to use > it. Correct? >
I'm would say "not exactly". The change must be made in such a way that maintanence releases would not pick up the changes in the CPAN release of the module as well. The module versions should be identical whether we are talking about 5.6.X, 5.8.X, or 5.10.X. Except for bug fixes, funcionality should not change during the lifetime of a release, and potentially even longer. For example, based on statements from several other dual-lived modules, these authors are regularly testing their modules with Perls going as far back as Perl 5.003. threads, of course, hasn't been around that long, but it should be tested and maintained in a way that it will not break code going back to its original introduction to the core. Steve Peters [EMAIL PROTECTED]
