version number

[David Sean Taylor <da...@bluesunrise.com>]

Marky made a good point about versioning.
I don't like the a1 a2 naming, I think that people find it confusing.
Why don't we just call the next release 1.4?

> -----Original Message-----
> From: Marky Goldstein [mailto:goldstein@markygoldstein.com]
> Sent: Saturday, October 13, 2001 9:01 AM
> To: jetspeed-dev@jakarta.apache.org
> Subject: Cant get in to work... Jetspeed 1.3a
> 
> 
> I have Tomcat 4 running on Win2000.
> 
> But Jetspeed does not work, even worse: it 
> stops the Tomcat aswell...
> 
> Please dont release Alpha Versions, or please
> better declare your versioning...
> 
> Thanks, regards,
> Marky Goldstein
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

Re: version number

[ra...@networks.groupvu.com]

David Sean Taylor wrote:
> We are now gathering all the known bugs and missing features for this
> release.
> If we can fix all of these bugs and implement the essential features, the
> quality, in my opinion, will be good enough to drop the alpha.
> 

Quite apart from bug issues/stability, the "alpha" denominator is used because
the main APIs are still very in flux: if you consider the API differences between
1.3a1 and 1.3a2 and what is considered for 1.3a3 (new Portlet API), you'll see that
there are still some changes planned.

I'd like to go "beta" only when we are confident that our APIs are stable enough
so that we can ensure backward compatibility for modules and API extensions.
I don't think we've quite reached this point yet, which is why I'm +1 to keep
alpha for the time being.
--
Raphaël Luta - raphael.luta@networks.groupvu.com
Vivendi Universal Networks - Services Manager / Paris


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

Re: version number

[Santiago Gala <sg...@hisitech.com>]

Paul Spencer wrote:

>I agree with Jon, we should call the next release 1.3-b1.   Along those
>line, we should limit enhancement between the beta and the release of
>1.3 to those that will NOT break user developed portlets.  If this means
>releasing 1.3 sooner and postponing the implementation of the new
>Portlet API to 1.4, I would support that decision.
>
I am +1 on this one also.

We have a product that depends on jetspeed, and I would like to have a 
stable point to have simpler release cycle, so I'm not continuously 
moving code between undocumented, unreleased versions of turbine and 
jetspeed.

I think PortletAPI work missing is enough to give a thought to freezing 
API in 1.3, release, and then have a extended 1.4 release cycle with the 
new API.

>
>
>Paul Spencer
>
>Jon Stevens wrote:
>
>>on 10/13/01 2:13 PM, "David Sean Taylor" <da...@bluesunrise.com> wrote:
>>
>>>If we can fix all of these bugs and implement the essential features, the
>>>quality, in my opinion, will be good enough to drop the alpha.
>>>
>>If that happens, then the next release would be beta. :-)
>>
>>-jon
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>




---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

Re: version number

[Paul Spencer <pa...@mikon.com>]

I agree with Jon, we should call the next release 1.3-b1.   Along those
line, we should limit enhancement between the beta and the release of
1.3 to those that will NOT break user developed portlets.  If this means
releasing 1.3 sooner and postponing the implementation of the new
Portlet API to 1.4, I would support that decision.

Paul Spencer

Jon Stevens wrote:
> 
> on 10/13/01 2:13 PM, "David Sean Taylor" <da...@bluesunrise.com> wrote:
> 
> > If we can fix all of these bugs and implement the essential features, the
> > quality, in my opinion, will be good enough to drop the alpha.
> 
> If that happens, then the next release would be beta. :-)
> 
> -jon
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

Re: version number

[Jon Stevens <jo...@latchkey.com>]

on 10/13/01 2:13 PM, "David Sean Taylor" <da...@bluesunrise.com> wrote:

> If we can fix all of these bugs and implement the essential features, the
> quality, in my opinion, will be good enough to drop the alpha.

If that happens, then the next release would be beta. :-)

-jon


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

RE: version number

[David Sean Taylor <da...@bluesunrise.com>]

If its not an alpha release, yes, people will have higher expectations.
I believe that Jetspeed needs to move out of the 'alpha quality' state,
which it has been in for a long time now.

In order to make this happen, we all need to put in some work. Unfortunately
the current team, what is left of us, does not do portal development as part
of our daytime jobs (except Paul...).

We are now gathering all the known bugs and missing features for this
release.
If we can fix all of these bugs and implement the essential features, the
quality, in my opinion, will be good enough to drop the alpha.


> -----Original Message-----
> From: Jon Stevens [mailto:jon@latchkey.com]
> Sent: Saturday, October 13, 2001 1:42 PM
> To: jetspeed-dev
> Subject: Re: version number
>
>
> on 10/13/01 1:04 PM, "David Sean Taylor"
> <da...@bluesunrise.com> wrote:
>
> > Marky made a good point about versioning.
> > I don't like the a1 a2 naming, I think that people find it
> confusing.
> > Why don't we just call the next release 1.4?
>
> I don't think it is confusing. It shows that it is alpha
> quality software
> and that people shouldn't expect much from it...or should they?
>
> -jon
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

Re: version number

[Jon Stevens <jo...@latchkey.com>]

on 10/13/01 1:04 PM, "David Sean Taylor" <da...@bluesunrise.com> wrote:

> Marky made a good point about versioning.
> I don't like the a1 a2 naming, I think that people find it confusing.
> Why don't we just call the next release 1.4?

I don't think it is confusing. It shows that it is alpha quality software
and that people shouldn't expect much from it...or should they?

-jon


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org