On Fri, Jun 14, 2013 at 08:53:47AM -0400, David Golden wrote: > On Fri, Jun 14, 2013 at 8:34 AM, Nicholas Clark <nick@ccl4.org> wrote: > > Should this test always be expected to pass? > > > > $ ./perl -Ilib -MModule::CoreList -le 'print Module::CoreList->find_version($]) ? "ok" : "not ok"' > > not ok > > > > > > That's effectively the problem that Andreas hits. So should we add that as > > a test? (And ensure that the version bump automation keeps it passing) > > We have a sort of race condition in that we need M::CL shipped to CPAN > without the newly bumped version. > > If there's a clean commit point before the bump, (possibly just the > release tag) I suppose BinGOs can jump back to that commit and release > from it. > > I'm also not sure the version bump automation is going to easily play > nice with M::CL's needs. > > But I like the idea of a Porting test to ensure M::CL gets updated > when the version is bumped, whether automated or not. > I have been taking the Module-CoreList to release to CPAN either from the tarballs that release managers make available or from the tagged release. -- Chris Williams aka BinGOs PGP ID 0x4658671F http://www.gumbynet.org.uk ==========================Thread Previous | Thread Next