8093 2015-08-04 10:48:44 +0000 Release change doesn't check machine compatibility 2016-04-22 15:55:07 +0000 1 1 7 Build System, Metadata & Runtime Toaster toaster unspecified x86 Multiple RESOLVED OBSOLETE Medium enhancement Future 1 michael.g.wood elliot.smith alexandru.damian belen.barros.pena cristiana.voicu jessica.zhang --- --- No (bug/feature does not impact docs) oldest_to_newest 52811 0 michael.g.wood 2015-08-04 10:48:44 +0000 If you change the release of the project we currently don't check to see if the machine set is still valid. 53023 1 mhalstead 2015-08-12 15:58:09 +0000 Clearing 2.0 milestone 54133 2 elliot.smith 2015-09-16 07:18:25 +0000 We could remove the capability to change the release for a project, so it's frozen when you create the project. If you want a project for other releases, make a new project. This would considerably simplify things. 54143 3 belen.barros.pena 2015-09-16 09:40:13 +0000 How do we know if the machine is valid or not? Do you mean if it is still provided by one of the layers in the project after the release change? About Elliot's suggestion of not being able to change the release, that is a bit draconian, particularly because we don't have an easy way to delete projects right now. What if I selected the wrong release by mistake? (which, by the way, just happened to me yesterday) I rather keep the ability to change the project release, if at all possible. 61562 4 belen.barros.pena 2016-04-22 15:55:07 +0000 We no longer allow users to change the project release, so this should now obsolete.