You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tiles.apache.org by Nicolas LE BAS <ma...@nlebas.net> on 2012/05/24 17:51:56 UTC

Project status and furure

Hi,

A quick sum up of the current situation:

* Releases
   The branch 2.2.x is dead unless we find people interested in testing it.
   We're releasing a first version of tiles-3 branch with the new 
tiles-request and tiles-autotag. We have the 3 bindings votes to release 
it and will probably have a consensus on Beta Quality. I'll try and 
complete the release process this week or next.
   The git mirror is still stale; you may use my own mirror at github if 
you wish, just make sure to base your work on the svn-tracking branches 
(not on my experiments).

* The road to GA
   From now on I feel we will use JIRA more extensively. There were a 
number of wide-scoped issues in 3.0.0; one or the other could describe 
almost anything we were doing and there were too many changes to track 
individually anyway, especially when removing unreleased stuff.
   I've created JIRAs on the issues we've identified since the release 
was tagged; please feel free to create more.

* Long term roadmap
   Perhaps it's time to start discussing the future.
   3.0 introduces tools to make tiles more maintainable across 
templating technologies, including a stable (hopefully) API for 
rendering requests and automatic tag generation. Otherwise, it's 
basically the same as 2.2.
   One objective I have for 3.1 is to complete independence from 
servlets. On a longer term, I'd like to try and introduce some cache 
management features to support some extra use cases and optimizations. 
Indeed I'm starting to think of tiles as an IoC framework for 
template-oriented programming.
   What are your plans for Tiles?

* Promotion
   It has been a long time without announce on the users ML; perhaps the 
beta release will draw the attention of new users and/or developers.
   We have an open issue with Spring for interfacing with tiles-3. 
Perhaps it's time to update it, a good way to get the attention of the 
spring community. Do we have a similar relationship with other projects? 
Struts perhaps?
   And finally I'm thinking of way to demonstrate and promote best 
practices with Tiles. We had the showcase but it is difficult to keep it 
up to date; perhaps a blog would make it easier for us, and at the same 
time more accessible to inexperienced users.

Nick.


Re: Project status and furure

Posted by Greg Reddin <gr...@gmail.com>.
On Fri, May 25, 2012 at 6:35 AM, Mick Semb Wever <mc...@apache.org> wrote:
>> Mck, would you be willing to change your vote to Beta so we'd have
>> full consensus? Or do you feel strongly that these should be GA?
>
> Absolutely. I was unsure how things worked here, my guess was that
> consensus fell upon the lowest denominator, therefore Beta was with 3
> votes already. But if i need to explicitly drop my vote down to Beta
> then i'm doing that with these words.

No need. You said it here on the list so that's good enough for me.

Greg

Re: Project status and furure

Posted by Mick Semb Wever <mc...@apache.org>.
> > We have the 3 bindings votes to release it
> > and will probably have a consensus on Beta Quality. I'll try and complete
> > the release process this week or next.
> 
> Mck, would you be willing to change your vote to Beta so we'd have
> full consensus? Or do you feel strongly that these should be GA? 

Absolutely. I was unsure how things worked here, my guess was that
consensus fell upon the lowest denominator, therefore Beta was with 3
votes already. But if i need to explicitly drop my vote down to Beta
then i'm doing that with these words.


> Indeed I'm starting to
>  think of tiles as an IoC framework for template-oriented programming.
>   What are your plans for Tiles?

This has a vision statement for the road forward has my full support!


> * Releases
>    The branch 2.2.x is dead unless we find people interested in
> testing it.

Agreed. The two of us need to be overly pragmatic here. Applying
provided fixes is probably about it.

> 
> * Promotion
>    It has been a long time without announce on the users ML; perhaps the 
> beta release will draw the attention of new users and/or developers.
>    We have an open issue with Spring for interfacing with tiles-3. 
> Perhaps it's time to update it, a good way to get the attention of the 
> spring community. 

Yeah, i'll take charge of updating that issue with your spring code
(which is far more elegant).

>    And finally I'm thinking of way to demonstrate and promote best 
> practices with Tiles. We had the showcase but it is difficult to keep it 
> up to date; perhaps a blog would make it easier for us, and at the same 
> time more accessible to inexperienced users.

The ultimate view article is being rewritten for Tiles-3 and is
currently in draft. That's one, more would be nice too...
Maybe a separate one on the new spring integration is another low
hanging fruit.

Otherwise Nick i'll focus on the code quality issue you opened
(checkstyle+test-coverage).

~mck

-- 
"We all may have come on different ships, but we’re in the same boat
now." Martin Luther King. Jr. 

| http://github.com/finn-no | http://tech.finn.no |

Re: Project status and furure

