atom feed46 messages in org.apache.cocoon.devRe: Renaming Corona to Cocoon 3.0 and...
FromSent OnAttachments
Reinhard PötzAug 6, 2008 4:19 am 
Felix KnechtAug 6, 2008 4:28 am 
Andrew SavoryAug 6, 2008 4:30 am 
Daniel FagerstromAug 6, 2008 4:39 am 
Thorsten ScherlerAug 6, 2008 4:54 am 
Carsten ZiegelerAug 6, 2008 4:56 am 
Jasha JoachimsthalAug 6, 2008 6:15 am 
Peter HunsbergerAug 6, 2008 7:30 am 
Ralph GoersAug 6, 2008 7:43 am 
Joerg HeinickeAug 6, 2008 8:09 am 
Vadim GritsenkoAug 7, 2008 5:23 am 
Bertrand DelacretazAug 8, 2008 7:06 am 
Alfred NathanielAug 8, 2008 4:23 pm 
Reinhard PötzAug 10, 2008 1:15 am 
Reinhard PötzAug 10, 2008 1:19 am 
Vadim GritsenkoAug 10, 2008 12:08 pm 
Reinhard PötzAug 10, 2008 1:18 pm 
Vadim GritsenkoAug 10, 2008 3:46 pm 
Reinhard PötzAug 16, 2008 7:19 am 
Ralph GoersAug 16, 2008 7:32 am 
Grzegorz KossakowskiAug 17, 2008 7:44 am 
Reinhard PötzAug 17, 2008 8:14 am 
Sylvain WallezAug 17, 2008 10:41 am 
Grzegorz KossakowskiAug 18, 2008 2:23 am 
Rainer PruyAug 18, 2008 2:43 am 
Grzegorz KossakowskiAug 18, 2008 3:04 am 
Jeremy QuinnAug 18, 2008 3:42 am 
Jeremy QuinnAug 18, 2008 4:07 am 
Reinhard PötzAug 18, 2008 4:21 am 
Sylvain WallezAug 18, 2008 5:12 am 
Sylvain WallezAug 18, 2008 5:13 am 
Sylvain WallezAug 18, 2008 5:47 am 
Grzegorz KossakowskiAug 18, 2008 6:22 am 
Reinhard PötzAug 18, 2008 6:23 am 
Grzegorz KossakowskiAug 18, 2008 6:28 am 
Reinhard PötzAug 18, 2008 6:29 am 
Sylvain WallezAug 18, 2008 8:04 am 
Ralph GoersAug 18, 2008 8:21 am 
Carsten ZiegelerAug 18, 2008 8:41 am 
Jeremy QuinnAug 18, 2008 8:56 am 
Sylvain WallezAug 18, 2008 8:57 am 
Grzegorz KossakowskiAug 19, 2008 4:53 am 
Jeremy QuinnAug 19, 2008 8:03 am 
Jeremy QuinnAug 19, 2008 8:10 am 
Reinhard PötzAug 20, 2008 5:44 am 
Peter HunsbergerAug 20, 2008 7:32 am 
Subject:Re: Renaming Corona to Cocoon 3.0 and infrastructure
From:Rainer Pruy (Rain@Acrys.COM)
Date:Aug 18, 2008 2:43:06 am
List:org.apache.cocoon.dev

Just another 0.01€ in the same direction:

most "developing" users (esp. the ones developing cocoon itself) would qualify
as hackers. Those are used to associate special meanings with groups of version numbers as a number of other projects follow similar rules (e.g. Linux for long used
that even/odd numbering scheme).

However, as Cocoon will (and should) attract non hacker users, on a first view, what will indicate to them, that version 3.1.2 is not
"superior" to 3.0.9? (superior aka later or more mature)

While I personally am quite fine with any versioning scheme, I do think, it is absolutely necessary to have a policy document explaining it to accidental users. And this nearly at the same time they will detect something
like cocoon does exist at all.

Rainer

Sylvain Wallez schrieb:

Reinhard Pötz wrote:

Versioning

------------------------------- For Cocoon 2 there have been proposals that all odd versions are development/alpha versions and all even versions are stable releases.

I like this idea and propose that we follow this versioning schema in Cocoon 3: All 3.0.x releases are marked as development versions and we clearly explain this on the website and the READMEs of all artifacts.

When we believe that the community and the technology are stable, we do a 3.1.0 release.

I think this is less confusing than appending alpha, beta or milestone postfixes.

I would say the contrary. Let's not forget that most of our users aren't hard-core developers (they love Cocoon because they can do complex stuff without programming) and they aren't used to this odd/even versioning scheme that comes from the Linux kernel.

Rather than that, it seems to me that most of the "normal" (i.e. non hard-core hacker) people consider a version without any "beta", "milestone" or other suffix as an official stable release. A well-known example is Firefox that goes through a series of milestones, beta and RC version before releasing a stable version with the same number. Eclipse does the same.

Also, I haven't voted for the renaming Corona to Cocoon 3.0 as I was on vacation, but I really think this is too early. Cocoon 2.2 is just out and we announce a 3.0. This will most probably lead people to consider 2.2 as a transition to 3.0 and just not use it, and thus just look elsewhere. Stated clearly, I have fears that just as Maven almost killed the developer community for 2.2, announcing a 3.0 now will kill the user community.

My 0.02 euros.