| Summary: | create official EDG 6 Alpha bundle | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Prabhat Jha <prabhat.jha> |
| Component: | unspecified | Assignee: | Default User <jbpapp-maint> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | unspecified | CC: | jdg-bugs, mlinhard, prabhat.jha, trustin |
| Target Milestone: | --- | ||
| Target Release: | 6.0.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/EDG-28 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-09-01 08:06:35 UTC | Type: | Feature Request |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Prabhat Jha
2011-06-20 14:41:19 UTC
What should the official bundle look like? Does it look different from the usual tar/zip distribution? Any pointers would be appreciated. I think for alpha, we are only talking about zip bundle. For Final PRD currently talks about RPM as well but that's not possible in alpha time frame IMO. What I thought by official build is basically a somehow stabler tag - the build process and format of the distribution is not any different. I'd like to see it based on tagged AS 7.0.0.CR1 that's about to be released a tagged version of infinispan, that means probably 5.0.0.CR6 also I'd like to establish a nomemclature for later tags let's say ALPHA1, ALPHA2 etc. so that we can report against a concrete version in JIRA (set proper affectsVersion, fixVersion) so that when we take ALPHAx and find serious blockers in it, new ALPHA(x+1) is released and every change and bug report is trackable. the customer will get one of the later ALPHA tags, that would be the result of our QA process wdyt ? So, what you mean is tag Alpha1 real soon and keep fixing the known issues and keep tagging, and then provide the latest alpha (e.g. alpha5) to the customer when it's ready? That's how I imagine it could work, of course this needs to be discussed, I've send an e-mail to infinispan-internal about this. We're simply releasing ALPHA as a zip file. Docs QE Status: Removed: NEW |