Change Details

We've been using the #scap3 sprint very effectively (clean board, only adding things we wanted to it, etc) and now that scap 3.0 is tagged/released, it's time to close that sprint. But, we don't want to go back to only having #deployment-systems. Thus, we'd like #scap to be created and we can move all scap-related tasks to it (I volunteer to do a first pass).

We've been using the #scap3 sprint very effectively (clean board, only adding things we wanted to it, etc) and now that scap 3.0 is tagged/released, it's time to close that sprint. But, we don't want to go back to only having #deployment-systems. Thus, we'd like #scap to be created and we can move all scap-related tasks to it (I volunteer to do a first pass). Similar reasoning for #trebuchet as well.

We've been using the #scap3 sprint very effectively (clean board, only adding things we wanted to it, etc) and now that scap 3.0 is tagged/released, it's time to close that sprint. But, we don't want to go back to only having #deployment-systems. Thus, we'd like #scap to be created and we can move all scap-related tasks to it (I volunteer to do a first pass). Similar reasoning for #trebuchet as well.