Posted by Greg Reddin <gr...@gmail.com>.
This is really good stuff. Thanks for taking the initiative to get it going...


On Thu, May 24, 2012 at 10:51 AM, Nicolas LE BAS <ma...@nlebas.net> wrote:
> We have the 3 bindings votes to release it
> and will probably have a consensus on Beta Quality. I'll try and complete
> the release process this week or next.

Mck, would you be willing to change your vote to Beta so we'd have
full consensus? Or do you feel strongly that these should be GA?

>  3.0 introduces tools to make tiles more maintainable across templating
> technologies, including a stable (hopefully) API for rendering requests and
> automatic tag generation. Otherwise, it's basically the same as 2.2.
>  One objective I have for 3.1 is to complete independence from servlets. On
> a longer term, I'd like to try and introduce some cache management features
> to support some extra use cases and optimizations. Indeed I'm starting to
> think of tiles as an IoC framework for template-oriented programming.
>  What are your plans for Tiles?

These are very good ideas. I like the direction I see of moving Tiles
from yet another web application templating framework to essentially
an offline or online templating system.

As I've said before my long-term goal is to help mentor the
regeneration of the team and move into a more backseat role. On that
note I think our biggest hurdle at this point is to recruit some new
developers. The ideas you point out below are good starting points
because they draw from the user base we've had in the past.

Greg

>
> * Promotion
>  It has been a long time without announce on the users ML; perhaps the beta
> release will draw the attention of new users and/or developers.
>  We have an open issue with Spring for interfacing with tiles-3. Perhaps
> it's time to update it, a good way to get the attention of the spring
> community. Do we have a similar relationship with other projects? Struts
> perhaps?
>  And finally I'm thinking of way to demonstrate and promote best practices
> with Tiles. We had the showcase but it is difficult to keep it up to date;
> perhaps a blog would make it easier for us, and at the same time more
> accessible to inexperienced users.
>
> Nick.
>

Re: Project status and furure

Posted by Greg Reddin <gr...@gmail.com>.
Looks like a good plan. Thanks for all your work!

Greg

On Wed, Jul 4, 2012 at 3:24 PM, Nicolas LE BAS <ma...@nlebas.net> wrote:
> Hi,
>
> A quick sum up of the current situation:
>
> * Beta testing
>   A few issues have been found since the release of Tiles 3.0.0 and
> associated projects. Most significant are:
>
>   AUTOTAG-15  Add an assembly project to deploy autotag artifacts and
> sources
>   AUTOTAG-16  Break the reactor-level dependency of Autotag on
> tiles-request-api
>   TILES-553  SimpleTilesListener not working in Tiles 3.0
>
>   All of them are now fixed, I think it is time to release again. I'd like
> to release Autotag 1.1.0 (AUTOTAG-16 breaks compatibility at compile-level
> by introducing generics), Request 1.0.1 (migration to Autotag 1.1.0) and
> Tiles 3.0.1.
>
> * Next 3.x version
>   The git mirror is working again, and Mck and I are slowly improving Tiles
> and Request with new features (or the same features with a broader scope).
> Those works are filed in JIRA, the release date is unpredictable as yet.
>
> * Next 2.x version
>   Still nobody interested in testing 2.2.x, so we can't release the bugs
> we've fixed.
>
>   If you agree, I'll post on the users list to ask for testers to join the
> dev team, failing that we won't release any more 2.2.x version, effectively
> dropping support.
>
> Nick.

Re: Project status and furure

Posted by Nicolas LE BAS <ma...@nlebas.net>.
Hi,

A quick sum up of the current situation:

* Beta testing
   A few issues have been found since the release of Tiles 3.0.0 and 
associated projects. Most significant are:

   AUTOTAG-15  Add an assembly project to deploy autotag artifacts and 
sources
   AUTOTAG-16  Break the reactor-level dependency of Autotag on 
tiles-request-api
   TILES-553  SimpleTilesListener not working in Tiles 3.0

   All of them are now fixed, I think it is time to release again. I'd 
like to release Autotag 1.1.0 (AUTOTAG-16 breaks compatibility at 
compile-level by introducing generics), Request 1.0.1 (migration to 
Autotag 1.1.0) and Tiles 3.0.1.

* Next 3.x version
   The git mirror is working again, and Mck and I are slowly improving 
Tiles and Request with new features (or the same features with a broader 
scope). Those works are filed in JIRA, the release date is unpredictable 
as yet.

* Next 2.x version
   Still nobody interested in testing 2.2.x, so we can't release the 
bugs we've fixed.

   If you agree, I'll post on the users list to ask for testers to join 
the dev team, failing that we won't release any more 2.2.x version, 
effectively dropping support.

Nick.