Context Navigation

Changes between Initial Version and Version 1 of Ticket #5160, comment 4

initial	v1
4	4	For lite, I made an assumption that we'd remove the bbPress SVN external, and add in the bbPress files when building a release package as a way of maintain backpat yet keeping a dev environment clean as of much deprecated stuff as possible. For example, I'd propose to include BP-Default in the same way if/as/when we move it to wp.org/themes/.
5	5
6		Did you have further thoughts to other items for the dev build for lite? PHPUnit? We'd definitely want a `watch` command added separately so we can lint JS during development. It looks like I didn't write this above, but with both the proposed bp-grunt and bp-grunt-lite, we'd no longer be committed minified CSS/JS to trunk. We'd only want those for the release packages. Sites running new /trunk/ as a checkout would load up the un-minified CSS/JS.
	6	Did you have further thoughts to other items for the dev build for lite? PHPUnit? We'd definitely want a `watch` command added separately so we can lint JS during development. It looks like I didn't write this above, but with both the proposed bp-grunt and bp-grunt-lite, we'd no longer be committing minified CSS/JS to trunk. We'd only want those for the release packages. Sites running new /trunk/ as a checkout would load up the un-minified CSS/JS.