I don't disagree, Todd. The 'process' and build are pretty stable right now right? That would be the main thing that devalues the effort.
I have a few ideas for this which I don't want to get anyone too excited about just now, so I think I'll just take this one on myself. :) Don't expect it any time soon though. ;-) Cheers, Chris 2009/10/26 Todd Volkert <[email protected]>: > Sounds like a good idea, though I think it'd be non-trivial to implement. > > Cheers, > -T > > On Mon, Oct 26, 2009 at 8:28 AM, Christopher Brind > <[email protected]>wrote: > >> I'd use it ;-) >> >> Your MD5 demo has given me another idea for a demo which could be >> quite useful to the whole team (sorry for hijacking your thread) ... >> >> How about an app which validates a Pivot release and outputs a report >> which can be copied and pasted in to an email to send to the team at >> release time? ;-) >> >> It would: >> - take a release URL as input >> - download the distribution archives >> - check the signatures >> - build the source archives >> - allow the user to run each demo and mark it as 'working' >> - have to be clever enough to cope with minor change to the build >> (e.g. addition or removal of demos) without putting any dependency in >> to the Pivot build itself >> >> What do you think? >> >> Cheers, >> Chris >> >> >> 2009/10/26 Sandro Martini <[email protected]>: >> >> I myself wouldn't use it, but if you have a use for it, have at it :) >> > I use a little utility like this, called WinMd5Sum (take a look at the >> > screenshot), small, fast and very useful for lazy users ( like me :-) >> > ). >> > >> > Could be useful for others too, and also for us to test if all works >> > good (performances, memory used by Java, etc). >> > >> > I'll put in list of my (long) TODO list ... but at low priority. >> > If someone is interested, tell me. >> > >> > Bye >> > >> >
