|Plugin Versioning [message #503485]
||Mon, 14 December 2009 12:52
| peter barry
Registered: October 2009
hi, not sure if this is the correct newsgroup for this post ...|
i'm looking for peoples experience with plugin versioning (or lack thereof)
we are developing a product based many plugins. the product consists of different internal 'domains'. these domains are seperated in such a way so that they can come and go without causing problems in the overall tool. so its possible for us to release these domains individually if we wanted to. our current release strategy is to release all these domains for every release allowing us to ignore the testing between different versions of these domains.
so in this scenario do we really need to worry about the versions of the plugins? could we maintain the version of the plugins at 1.0.0 (or maybe the product release version)?
if we did change our release strategy then we could introduce proper plugin versioning then.
anyone have similar experiences and if so any lessons learned?
|Re: Plugin Versioning [message #503767 is a reply to message #503760]
||Tue, 15 December 2009 11:50
Originally posted by: richkulp.us.NO_SPAM.ibm.com|
Even if you always release everything it is still a good idea to give
new versions/revisions. That way when you look at an Eclipse
configuration you know immediately what level of your code is installed.
Powered by FUDForum
. Page generated in 0.03247 seconds