[henshin-dev] Should we introduce a new model version after renaming and

[Riegerf@xxxxxxxxxxxxxxxxxxxxxxx]

Hi everyone,

recently, we decided to change the names of some classes and methods,  
as well as to clean up the containment structure in order to improve  
software quality, ease of use and understanding. This led, however, to  
a change in the model. Since both the original and the refactored 2011  
model are very similar, it didn't appear neccessary to issue a new  
model version. As it turns out, some of our code seems to have  
problems with the new model. Since we do not know how our users use  
Henshin in their projects, I propose to issue a new "2012" model  
version instead of changing the 2011 model without changing its  
version. Doing so will lead to less confusion. Migration should be  
pretty straightforward and will only consist in renaming elements.

What do you think?

Felix