Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (athena.apache.org: domain of genspring@gmail.com
 designates 209.85.215.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CACR2OsfNuvHR-RR_EHeZwpDyX3_M3k1is5ksqo2JiGsJkn63-w@mail.gmail.com>
References: 
 <CAGUes6H5w9Cg48jMddxS_xuTjwD6g2vhByDA91+dcJq4d2YAnQ@mail.gmail.com>
	<CACR2OsfNuvHR-RR_EHeZwpDyX3_M3k1is5ksqo2JiGsJkn63-w@mail.gmail.com>
Date: Wed, 28 Mar 2012 18:08:27 +0800
Message-ID: 
 <CANjG=51TyzgkCs2pvXy5d8eK70bnEWteZ+ThNeet9BL6AonLTQ@mail.gmail.com>
Subject: Re: Geronimo release cycle
From: Shawn Jiang <genspring@gmail.com>
To: dev@geronimo.apache.org
Content-Type: multipart/alternative; boundary=0015174be4cce6445d04bc4ac980

--0015174be4cce6445d04bc4ac980
Content-Type: text/plain; charset=ISO-8859-1

1.x   J2EE 1.4
2.0   Java EE 1.5
2.1  Java EE 1.5
2.2   Java EE 1.5
3.0   Java EE 1.6

Considering the previous practice, we'd better to move current trunk to 3.1
and change current beta branch to 3.0.

On Tue, Mar 27, 2012 at 11:48 PM, Forrest Xia <forrestxm@gmail.com> wrote:

> Saw this query, have an idea about the current release roadmap.
>
> 1. Can we move the current incomplete trunk work to version 4 of geronimo?
> 2. Rename 3.0-beta branch as the formal 3.0 release?
>
> Any thoughts?
>
> Forrest
>
> ---------- Forwarded message ----------
> From: Arsen Abdrakhmanov <arsen.abdrakhmanov@gmail.com>
> Date: Tue, Mar 27, 2012 at 7:20 PM
> Subject: Geronimo release cycle
> To: user@geronimo.apache.org
>
>
> 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
>
>
>
>
> --
> Thanks!
>
> Regards, Forrest
>
>


-- 
Shawn

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

1.x =A0 J2EE 1.4<div>2.0 =A0 Java EE 1.5</div><div>2.1=A0=A0Java EE 1.5</di=
v><div>2.2=A0
=A0Java EE 1.5=A0</div><div>3.0 =A0 Java EE 1.6</div><div><br></div><div>Co=
nsidering the previous practice,=A0we&#39;d better to move current trunk to=
 3.1 and change current beta branch to 3.0.</div><div><br><div class=3D"gma=
il_quote">
On Tue, Mar 27, 2012 at 11:48 PM, Forrest Xia <span dir=3D"ltr">&lt;<a href=
=3D"mailto:forrestxm@gmail.com">forrestxm@gmail.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
Saw this query, have an idea about the current release roadmap. <br><div cl=
ass=3D"im"><br>1. Can we move the current incomplete trunk work to version =
4 of geronimo? <br></div>2. Rename 3.0-beta branch as the formal 3.0 releas=
e?<br>
<br>Any thoughts?<br>

<br>Forrest<br><br><div class=3D"gmail_quote"><div class=3D"im">---------- =
Forwarded message ----------<br>From: <b class=3D"gmail_sendername">Arsen A=
bdrakhmanov</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:arsen.abdrakhmanov@=
gmail.com" target=3D"_blank">arsen.abdrakhmanov@gmail.com</a>&gt;</span><br=
>

Date: Tue, Mar 27, 2012 at 7:20 PM<br>Subject: Geronimo release cycle<br>To=
: <a href=3D"mailto:user@geronimo.apache.org" target=3D"_blank">user@geroni=
mo.apache.org</a><br><br><br></div><div><div class=3D"h5">Dear Geronimo Tea=
m,<div>
<br></div><div>Actually, I am the fan of geronimo for more than 5 years alr=
eady.</div>
<div>For the moment, I am promoting the usage of Geronimo as a platform for=
 non-critical 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>
</div></div></div><span class=3D"HOEnZb"><font color=3D"#888888"><br><br cl=
ear=3D"all"><br>-- <br>Thanks!<br><br>Regards, Forrest<br><br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r>Shawn<br>
</div>

--0015174be4cce6445d04bc4ac980--