romichg
commented
10 years ago We have committed to certain features and functionality to be in 4.0 back in June. If we cannot deliver on a particular feature because of time constraints that is fine, and something we need to set the expectation on, now. But the new UI design, enhanced search and new navigation needs to be there. The new version should be called 4.0 and should be released at the end of Q3. The version numbers need to makes sense from a product/feature point of view, not from the coding point of view. Whatever has to be in the back end for this, should be there. If the current 3.5 back end will do everything that will meet all the functionality expectations of 4.0 that is great, if it needs to be enhanced (like for the search functionality) or changed that is something that we need to work on. As for the prototype numbering, I am about to share a document I was working on that would outline a proposal on how we should structure the milestones.
We kinda talked about this in one of our calls and my idea is that as I start adding 4.0 design to TM, at the moment the current 3.5 SiteData capabilities are powerful enough to implement the first batch of designs.
This will allow the full reuse of the 3.5 backend and functionality while we implement the 4.0 design.
This doesn't mean that we will ship a 3.6 version in 3 months (that is a business decision), but from a coding point of view, it makes sense:
From a backend point of view, I think it makes sense to move it to 4.0 when there are breaking changes with the 3.5 design