Changes to release process *: How long do we need to run on CSL/NMI/CHTC? *: How much notice can we give to CSL/NMI/CHTC? -*: *We need release notes ahead of beta testers upgrade* - +*: We need release notes ahead of beta testers upgrade *: Can we change the Condor release version to include the run id? Test pool? *: Should we run a test pool that we upgrade before the pre-release to NMI/CHTC? -*:: Should NMI be the test pool +*:: Should NMI have a shadow pool that functions as the test pool? *: Maybe NMI should not be running the development series? *: Can we submit VMs to CHTC? The VMs can have any version of Condor installed Testing of tarballs: *: Still working on integrating the tarball tests in *: RPM/Deb tests up next -*::How important are these? Tim indicated that these are a stopgap measure and may not be extensively used (because someone is making Debian source packages and RPMs are in Fedora and will eventually be in RH6?) *: Should we do extra manual tests before release checking for things that are hard to automate? Examples: *:: Difference in tarball size between this and last version *:: Difference in number of files between this and last version @@ -24,9 +22,9 @@ *:: Could we do this in NMI using "parallel" ability? *:: If not automated in NMI what about just doing a manual test before release? -AIX machine is uberslow -*: when users submit one-off builds can they evict our nightly runs? -*: can we drop AIX in 7.6? What about HPUX and Solaris? +Platform list +*: Meet with NMI and Condor to get platforms to drop +*: Likely candidates include AIX, HPUX Improvements to build status page: *: Change tasks to be sorted by the order they run (rather than alpha order)
