Re: [DISCUSS] next release version? 0.6 or 1.0?
I think 1.0 sounds great. Improving docs would be the best way to move deltaspike forward imo. My major concern right now is the windowId stuff. I like many want the functionality but struggles with dual ids (windowId dsRid) a loading splash. Would love docs here that covers the different strategies and routes one can take. cheers On 15 November 2013 14:31, Christian Kaltepoth christ...@kaltepoth.dewrote: +1 for releasing 1.0 next -1 for subreleases. This would be very confusing. +1 for improving the documentation before the 1.0 release. This is IMHO more important than examples. 2013/11/11 Romain Manni-Bucau rmannibu...@gmail.com Well if code is released it should be stable or explicitely in alpha/beta..maybe we should do subreleases for unstables modules Le 11 nov. 2013 18:43, Mark Struberg strub...@yahoo.de a écrit : Oki folks, txs 4 the feedback, all! I'd say we should create the module-maturity-matrix.md first and then we might do the version bump. Maybe something like green/blue/orange/red for mature / ready but still needs a few features / ready but might change it's api still / work in progress LieGrue, strub - Original Message - From: Charles Moulliard ch0...@gmail.com To: dev@deltaspike.apache.org Cc: Mark Struberg strub...@yahoo.de Sent: Monday, 11 November 2013, 18:25 Subject: Re: [DISCUSS] next release version? 0.6 or 1.0? +1 to move to 1.0. We have done the same thing with Apache Aries moving Blueprint from 0.5 to 1.0 release On Mon, Nov 11, 2013 at 6:17 PM, John D. Ament john.d.am...@gmail.comwrote: Yep, agreed. Users care about the version #. I would recommend that if we could release a 1.0 based on the current code base + some additional bug fixes we'll get huge wins. +1 to switching current to 1.0.0-SNAPSHOT. On Mon, Nov 11, 2013 at 12:08 PM, Mark Struberg strub...@yahoo.de wrote: Hi! In the last 2 months I did a few conference talks and smaller presentations (OpenBlend, W-JAX, ..) and always got the same questions: it's only a 0.x version, so is it already stable? I don't like to use it in production with 0.x And the actual answer is: well, core, cdictrl, etc are stable since a long time, other modules are not yet 100% where we like them. The other fact is that we will never get all our modules 100% stable. Because new modules cannot be released with the same quality than established and well known and bugfixed modules. Thus I think we should rather introduce a kind of majurity-matrix for DeltaSpike. A simple list of modules and their majurity grade. By officially moving to 1.0 we would gain much more users. I personally do not care about numbers, but LOTS of users do! Wdyt? LieGrue, strub -- Charles Moulliard Apache Committer / Architect @RedHat Twitter : @cmoulliard | Blog : http://cmoulliard.github.io -- Christian Kaltepoth Blog: http://blog.kaltepoth.de/ Twitter: http://twitter.com/chkal GitHub: https://github.com/chkal
[jira] [Commented] (DELTASPIKE-454) Provide a ClientWindowRenderMode similiar to CODI
[ https://issues.apache.org/jira/browse/DELTASPIKE-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13848418#comment-13848418 ] Oleg Varaksin commented on DELTASPIKE-454: -- Every full page request causes displaying a Loading... page. This is quite strange. We don't want to see this page. I also noticed, full page requests are very slow in comparison to CODI (have a big web app). Please, don't show this Loading... page. Even worst. DeltaSpike always shows Loading... when you download a binary content (e.g. PDF) too. That means, if the content-disposition for the content streaming is attachment (set in response header), the original page disappears! That's a bug. The original page should stay displayed. So, I switched to CODI for now again. Provide a ClientWindowRenderMode similiar to CODI - Key: DELTASPIKE-454 URL: https://issues.apache.org/jira/browse/DELTASPIKE-454 Project: DeltaSpike Issue Type: New Feature Components: JSF-Module Reporter: Thomas Andraschko Assignee: Mark Struberg Without LoadingScreen, JS, HTML and else. Its stable and works fine. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Created] (DELTASPIKE-467) Add default module.xml for jboss modules.
John D. Ament created DELTASPIKE-467: Summary: Add default module.xml for jboss modules. Key: DELTASPIKE-467 URL: https://issues.apache.org/jira/browse/DELTASPIKE-467 Project: DeltaSpike Issue Type: Improvement Affects Versions: 0.5 Reporter: John D. Ament Assignee: John D. Ament Fix For: 0.6 Add module.xml to the binary distribution, to make it easier to import to repackaged JBoss AS7+ distribution that includes DeltaSpike. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (DELTASPIKE-467) Add default module.xml for jboss modules.
[ https://issues.apache.org/jira/browse/DELTASPIKE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved DELTASPIKE-467. -- Resolution: Fixed Fixed Add default module.xml for jboss modules. - Key: DELTASPIKE-467 URL: https://issues.apache.org/jira/browse/DELTASPIKE-467 Project: DeltaSpike Issue Type: Improvement Affects Versions: 0.5 Reporter: John D. Ament Assignee: John D. Ament Fix For: 0.6 Add module.xml to the binary distribution, to make it easier to import to repackaged JBoss AS7+ distribution that includes DeltaSpike. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Resolved] (DELTASPIKE-263) Generate binaries of DeltaSpike project
[ https://issues.apache.org/jira/browse/DELTASPIKE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved DELTASPIKE-263. -- Resolution: Fixed Added a 'distribution' profile that when run will generate binaries in zip and tar.gz formats. Generate binaries of DeltaSpike project --- Key: DELTASPIKE-263 URL: https://issues.apache.org/jira/browse/DELTASPIKE-263 Project: DeltaSpike Issue Type: New Feature Affects Versions: 0.3-incubating Reporter: Charles Moulliard Assignee: John D. Ament Fix For: 0.6 -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Updated] (DELTASPIKE-193) Setup SecurityManager enabled CI build
[ https://issues.apache.org/jira/browse/DELTASPIKE-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated DELTASPIKE-193: - Summary: Setup SecurityManager enabled CI build (was: Setup SecurityManagager enabled CI build) Setup SecurityManager enabled CI build -- Key: DELTASPIKE-193 URL: https://issues.apache.org/jira/browse/DELTASPIKE-193 Project: DeltaSpike Issue Type: Task Components: Build Affects Versions: 0.2-incubating Reporter: Mark Struberg Assignee: Mark Struberg Fix For: 0.6 We currently don't have any CI environment which uses a SecurityManager. We should add such an environment to check whether DeltaSpike properly uses doPrivileged blocks where needed. -- This message was sent by Atlassian JIRA (v6.1.4#6159)
