Grzegorz,
I don't agree with non-stable releases and totally disagree with a
nonchalant care taken for any release however I suspect Remi's comments
might allude to the fact that the release deployment has been
streamlined vs. toss the release out there the Microsoft way... .
*Please re-read the initial post on this thread.*
Nested layouts was the main thing IMO that held back the 1.5.4 release.
I reported some issues w/ nested layouts as well as provided Ben with
simple reproducible tests.
Ben resolved those issues a month ago and said:
> I have lots of crazy test cases that work great. I just wanted people
to drop in a snapshot where they're running 1.5.3 and make sure
everything still works.
Others have made aside comments that nested layouts work for them.
If all project test cases have passed, non-working cases have been
resolved, and nobody is voicing any issues (on the mailing list OR via
JIRA) then my question is then what is the criteria to release 1.5.4
Snapshot?
Again - I disagree with Remi's comments and couldn't agree with you more
- however on your "Up" remark...
What is the issue you have with the 1.5.4 release going live?
Cheers,
--Nikolaos
Grzegorz Krug?y wrote:
W dniu 09.11.2010 20:51, VANKEISBELCK Remi pisze:
Let's go. It's been too long already. And if this layout thing
actually turns out to be a disaster, well, we'll fix and re-release.
This does sound more like Microsoft relasing Windows (hey, we have
autoupdate, we'll fix it later or we'll issue an SP). I believe changes
as deep as those with layout engine should be tested and confirmed
working if we still want Stripes to be treated seriously.
Having said that, I have been using 1.5.x branch on my e-commerce app
where layouts are intensively used for CMS-related stuff and I have
noticed no fuckups after Ben's changes. But there have not been too many
responses to Ben's call for testing and I'm not sure if releasing
without confirming (perhaps some synthetic suite of tests that check
edge cases?) it works for everyone is a good idea.
The release process (apart from the whole website/news etc) is really
straightforward with maven now, I don't see no showstopper.
If someone is happily using 1.5.3 and replaces it with 1.5.4 (so only
minor version increase) and it breaks horribly with strange templating
bugs, it IS a showstopper. Breaking things between minor releases is the
way PHP works, not serious Java frameworks.
If anyone thinks we should wait, please speak up !
Up! ;-)
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
------------------------------------------------------------------------------
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book "Blueprint to a
Billion" shares his insights and actions to help propel your
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
_______________________________________________
Stripes-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-users
