Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (nike.apache.org: domain of arsen.abdrakhmanov@gmail.com
 designates 209.85.210.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGUes6H5w9Cg48jMddxS_xuTjwD6g2vhByDA91+dcJq4d2YAnQ@mail.gmail.com>
References: 
 <CAGUes6H5w9Cg48jMddxS_xuTjwD6g2vhByDA91+dcJq4d2YAnQ@mail.gmail.com>
Date: Thu, 29 Mar 2012 18:41:48 +0600
Message-ID: 
 <CAGUes6GqVVuMok1yhqF6Js_RE8fv0=1XByty-Dd0Pgw7Yw5SMA@mail.gmail.com>
Subject: Re: Geronimo release cycle
From: Arsen Abdrakhmanov <arsen.abdrakhmanov@gmail.com>
To: dev@geronimo.apache.org
Content-Type: multipart/alternative; boundary=14dae9340fbf2d58ce04bc610cb9

--14dae9340fbf2d58ce04bc610cb9
Content-Type: text/plain; charset=ISO-8859-1

Dear Team,

Thank you very much for your attention to my request and please, let me
give small comment regarding my previous message.

Frankly speaking, I have meant primarily the release cycle for 2.1.x and
2.2.x versions of Geronimo.
We were not using the 3.0 version of Geronimo, as there was no stable
non-beta release for it.
Actually, we were using the 2.2.1 version of Geronimo in our previous
project.
For the moment, I am in position to make a decision for moving to the
version 2.1.8 for new project, as the release is much newer.

The question was, that if the minor versions were released at least
semi-annually, it would be very usefull for us in terms of access to
bug-fixed versions.
In this case, we would never discuss in our company the variants with
downgrade to previous major version of application server.

Regarding the 3.0 version of Geronimo, I would be glad to use it in
upcoming projects, but if the newer minor versions of 3.0.x could be
released more frequently.

Hope, you got my idea.
Sorry for inconveniences caused.

Best regards,
Arsen Abdrakhmanov


2012/3/27 Arsen Abdrakhmanov <arsen.abdrakhmanov@gmail.com>

> Dear Geronimo Team,
>
> Actually, I am the fan of geronimo for more than 5 years already.
> For the moment, I am promoting the usage of Geronimo as a platform for
> non-critical applications in our company (banking industry in KZ).
> According to our company's internal policy, only official releases of
> open-source software products can be used for internal applications.
>
> Currently, the release cycle for Geronimo is about an year or even longer,
> so it takes significant amount of time before we could use an updated
> version of software with bug fixes and enhancements.
>
> Taking that into account, can you give any information on your plans to
> accelerate the release cycle for new versions of Geronimo?
>
> I think, it would be very useful for the whole geronimo user community, if
> the releases were published at least semi-anually.
> Hope, it can also increase the popularity of Geronimo among other
> application servers.
>
> Best regards,
> Arsen Abdrakhmanov
>
>

--14dae9340fbf2d58ce04bc610cb9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Team,<div><br></div><div>Thank you very much for your attention to my =
request and please, let me give small comment regarding my previous message=
.</div><div><br></div><div>Frankly speaking, I have meant primarily the rel=
ease cycle for 2.1.x and 2.2.x versions of Geronimo.</div>
<div>We were not using the 3.0 version of Geronimo, as there was no stable =
non-beta release for it.</div><div>Actually, we were using the 2.2.1 versio=
n of Geronimo in our previous project.</div><div>For the moment, I am in po=
sition to make a decision for moving to the version 2.1.8 for new project, =
as the release is much newer.</div>
<div><br></div><div>The question was, that if the minor versions were relea=
sed at least semi-annually, it would be very usefull for us in terms of acc=
ess to bug-fixed versions.</div><div>In this case, we would never discuss i=
n our company the variants with downgrade to previous major version of appl=
ication server.</div>
<div><br></div><div>Regarding the 3.0 version of Geronimo, I would be glad =
to use it in upcoming projects, but if the newer minor versions of 3.0.x co=
uld be released more frequently.</div><div><br></div><div>Hope, you got my =
idea.</div>
<div>Sorry for inconveniences caused.</div><div><br></div><div>Best regards=
,</div><div>Arsen Abdrakhmanov</div><div><br></div><div><br><br><div class=
=3D"gmail_quote">2012/3/27 Arsen Abdrakhmanov <span dir=3D"ltr">&lt;<a href=
=3D"mailto:arsen.abdrakhmanov@gmail.com">arsen.abdrakhmanov@gmail.com</a>&g=
t;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Dear Geronimo Team,<div><br></div><div>Actua=
lly, I am the fan of geronimo for more than 5 years already.</div><div>For =
the moment, I am promoting the usage of Geronimo as a platform for non-crit=
ical applications in our company (banking industry in KZ).</div>

<div>According to our company&#39;s internal policy, only official releases=
 of open-source software products can be used for internal applications.</d=
iv><div><br></div><div>Currently, the release cycle for Geronimo is about a=
n year or even longer, so it takes significant amount of time before we cou=
ld use an updated version of software with=A0bug fixes and enhancements.</d=
iv>

<div><br></div><div>Taking that into account, can you give any information =
on your=A0plans to accelerate the release cycle for new versions of Geronim=
o?</div><div><br></div><div>I think, it would be very useful for the whole =
geronimo user community, if the releases were published at least semi-anual=
ly.</div>

<div>Hope, it can also increase the popularity of Geronimo among other appl=
ication servers.</div><div><br></div><div>Best regards,</div><div>Arsen Abd=
rakhmanov</div><div><br></div>
</blockquote></div><br></div>

--14dae9340fbf2d58ce04bc610cb9--