Releasing 3.17
Andy Armstrong
andy at hexten.net
Tue May 5 11:18:29 GMT 2009
On 5 May 2009, at 12:14, Steve Purkis wrote:
> On 3 May 2009, at 23:07, Andy Armstrong wrote:
>
>> I'd like to release 3.17 but I think Steve's work on the sniffing a
>> suitable interpreter for test scripts is incomplete.
>>
>> Steve - would it be OK to move your stuff to a branch and take it out
>> of trunk until it's complete?
>
> Yes, I prolly should've done that in the first place :-/
>
> Alternatively, it is safe to release as-is - I didn't integrate the
> new classes in, so the current behaviour will be preserved. Looking
> at the last build, only the Pod test is failing with 7 naked subs
> which can all be marked 'TODO'.
I'd rather not make a release with unused code in there.
> Unfortunately the soonest I can get to it at this point is Thursday;
> I'm on hols atm & no dev box.
No problem - thanks for what you've done so far.
> I don't want to hold up a release, so if someone else wants to pick
> this up feel free. It's probably easier to fix the pod, but if you
> decide to branch stuff, it should be safe to prune these:
>
> trunk/lib/TAP/Parser/SourceDetector
> trunk/lib/TAP/Parser/SourceDetector.pm
> trunk/lib/TAP/Parser/SourceFactory.pm
> trunk/t/source_factory.t
> trunk/t/lib/MySourceDetector.pm
>
> Though you'll have to remove the use statements from TAP/Parser.pm ...
>
> +use TAP::Parser::SourceFactory ();
> +use TAP::Parser::SourceDetector::Perl ();
I'll copy trunk into a branch and then back out your commits from
trunk. I think that should do it.
--
Andy Armstrong, Hexten
More information about the tapx-dev
mailing list