Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [riena-dev] Change of Plans in Riena...

+1
think its a very realistic plan

after reading all from Elias about current state of Riena + RAP -esp. in usecase of an Enterprise Application,
it makes sense to go the 3.0 way

we'll follow this path to RAP and e4 from redView ;-)

ekke

Am 10.08.10 22:19, schrieb Elias Volanakis:
+1

I think Riena on RAP and Riena on e4 good goals to pursue.

Elias.

On Tue, Aug 10, 2010 at 4:24 AM, Christian Campo
<christian.campo@xxxxxxxxxxxx> wrote:
  
Hi Rienaers, (Riena committers, contributors, users, interested parties)

"dont surprise your community" is one of the key points when dealing with
others in an open source environment. So I have explain a little for a
change in our plans and I hope I dont surprise anyone here.

When we create Riena 2.0 for the Helios release we published that our next
release would be 2.1. in december this year. That pretty much followed what
we did the year before where we have a minor release after 6 month.

Now several month in the time "after Helios", when we looked for ways to go
we had some interesting discussions among us committers (mostly face 2 face
or telco's).

We'd like to make a major step in making Riena work really way better under
RAP. A second goal is to investigate and prototyp making Riena run on e4,
not only on the compatibility layer but also using the new workbench model
and all the other new stuff that is part of it.

However we cannot do all at the same time.

In any event, having a midterm release in december seems to stop us from
making a big step forward. So we decided that our next release is Riena 3.0
which will come with Indigo in June 2011. We will publish milestones along
the line with Indigo (Eclipse 3.7).

A new major version is not only necessary because it is a big step forward
but it also need some flexibilty (nice wording :-) ) for breaking API. We
will do that we the same kind of documentation and caution that we used for
Riena 2.0. But certain things will need to change.

Our main focus will be to improve the RAP support. And that will also mean
that we have to make a number of changes in our code. Elias was kind enough
to start a wiki page http://wiki.eclipse.org/Riena_on_RAP with some issues
that we need to address.

The second task (with less prio) is to investigate what it means to also run
on the native new API of e4 and build prototypes for that. We have already
started and will keep on going there and start to create bundles for that.

Any feedback, comments, contribution, help or anything is welcomed at this
point in time.

If you have an opinion about the direction we are taking let us know......

christian

-------------------------------------------------------------
compeople AG
Untermainanlage 8
60329 Frankfurt/Main
fon: +49 (0) 69 / 27 22 18 0
fax: +49 (0) 69 / 27 22 18 22
web: http://www.compeople.de/

Vorstand: Jürgen Wiesmaier
Aufsichtsratsvorsitzender: Christian Glanz

Sitz der Gesellschaft: Frankfurt/Main
Handelsregister Frankfurt HRB 56759
Ust-Ident.-Nr: DE207665352
-------------------------------------------------------------
_______________________________________________
riena-dev mailing list
riena-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/riena-dev

    


  


--

ekke (ekkehard gentz)
independent software-architect
senior erp-consultant
eclipse | osgi | equinox | mdsd | oaw | emf | uml | blackberry
max-josefs-platz 30, D-83022 rosenheim, germany
mailto:ekke@xxxxxxxxxxxxxxxx
homepage (de): http://gentz-software.de
blog (en): http://ekkes-corner.org
project lead: http://redview.org and http://red-open.org
eclipse committer: Runtime Project Riena - http://eclipse.org/riena
twitter: @ekkescorner
skype: ekkes-corner
Steuer-Nr: 156/220/30931 FA Rosenheim, UST-ID: DE189929490


Back to the top