You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by Thorsten Scherler <th...@juntadeandalucia.es> on 2004/06/01 08:56:06 UTC
Release management (Re: Lenya 1.2 was NOT released)
Andreas Kuckartz wrote:
>Please remove the "Lenya 1.2 Released (26 April 2004)" line before someone
>"higher up" complains...
>
>
>
...that is already to late, a couple of month ago that was in this list ;-)
>The simple fact is: currently no released version exists.
>
>Andreas
>
>
Ok, I can do that but I reckon that should normally do somebody that
knows which version we on. I dunno think that we do not have jet
released a version. I think we are on lenya 1.0 (the initial version of
lenya). ...but CVS is on 1.2dev (like Michi once stated),... I will
change the above to "Lenya 1.2dev Released (26 April 2004)". So nobody
will complain ;-).
I think we have to discuss the versioning and release process because
this seems not to be clear for everybody (me included). In the future I
wish a clear diferentation between
- Releases (Target audience are the normal users -> stable version,
nearly all bugs are fixed)
- Dev (Target audience are the devs -> unstable version, for future
feature testing,...)
- RC (Target audience devs and user -> testing of rc, after the testing
phase (like incubation) we decide to do the release)
IMO a release process should be follow the following patern:
Dev-->RC-->Release
There can be more than 1 dev version in the head (as different branches
e.g. 1.4 dev with publets; 1.6 dev with db-integration; ...).
There is only *one* RC for *one* release. To keep track of the version
and the targeted release of the RC we should use something like "1.2
RC4, 1.2 RC5, ..." as we already do. The releases on the end should be
all downloadable. Trying to say if I could find any versioning number in
our download area than I would know which version we use.
King regards
King regards
thorsten
--
Thorsten Scherler
Departamento de Desarrollo de Proyectos
Sociedad Andaluza para el Desarrollo de la Sociedad de la Información S.A.U.
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Correct version of lenya (Re: Release management )
Posted by Thorsten Scherler <th...@juntadeandalucia.es>.
Michael Wechner wrote:
> [...]
> but anyway, I agree that our website needs to be updated re the correct
> version, maybe similar to Lucene
[...]
Hi michi,
can you please correct that and commit it, I will do an update of our
website after work.
I will package today our skin like suggest in a mail in forrest dev
(today 09:56).
Dave Brondsema wrote:
> A better option might be to package it and host it yourself and then
> we can add
> it to http://xml.apache.org/forrest/skins/skins.xml (the default skins
> descriptor)
So point 1 from http://issues.apache.org/bugzilla/show_bug.cgi?id=29032
is gone by tonight.
I will further look in the menu problematic.
Right now the update process is *not* using the docs-new pub!!! I
created an independent forrest pub for that! Would you like me to commit
that into /src/forrest or should I wait till after the release. Maybe
till than I have it again in our pub structure. Other possibility is to
make it downloadable on my webpage or the public_html at
http://cvs.apache.org/~thorsten/.
I volunteer in the meantime for any website update.
WDYT?
--
Thorsten Scherler
Departamento de Desarrollo de Proyectos
Sociedad Andaluza para el Desarrollo de la Sociedad de la Información S.A.U.
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: Release management (Re: Lenya 1.2 was NOT released)
Posted by Andreas Kuckartz <A....@ping.de>.
> again ;-) I don't think 1.4RC5 has the same meaning as 1.3.5, but maybe
> I am wrong (plz see below) ...
I am not sure if the following makes clear what I mean :-)
1.4RC5 = 1.3RC5 = 1.4dev5 = 1.3dev5
1.3.5 = 1.3RC5
result:
1.4RC5 = 1.3.5
1.4dev5 = 1.3.5
and if 1.3.5 is accepted to be released:
1.4.0 = 1.3.5
The first "development" version after the release of 1.2 would be 1.3.0
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: Release management (Re: Lenya 1.2 was NOT released)
Posted by Michael Wechner <mi...@wyona.com>.
Andreas Kuckartz wrote:
>Thorsten Scherler wrote:
>
>
>"After the release of 1.2 I suggest this change: use a similar numbering scheme
>as in the Cocoon project and use unequal minor numbers for development versions.
>For example: 1.3.5 instead of 1.4RC5 and 1.4.0 instead of 1.4."
>
>
again ;-) I don't think 1.4RC5 has the same meaning as 1.3.5, but maybe
I am wrong (plz see below) ...
but anyway, I agree that our website needs to be updated re the correct
version, maybe similar to Lucene
11 May 2004 - Lucene 1.4 Release Candidate 3 Released
A new release of is available with many new features and bug fixes.
See CHANGES.txt
<http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-lucene/CHANGES.txt?rev=1.85>
for details. Binary and source distributions are available here
<http://cvs.apache.org/dist/jakarta/lucene/v1.4-rc3/>.
26 December 2003 - Lucene 1.3 Final Released
A new release of is available with many new features and bug fixes.
See CHANGES.txt
<http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-lucene/CHANGES.txt?rev=1.65>
for details. Binary and source distributions are available here
<http://cvs.apache.org/dist/jakarta/lucene/v1.3-final/>.
>I think a differentiation between "development versions" and "release
>candidates" is not needed and overkill. In the future every development version
>should potentially be releasable.
>
>Andreas
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
>For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
>
>
>
>
--
Michael Wechner
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://cocoon.apache.org/lenya/
michael.wechner@wyona.com michi@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org
Re: Release management (Re: Lenya 1.2 was NOT released)
Posted by Andreas Kuckartz <A....@ping.de>.
Thorsten Scherler wrote:
> I dunno think that we do not have jet released a version.
> I think we are on lenya 1.0 (the initial version of lenya).
Again: 1.0 was released (prematurely) and withdrawn due to legal reasons
(concerning libraries which were included).
> I think we have to discuss the versioning and release process because
> this seems not to be clear for everybody (me included).
Agreed. Here is the proposal for a numbering scheme which I posted on May 26:
"After the release of 1.2 I suggest this change: use a similar numbering scheme
as in the Cocoon project and use unequal minor numbers for development versions.
For example: 1.3.5 instead of 1.4RC5 and 1.4.0 instead of 1.4."
I think a differentiation between "development versions" and "release
candidates" is not needed and overkill. In the future every development version
should potentially be releasable.
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org