From: Darren K. <da...@pr...> - 2009-11-18 18:43:42
|
I think we should move to as much automated post-build testing as possible. This is on my list of things to get going, but it's going to have to wait a few weeks until after my Finals. This would basically be a bunch of scripts that would test the output of msconvert, etc. on various input files after the build. I propose that, unless someone has time to do more, someone pushes the "release" button once a month, and the post-build scripts will give us more confidence in the integrity of these builds. Darren On Wed, Nov 18, 2009 at 8:05 AM, Matthew Chambers <mat...@va...> wrote: > We have no established method for determining when a release should > happen or collecting the changes since the last release. We could > compile an automatic list of all SVN commits with the log comments and > ask developers to tweak their log comments for use in release notes. But > as for determining when a release should happen, I don't know. The way > the release would work now, it's hardly better than using the snapshot > builds (as long as all tests pass). It would be very hard to separate > unstable code from stable code, and not doing that could lead to long > delays between releases (and by the time the unstable code is stable, > the stable code may be unstable). This is the purpose of branching to a > release branch and only merging stable code it. This takes considerable > effort though (Boost honors them as "release managers") and I don't know > if any of our developers have the time to commit to it on a regular > basis. Perhaps we need to rotate responsibility? > > -Matt > > > Parag Mallick wrote: >> Hi All, >> >> I've been routinely sending folks to the daily builds instead of the actual build on the website because so much has happened since that came out. Any chance we can get a package for a formal release soonish? Also, does there exist somewhere a list of 'this has changed since the last formal release?' sort of doc anywhere? Lastly - now that the magic release button exists, how should releases happen? Is there some quota of 'major change has happened' or 'X-amount of time has passed' etc? >> >> Thx. >> ~ Parag M ~ >> > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > proteowizard-developer mailing list > pro...@li... > https://lists.sourceforge.net/lists/listinfo/proteowizard-developer > |