[Live-demo] Re: [OSGeo] #778: regression test

OSGeo trac_osgeo at osgeo.org
Thu Aug 25 22:11:49 PDT 2011


#778: regression test
-------------------------+--------------------------------------------------
 Reporter:  jive         |       Owner:  live-demo@…              
     Type:  enhancement  |      Status:  new                      
 Priority:  minor        |   Milestone:  Unplanned                
Component:  LiveDVD      |    Keywords:  qa                       
-------------------------+--------------------------------------------------

Comment(by hamish):

 Hi,

 some thoughts--

 any file manifest belongs with the ISO and md5s for that at
   http://live.osgeo.org/dev/build/

 while potentially a very valuable tool, it doesn't need to be on the disc,
 doesn't belong in svn, and doesn't really belong at download.osgeo.org
 either.

 sounds like the generating command belongs in a build script somewhere
 after build_iso.sh? (or before?)

 Until we go to automated fortnightly/nightly dev builds of the disc,
 putting this in a cron job or by-date doesn't gain us anything. It's a
 single-time post-build task, so gets versioned the same as the build
 version number.

 The manifest file should be bzip2'd; you can compare with `bzdiff` as you
 like.

 There is no way for the build to know what the previous version was unless
 we do some svn log+diff command line magic to compare VERSION.txt vs
 latest_rev - 1. But that's fragile- you might be more interested to
 compare rc5 vs rc3 if rc4 was a dud.

 It should not be automatically posted to the mailing list. I keep a rather
 tight attachment size limit there on purpose as some subscribers connect
 over slow bad connections, tiny mailbox sizes, or over expensive cell
 phone connections, and I would hazard a guess that most of us are already
 drowning in email. This may not be you, but it is others. automated things
 like svn commit log messages and automated QA results, belong online or in
 a second dedicated mailing list IMO.

 finally file name should say what's in it, like
 ${NAME}_${RELEASE}_manifest.txt
 (I think the "contents" name space is already claimed by overview.rst)


 2 or 3c,
 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/778#comment:1>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.


More information about the Osgeolive mailing list