Should we rename Lenya 1.4 to 2.0?

[Thorsten Scherler <th...@apache.org>]

Hi users,

on the dev list we are talking about to rename 1.4 to 2.0.

The new major version number implies:

* major architectural changes
* significant upgrade effort
* major new functionality
* lots of cool new things to learn about

and a ".0" minor version implies:

* some risk of bugginess, until the ".1" or ".01" release comes out.

That describes the current Lenya code pretty well.

However some devs point out that the disadvantage is the community knows
the next release as 1.4.  Many people are using various development
versions.  Changing the name will cause confusion.  Directories are
often named with the version number so this increases the work of
"upgrading'" to the production release.

"2.0" sounds less stable than "1.4.0". The old skills still apply, but
this may discourage less innovative developers.

Changing the version number may attract a new audience, but may damage
the current community.  Some of us are not certain the change will
accomplish enough to offset the effort.

What do you as user think about this?

You are encourage to participate in the currently running vote thread
http://marc.info/?t=118354802100001&r=1&w=2 and/or air your opinion
here.

TIA

salu2
-- 
Thorsten Scherler                                 thorsten.at.apache.org
Open Source Java                      consulting, training and solutions


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org