[Bioperl-l] releases {1.0.2, 1.1}

[Hilmar Lapp]

Apart from Exception.t I get two more failures:

EMBL_DB.t:

cb6: bioperl-live 15:40 15>perl t/EMBL_DB.t 
1..15
ok 1
ok 2
ok 3
ok 4
ok 5
not ok 6
# Test 6 got: 'embl:BUM' (t/EMBL_DB.t at line 67)
#   Expected: 'embl|J02231|BUM'
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14
ok 15

and BioGraphics.t:

cb6: bioperl-live 15:41 16>perl t/BioGraphics.t 
1..14
not ok 1
# Failed test 1 in t/BioGraphics.t at line 114
not ok 2
# Failed test 2 in t/BioGraphics.t at line 114 fail #2
ok 3
ok 4
ok 5
ok 6
ok 7
ok 8
ok 9
ok 10
ok 11
ok 12
ok 13
ok 14

Does the latter indicate a problem with my GD installation?

	-hilmar
-- 
-------------------------------------------------------------
Hilmar Lapp                            email: lapp@gnf.org
GNF, San Diego, Ca. 92121              phone: +1-858-812-1757
-------------------------------------------------------------

On Mon, 8 Jul 2002, Jason Stajich wrote:

> I think a lot of good bug fixes have gone in to the branch in the last few
> weeks, I'd like to do 1.0.2 at the end of the week.  I believe all of
> Lincoln's major graphics edits to support the latest GBrowse release are
> on the branch.  Additionally I've fixed quite a few FastA parsing bugs in
> SearchIO (thanks to the patience of Robin Emig), some fixed to the Search
> objects to bring them in line with Steve's BlastXX objects API, and fixed
> some implementation issues with the Tree objects.  I suspect there a few
> more bugs out there that have been fixed on the branch and would like to
> make them available in the release.  Please update the Changes file to
> reflect any changes you've put in on the branch.
> 
> If you have outstanding commits on the branch, email me, or get them in
> soon (before Thursday) and I'll release on Friday.  It looks like the
> tests are all passing as of right now.  I'll need some testers to make
> sure we are passing on most platforms (me thinks we should see about
> plugging into the CPAN tester system somehow).
> 
> As for the developer release, how about 1.1.0 next week?  This would
> include the bioperl-run (I'm actually liking it being a separate package,
> we'd need to discuss and update the INSTALL docs if it is released this
> way), bioperl-pipeline alpha code, and of course the core code in
> bioperl-live.  I'm not clear where the bioperl-db code is at this point,
> hopefully a little momentum for OBDA will get picked back up at BOSC and
> we can coordinate the bioperl|biojava|biopython OBDA compliant
> client/server releases (w/ related BioSQL,BioCORBA packages included as
> well).
> 
> At any rate the dev release would then be available a few weeks before
> BOSC and if major things happen we can do a 1.1.1 just before or after
> BOSC.
> 
> Comments?  Volunteers?
> 
> -jason
> 
>