2009/1/19 Vladimir Savic <[email protected]>
> I know many of you don't like kde release numbering scheme, but I
> don't think we would lose much if using it here. I'd go with 1.9.xx
> and release occasionally (using "alpha" and "beta" suffixes).
> The only problem with this is that we will eventually hit 2.0 as
> stable. I don't mind, though.
All numbering schemes have their own pros and cons.
I am not against publishing development releases. Somebody would
just have to take responsibility of reporting the past development.
>From the marketing point of view, 1.9.xx is equally bad as 2.0.
I know that developers love these numbers, because they are able
to order the development chronologically. It is kind of having an own
type of timer to track the developing time: 1 year 0 month 2 days,
1 year 8 month 7 days, 1.9.9, 2.0.0 etc. The only practical issue
is to keep things in time order.
Maybe it would be better to have one numbering schedule for
development, and another one for releasing. Actually, we even do have
(1) svn number (currently 9753) for developers
(2) release number (currently 1.7.2) for users and packagers
Of these (1) is deterministic and (2) is arbitrary.
The fact that (2) is arbitrary runs us constantly into the situation that
there appears a discussion: "Whether we call this release a 1.X or
even X.0" Really, who cares? The packagers? I don't care if they do.
There appears a mental barrier to release X.0, but really, who cares.
I do not want to have such barriers. I am much more interested,
whether the program can do this and that. Whether it works or crashes.
Whether it has a working development community or whether it will die.
I would like really like to make (2) deterministic, because I find these
discussions on "what will be the next release number" quite superstitious.
There is no need to reinvent a timer. We could as well track the time
since start of the start of the development of Rosegarden, i.e.,
every now and then celebrate the aging of Rosegarden:
"Rosegarden team celebrates the 20 years of development by
releasing Rosegarden v20"
So, somebody, please invent a deterministic way to give the release number.
I do not want to give a new name to my child again and again.
The only psycological barrier should in the time whether to release or not.
Like Shakespeare would put it: "To release or not to release, that's the
question."
--
Heikki
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
