5:05 p.m.
I've changed the subject to reflect the topic-fork :-)
Let me write out some thoughts on Roadmap, and the way I would like to structure it, and
then make a proposal about your comment.
* The goal of jdf is to show people how to use JBoss software, both the upstream stuff
(e.g. JBoss AS) and the supported products (e.g. JBoss Enterprise Application Platform).
* Many JBoss upstream project release dates are partly driven by product dates.
* We're not really that tied to EAP/AS, as our main dependence here is the Java EE API
(which pretty much affects everything anyway)
* We will introduce ties to other products down the line
* We're probably most tied to the JBoss Web Framework Kit release schedule, as that is
what includes Errai, RichFaces, Spring support for JBoss, and will likely include
DeltaSpike at some future point
* We will probably want to ship the big examples in jdf in WFK
For these reasons, I would like to align the jdf release cycle to WFK. I'm still
working with the product management team for WFK to tie down the exact schedule.
To me, it makes most sense to start the poll for roadmap feedback once we have the
schedule locked down, as it gives users a basic framework for deciding what their
priorities are. So, I would propose we hold off the poll for a week or so, just to get the
schedule in place.
Finally, we're still working through the backlog of topics right now, so for JDF.next,
we do have a roadmap.
Regarding publicising, usual channels I think - blogs, twitter etc.
On 2 Jul 2012, at 15:48, Jason Porter wrote:
At this point since it's been released and we have had a pretty
good showing of jdf now, should we open things up to the users we're targeting and get
them to help us flesh out our roadmap? This is all about them and finding the pain points
they have. I'm not exactly sure the best way to do that though besides putting out a
news section and ask for comments. Thoughts?
----- Original Message -----
> From: "Pete Muir" <pmuir(a)redhat.com>
> To: jdf-dev(a)lists.jboss.org
> Sent: Thursday, June 28, 2012 6:29:57 PM
> Subject: [jdf-dev] Migration: when and what
>
> One thing I picked up at Summit was that whilst people really
> appreciate the migration guides, they also want more advice on when
> (/whether) they should migrate, and what they should migrate too. We
> have the story pretty much sorted:
>
> * if you have an app that works, and you want to keep running it on
> Seam 2.2, then great. We'll support that for X more years on EAP.
> Stay where you are.
> * if you want to stay on Seam 2, but want to take advantage of the
> new features of Java EE 6, then you can take a look at Seam 2.3,
> which is currently beta quality. We haven't decided yet whether this
> will enter the supported product arena.
> * if you want to take advantage of Java EE, you need to do a bit of
> analysis of your app:
> ** if you have all the features you need in Java EE 6 (and look at
> TicketMonster, you can achieve a lot!) then migrate to Java EE 6
> ** if you don't, but you can find them in DeltaSpike, and like living
> on the edge, then you can take the path of adding DeltaSpike to Java
> EE 6. But we don't have a well trodden path here, with guides for
> you to follow
> ** otherwise, take a look at the jdf roadmap to see when the features
> you need will enter jdf, will all the goodness of the stack and
> guides
>
> Comments? I'll get this written up for
> http://www.jboss.org/jdf/migrations/get-started/ next week.
> _______________________________________________
> jdf-dev mailing list
> jdf-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jdf-dev
>