RE: [wtp-dev] What to do about feature version numbers?

[David M Williams <david_williams@xxxxxxxxxx>]

Yes, it was discussed and decided at
PMC meeting ... it was felt the lessor evil was to go ahead and bump up
to 2.0, in the interest of end-user usability (and readability). 
(for JST and WST, JSF and JPA features
still at 1.0). 

I'll make some mass changes to any features
I have write access to ... and we can tweak next week if I miss any. 

Thanks, 

BTW, this does not mean we do not agree
with 
http://wiki.eclipse.org/index.php/Version_Numbering
 

Just that it doesn't work well for end-users
looking at long lists of features in the 'about' box (or, update site).

There may be "marketing version
labels" supported someday to make both technical accuracy and readability

both feasible, but in the mean time,
there's little reason to constrain feature versions. 

Some adopters _MIGHT_ have to adjust
their features ... if they said in one of their features, 
for example, that wst.xml feature version
1.6 was required. 
But ... the current recommendation is
that dependancies be expressed in terms of plugins anyway, 
not features. 

Thanks all.

John Lanuti/Raleigh/IBM@IBMUS
Sent by: wtp-dev-bounces@xxxxxxxxxxx

03/27/2007 02:59 PM

Please respond to
"General discussion of project-wide or architectural issues."        <wtp-dev@xxxxxxxxxxx>

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	RE: [wtp-dev] What to do about feature  version numbers?

Any other comments here?  Was this discussed in the PMC?  Do
we need to discuss on Thursday? 

My feeling is that, to users, they would expect to see 2.0.  I think
1.6 would be confusing to them.  Raghu is right though, to developers,
bumping to 2.0 might set the wrong expectations. 

John Lanuti
IBM Web Tools Platform Technical Lead, IBM Rational
IBM Software Lab - Research Triangle Park, NC
jlanuti@xxxxxxxxxx
t/l 441-7861

"raghunathan srinivasan" <raghunathan.srinivasan@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

03/26/2007 12:40 PM

Please respond to
"raghunathan.srinivasan@xxxxxxxxxx"        <raghunathan.srinivasan@xxxxxxxxxx>; Please respond to
"General discussion of project-wide or architectural issues."        <wtp-dev@xxxxxxxxxxx>

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	RE: [wtp-dev] What to do about feature  version numbers?

I have moved JSF to version 1.0. 
  
For WST and JST, my preference is to follow the guideline and stick to
1.6. 2.0 sets the wrong expectation of major changes in those projects.
-Raghu

---

From: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx]
On Behalf Of David M Williams
Sent: Sunday, March 25, 2007 10:54 PM
To: wtp-dev@xxxxxxxxxxx
Subject: [wtp-dev] What to do about feature version numbers?
  

Many of our WST and JST features are still versioned 1.6, which is what
we bumped 
to right after 1.5 was released. 

My thinking is that the WST and JST features should be versioned 2.0, to
match "WTP 2.0". 
This does not technically match the guidelines put forth in 
http://wiki.eclipse.org/index.php/Version_Numbering
which would recommend a bit closer relation to the type of change in contained
plugins 
to the feature version ... which means we should leave our features at
1.6. 

It seems to me, though, that users looking at a list of installed features
would expect 
them to match 2.0. In other words, seems to me, the JST and WST features
are more 
of a "marketing number" related to the major yearly release,
rather than a runtime constraint
as the plugin versioning is. 

What do others think? 1.6? 2.0? Don't care? 

BTW, I do think the JPA and JSF features should be 1.0, since this is the
first year of 
their release. 


_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev