Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Received-SPF: pass (nike.apache.org: local policy)
MIME-version: 1.0
Date: Tue, 28 Apr 2009 15:20:14 -0700
From: Craig L Russell <Craig.Russell@Sun.COM>
Subject: Re: Proposed maintenance branch policy
In-reply-to: <49F778F1.5060508@apache.org>
Sender: Craig.Russell@Sun.COM
To: dev@openjpa.apache.org
Message-id: <6A991287-BBDD-42D0-9FAE-3BE967B0DF66@SUN.com>
Content-type: multipart/signed; protocol="application/pkcs7-signature";
 micalg=sha1; boundary=Apple-Mail-243-657009994
References: <44A67F59-138C-4C75-8393-5853E20649E1@SUN.com>
 <49F76A84.7020705@apache.org> <A14D162E-C1DE-4BFF-BA2C-CE08721D7FC8@SUN.com>
 <49F778F1.5060508@apache.org>

--Apple-Mail-243-657009994
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Hi David,

You can edit the issue and mark it as fix for 2.0.0 and 1.3 (which it  
already is) and mark it as affects versions 2.0.0 and 1.3 (which it  
isn't yet).

There's no succinct way to indicate tell the patch has been applied to  
the trunk except by reading the svn log that's part of the issue and  
reading your comments.

1.3 is an open release (no release manager watching it) so feel free  
to apply the patch to 1.3.x also.

I agree with you that the process isn't perfect with regard to  
applying this fix to other branches. I don't know what more guidance  
we should offer committers with a patch like this.

Craig

On Apr 28, 2009, at 2:45 PM, David Ezzio wrote:

> Hi Craig,
>
> In some cases the process starts differently.  A fix is needed for  
> branch 1.1, and to be polite (and conforming) it is also applied to  
> trunk.  So then, what's the process for the 1.2 and 1.3 branches in  
> this case?  It seems unfair that the person fixing 1.1 and trunk  
> should also fix (really nag and fix) every other branch, and it  
> seems inefficient that the branch managers be left to fend for  
> themselves in determining which fixes applied to trunk might be of  
> interest to them.  And when is the JIRA issue closed?
>
> Hmm.  I missed how to indicate in the JIRA that a problem is fixed  
> in a particular branch but still pending as a problem for other  
> branches. Could you take a look at 1002, and tell me how to indicate  
> that the problem is fixed for 2.0, but remains unfixed for 1.3?
>
> Cheers,
>
> David
>
>
> Craig L Russell wrote:
>> Hi David,
>> On Apr 28, 2009, at 1:43 PM, David Ezzio wrote:
>>> Hi Craig,
>>>
>>> I'm not sure I understand the following:
>>>
>>> "Fixes which are committed to an earlier release should also be  
>>> present 'up-stream'. Ie a fix for 1.0.x should also appear in  
>>> 1.2.x."
>>>
>>> I'm unclear about who should make it appear in the upstream  
>>> releases. In other words, I apply a fix today to trunk and to  
>>> 1.1.x (with approval).  Who applies the fix to 1.2.x and 1.3.x?
>> I'd say you start with trunk and work backwards, recommending that  
>> the fix be applied to 1.3.x and if you get any pushback, then stop.  
>> If it's ok for 1.3.x, then try 1.2.x. Rinse and repeat.
>>> And how do we track  all the branches where a fix has been,  
>>> should, or should not be applied.
>>>
>>> Ideally, the JIRA would do this work for us, but maybe there's a  
>>> simpler way.
>> I think JIRA actually does support the issue being fixed in  
>> multiple releases. I don't know of a simpler way than marking the  
>> JIRA with multiple releases.
>> Craig
>>>
>>>
>>> Thanks,
>>>
>>> David
>>>
>>> Craig L Russell wrote:
>>>> Hi,
>>>> I think it would be a good idea to formalize OpenJPA's policy  
>>>> with regard to maintenance branch responsibilities.
>>>> The draft is published at http://cwiki.apache.org/confluence/display/openjpa/OpenJPA+Release+Management 
>>>>  for review/comment.
>>>> Feel free to comment by either posting on the wiki or discussing  
>>>> on this email thread. Once we have consensus, the wiki will be  
>>>> considered policy.
>>>> Thanks,
>>>> Craig
>>>> Craig L Russell
>>>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>>>> 408 276-5638 mailto:Craig.Russell@sun.com
>>>> P.S. A good JDO? O, Gasp!
>> Craig L Russell
>> Architect, Sun Java Enterprise System http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@sun.com
>> P.S. A good JDO? O, Gasp!

Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!


--Apple-Mail-243-657009994
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGUDCCAwkw
ggJyoAMCAQICEDXZ+Ig/3d9DjJZ8u++ZnC0wDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx
JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ
ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA4MTIwOTE4MTYwMloXDTA5MTIwOTE4MTYw
MlowbDEQMA4GA1UEBBMHUnVzc2VsbDEUMBIGA1UEKhMLQ3JhaWcgTGFpcmQxHDAaBgNVBAMTE0Ny
YWlnIExhaXJkIFJ1c3NlbGwxJDAiBgkqhkiG9w0BCQEWFUNyYWlnLlJ1c3NlbGxAU3VuLkNPTTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAOe3oksetTgSiqqWllhIYBT0dWhR4CitzXDf
+ETyrtEF2HWRRpfwixLpV1Az8wwFzNKfjvQn3tQh0A/VDDeepDEM9TKLP+D6qShLR/KTf5kCMyT4
mILJYIDo/JMmTIH5jceojvlTDFd0gd+XXNAGGz1Wu2XxfvFDE/lpFnQkKYE+VjjENONy4JlkJnOI
rSfMlb+zHPAUmMTtmhxYIDLgov4Jv2Z5pUKZMpNcYr+7jJeUxkxKwWm4im56h7CGP0Yhkq2Je506
mqKCFImxofBjkHZISVS5m7WaGs4lViDtwLQEPtyUt7RcaoYWTvEQtvoy1TE2oZDUaAYFxVu0cHUW
bU0CAwEAAaMyMDAwIAYDVR0RBBkwF4EVQ3JhaWcuUnVzc2VsbEBTdW4uQ09NMAwGA1UdEwEB/wQC
MAAwDQYJKoZIhvcNAQEFBQADgYEAQaqAADs5GLyk9iO1xfmNFySpOXXofJPEbfbt77BK/WLhLOwS
69WIxSmGMpGGUlLd6FJ1xfLzsvP9/N5tmZQlpGcBoEwrn830JcbNyEG0ANcmdeAy2yBjNjWoIDhV
QmQw8OgJDk0xi0Tv/UYm9uPxOhDJOA67a3v6FHvSAbLqBScwggM/MIICqKADAgECAgENMA0GCSqG
SIb3DQEBBQUAMIHRMQswCQYDVQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQH
EwlDYXBlIFRvd24xGjAYBgNVBAoTEVRoYXd0ZSBDb25zdWx0aW5nMSgwJgYDVQQLEx9DZXJ0aWZp
Y2F0aW9uIFNlcnZpY2VzIERpdmlzaW9uMSQwIgYDVQQDExtUaGF3dGUgUGVyc29uYWwgRnJlZW1h
aWwgQ0ExKzApBgkqhkiG9w0BCQEWHHBlcnNvbmFsLWZyZWVtYWlsQHRoYXd0ZS5jb20wHhcNMDMw
NzE3MDAwMDAwWhcNMTMwNzE2MjM1OTU5WjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3Rl
IENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWls
IElzc3VpbmcgQ0EwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAMSmPFVzVftOucqZWh5owHUE
cJ3f6f+jHuy9zfVb8hp2vX8MOmHyv1HOAdTlUAow1wJjWiyJFXCO3cnwK4Vaqj9xVsuvPAsH5/Ef
kTYkKhPPK9Xzgnc9A74r/rsYPge/QIACZNenprufZdHFKlSFD0gEf6e20TxhBEAeZBlyYLf7AgMB
AAGjgZQwgZEwEgYDVR0TAQH/BAgwBgEB/wIBADBDBgNVHR8EPDA6MDigNqA0hjJodHRwOi8vY3Js
LnRoYXd0ZS5jb20vVGhhd3RlUGVyc29uYWxGcmVlbWFpbENBLmNybDALBgNVHQ8EBAMCAQYwKQYD
VR0RBCIwIKQeMBwxGjAYBgNVBAMTEVByaXZhdGVMYWJlbDItMTM4MA0GCSqGSIb3DQEBBQUAA4GB
AEiM0VCD6gsuzA2jZqxnD3+vrL7CF6FDlpSdf0whuPg2H6otnzYvwPQcUCCTcDz9reFhYsPZOhl+
hLGZGwDFGguCdJ4lUJRix9sncVcljd2pnDmOjCBPZV+V2vf3h9bGCE6u9uo05RAaWzVNd+NWIXiC
3CEZNd4ksdMdRv9dX2VPMYIDEDCCAwwCAQEwdjBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0ECEDXZ+Ig/3d9DjJZ8u++ZnC0wCQYFKw4DAhoFAKCCAW8wGAYJKoZIhvcN
AQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMDkwNDI4MjIyMDE1WjAjBgkqhkiG9w0B
CQQxFgQUOcQJES+cWLVPftFfnRbUp9s/jkQwgYUGCSsGAQQBgjcQBDF4MHYwYjELMAkGA1UEBhMC
WkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0
ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhA12fiIP93fQ4yWfLvvmZwtMIGHBgsqhkiG
9w0BCRACCzF4oHYwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQ
dHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhA1
2fiIP93fQ4yWfLvvmZwtMA0GCSqGSIb3DQEBAQUABIIBAI8tr4cTgl+O9cy0gErIJmOoaolcboqt
IG34d7AhmouqMJY8hxOweXAVXaf8IhXgL+DdkOQzJBfVFpJ2lYues21PruBkO4pl859jQMjCWDRn
sGRU/B2LRs6gP54haW8K9edX7ShJXwJP4hYAiAAXkE+J9KuETbHjcr7cC6r/uFlYJ5jhIQp0f1Zj
QJHy8X+2D9hWQ4a+MgbZm2EnsdUJWHVIJ3NzzrrRIbR13ignlP5SdreCBb/mRMmhJaznhtiSEXhf
tkemq6f4cgIwAV4Q/2vH3q3hi89AUQtxDYUUdEwTY00ra1ewqv9iEo9fNvt+0Fd3rZddKNpZh45t
jqtkd2YAAAAAAAA=

--Apple-Mail-243-657009994--