NUnit Framework

  1. Bug #1176462
  2. Activity log

Activity log for bug #1176462

Date Who What changed Old value New value Message
2013-05-05 01:47:15 Charlie Poole bug added bug
2013-05-05 01:47:31 Charlie Poole nunitlite: importance Undecided High
2013-07-20 03:01:16 Charlie Poole nunitlite: status New Triaged
2013-07-20 03:07:02 Charlie Poole nunitlite: milestone 1.0
2013-07-25 23:02:31 Charlie Poole nunitlite: milestone 1.0 3.0
2013-08-11 22:42:05 Charlie Poole affects nunitlite nunit-3.0
2013-08-11 22:42:05 Charlie Poole nunit-3.0: milestone 3.0
2013-10-19 02:40:02 Charlie Poole tags github
2013-10-19 02:40:04 Charlie Poole description Currently, it's only possible to do a release of NUnitLite on a machine with all the runtimes we support installed. This makes it difficult for contributors to handle releases. It would be better if the builds could be completed on different machines and then aggregated on a separate server. The main changes needed to the build script to accomplish this are: 1. Provide a remote location to which builds are published 2. Add a target to copy builds to that location. 3. Modify package targets to use that location. In order to make sure that all the builds for a release are all based on the same source, we will need to tag the published packages with a revision number and/or date. [Issue now tracked at https://github.com/nunit/nunit-framework/issues/11] Currently, it's only possible to do a release of NUnitLite on a machine with all the runtimes we support installed. This makes it difficult for contributors to handle releases. It would be better if the builds could be completed on different machines and then aggregated on a separate server. The main changes needed to the build script to accomplish this are: 1. Provide a remote location to which builds are published 2. Add a target to copy builds to that location. 3. Modify package targets to use that location. In order to make sure that all the builds for a release are all based on the same source, we will need to tag the published packages with a revision number and/or date.