As a member of the avant-garde, I only have two requirements in the solution
space:
1. Avalon-Framework not promoted as a Product 2. Not ready to re-version/re-brand Avalon as Avalon-5
Ah, but there in lines the paradox :)
Avalon-4 *WAS* Avalon-Framework
Avalon-4 *WAS* a Product.
I believe one can sum up all of the disagreements over the fact that Avalon-4 is now more than the framework, and is no longer a product.
I don't know what other's experience is in the commercial software market is, but sometimes you have to bump the version for marketing reasons. That's all that is being asked.
Bump everything to 5, and in doing so a clean line is drawn between the past and the future. What was planned for 5 can then be pushed to 6.
I propose:
* Bump to Avalon 5.
* On front page, under products, list:
Current:
Merlin
Legacy:
Avalon Framework
Components & Containers
* Legacy Avalon-Framework will goto the 4.1 API docs and its limited documentation
* Legacy Components & Containers will links to similar verbage as on the download page.
The past will not be hidden, and a clean line will be drawn for the future.
-pete
smime.p7s
Description: S/MIME cryptographic signature
