Raphael,
we really appreciate the plan to come out with an 1.3a1
next week. It is important for us that an alpha release
with the current code base becomes available very soon.
I'm really glad to see how fast JetSpeed moved forward
in recent time :)
Jon's advice to call it a 1.3a1 is very good, indeed
there has been significant change since 1.2b1, so 1.2x
would not be appropriate, calling it 1.3a1 is honest.
We will make sure to commit our code on time.
Best regards,
Thomas
Thomas Schaeck
IBM Pervasive Computing Division
Phone: +49-(0)7031-16-3479 e-mail: [EMAIL PROTECTED]
Address: IBM Deutschland Entwicklung GmbH,
Schoenaicher Str. 220, 71032 Boeblingen, Germany
Raphael Luta wrote:
> Now that the project has mostly caught up with Turbine development
> and that we have a simple packaging system in form of WAR, I propose
> that we release very soon a new "alpha" release to give new users
> simpler access to Jetspeed.
>
> Due to the huge amount of reimplementation that have occured within
> last month, I suggest that we follow Jon advice and use the 1.3a1
> for this release denoting both the break from the 1.2b1 codebase and
> the "alpha" nature of the product where some major APIs are going to
> change in the near future.
>
> What I'd like in this release that is not yet in the CVS is:
> - the customizer
> - the WAP support code
>
> As soon as these 2 components are committed, I propose that we create
> a release branch for ironing all the possible bugs and clean-up the
> documentation for the release.
> The HEAD would stay open for new features to be incorporated, most
notably
> the profiler implementation of David.
>
> If everything goes well and the missing code is committed today or
> tomorrow, we should be able to release the new 1.3a1 sometimes next
> week.
>
> In summary, let me know :
> - if you agree that we should release a new alpha release ASAP.
> - if there are some features that you deem necessary for an alpha release
> that are not yet there
> - if you have some ideas on how to improve the base document set included
> in the webapp.
>
> One of my ideas on the last topic:
> Create an Apache OCS feed and make it available under the Jetspeed
website,
> configure the default Jetspeed distribution to use this feed, let all the
> current Apache projects define their own RSS channel registered within
the
> feed, so that Jetspeed can act as global multi-device "What's new" for
> the ASF.
>
> I'm open to any other ideas for illustrating Jetspeed.
>
> --
> Rapha�l Luta - [EMAIL PROTECTED]
> Vivendi Universal Networks - Services Manager / Paris
>
>
> --
> --------------------------------------------------------------
> Please read the FAQ! <http://java.apache.org/faq/>
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
> Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://marc.theaimsgroup.com/?l=jetspeed>
Problems?: [EMAIL PROTECTED]
