Hi,

I am planing to look at that soon:
https://issues.apache.org/struts/browse/SHALE-484

Since that may cause an API change, it might be "clever" to release
1.1.0 before ?

Did we now finally agree on "complete" vs "module" release ?

-Matthias

On Feb 7, 2008 5:42 PM, Gary VanMatre <[EMAIL PROTECTED]> wrote:
> >From: "Niall Pemberton" <[EMAIL PROTECTED]>
> >
> > On Feb 6, 2008 7:21 PM, linux.eavilesa wrote:
> > > Hi all,
> > >
> > > I've been tracking user and development mailing lists during some time,
> > > and I think that people is getting (including me) a little bit nervous
> > > about Shale project.
> >
> > and rightly so - the trends are stark:
> >
> > Overall: http://shale.markmail.org/search/?q=
> > Dev: http://tinyurl.com/2d3e92
> > Commits: http://tinyurl.com/2synvm
> >
> > Unless those trends start to reverse, the only glimmer of hope on the
> > horizon is/was the proposal to move the code to MyFaces.
> >
>
>
> Niall, I know you are a *very* active struts and commons committer and apache 
> supporter so I will take this to heart.
>
>
> > Niall
> >
>
>
> Gary
>
>
>
> > > I think that the main reason why is the fact that there is not a well
> > > defined road map now for the project and many of as have bitten to use
> > > Shale in front of other frameworks.
> > >
> > > First of all decide if Shale has a future (that I think that it does)
> > > and redefine or reinforce the project goal.
> > >
> > > So in my opinion we should focus on defining or determining three key
> > > concepts:
> > > · Define the project team organization, mainly the project leader and
> > > the development team.
> > > · Determine the release of the stable version (date and who will lead it)
> > > · Analyze each module and decide which must eliminated and which is
> > > worth keeping alive
> > >
> > > You will say....
> > >
> > > Thanks for your time.
> > >
> > > Esteve
> > >
> > >



-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org

Reply via email to