Bug 745894 (EDG-28) - create official EDG 6 Alpha bundle
Summary: create official EDG 6 Alpha bundle
Keywords:
Status: CLOSED NEXTRELEASE
Alias: EDG-28
Product: JBoss Data Grid 6
Classification: JBoss
Component: unspecified
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 6.0.0
Assignee: Default User
QA Contact:
URL: http://jira.jboss.org/jira/browse/EDG-28
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-20 14:41 UTC by Prabhat Jha
Modified: 2012-08-15 16:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-09-01 08:06:35 UTC
Type: Feature Request

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker EDG-28 0 Major Closed create official EDG 6 Alpha bundle 2017-09-07 08:34:54 UTC

Description Prabhat Jha 2011-06-20 14:41:19 UTC 
project_key: EDG
Comment 1 Trustin Lee 2011-06-20 16:03:15 UTC 
What should the official bundle look like?  Does it look different from the usual tar/zip distribution?  Any pointers would be appreciated.
Comment 2 Prabhat Jha 2011-06-20 16:13:16 UTC 
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.
Comment 3 Michal Linhard 2011-06-21 10:27:34 UTC 
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 ?
Comment 4 Trustin Lee 2011-06-21 10:36:32 UTC 
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?
Comment 5 Michal Linhard 2011-06-21 10:46:08 UTC 
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.
Comment 6 Galder Zamarreño 2011-09-01 08:06:34 UTC 
We're simply releasing ALPHA as a zip file.
Comment 7 Anne-Louise Tangring 2011-09-26 19:41:34 UTC 
Docs QE Status: Removed: NEW
Note You need to log in before you can comment on or make changes to this bug.