Hi all,
with switching YaST into Ruby we reach an important milestone and also
do a major change in YaST after many years. So we would like to emphasize
this change by increasing the YaST version to number 3.
With version 3 we tell all users that there is an important change
(although under the cover, look&feel will be the same).
And this could be also used as a marketing feature for new products... ;-)
There are basically these approaches:
- Keep number "2" in the package names, just increase the current version number
(e.g. yast2-3.0.0, yast2-packager-3.0.0, ...), but this looks a little bit
strange.
- Update also the package names to contain "3", e.g. have yast3-3.0.0,
yast3-packager-3.0.0... This looks better and uses the old schema.
- Remove the number from the package names completely, e.g. have yast-3.0.0,
yast-packager-3.0.0... (This would be also future proof as it allows easy
switching to version 4 in the far far future :-))
The first solution is the easiest one, we would just need to update
the VERSION files.
The other solutions need additional support for correct update (additional
Provides/Obsoletes in spec files) and would also need extra work for testing
updates in real systems (think also of SLE11 upgrades).
So there are pros and cons for each solution and therefore I'd like to start a
discussion here about the version numbering.
What do you think about it?
--
Best Regards
Ladislav Slezák
Yast Developer
------------------------------------------------------------------------
SUSE LINUX, s.r.o. e-mail: [email protected]
Lihovarská 1060/12 tel: +420 284 028 960
190 00 Prague 9 fax: +420 284 028 951
Czech Republic http://www.suse.cz/
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
