<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">As I said we have a snapshot of the
latest version of the code (see [1]), however this doesn't include
the commit history. If the history is important for whatever
reason, I suggest we reinstate it under its own branch of the
picketlink-idm repository. I thought we were both of the
understanding though from our discussions that this code was just
a stop-gap measure so that we had something to show in time for
JavaOne.<br>
<br>
[1]
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="https://github.com/picketlink/picketlink/tree/953c39f6ccb9c4617357deb47210ad15151c2b08/idm-impl/src/main/java/org/picketlink/idm/internal">https://github.com/picketlink/picketlink/tree/953c39f6ccb9c4617357deb47210ad15151c2b08/idm-impl/src/main/java/org/picketlink/idm/internal</a><br>
<br>
<br>
<br>
On 04/10/12 11:05, Anil Saldhana wrote:<br>
</div>
<blockquote cite="mid:506CE0C9.6060808@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Shane,<br>
did you throw away the JPA code that Pedro had done for almost
a month? Where is that code? <br>
<br>
Code contributions have legal ramifications. We cannot just
throw away code and loss of history is deeply disturbing.<br>
<br>
Regards,<br>
Anil<br>
<br>
On 10/03/2012 05:39 PM, Shane Bryzak wrote:<br>
</div>
<blockquote cite="mid:506CBEA0.9020909@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">There was a little bit of confusion
over the legacy IDM code (I had forgotten that it had been
migrated to the picketlink-idm repo on GitHub albeit under
different branches) but this has been sorted out now, and I
believe all the history for it is intact. As for the
temporary IDM implementation we have the final snapshot of it,
however since then I've blown it away anyhow and started
working on the proper implementation. I don't think we need
the history for the temporary stuff. <br>
<br>
Agreed with the collective PL release. As for the version
number, did we ever do a 2.x release? If so, then I agree we
should update it to 3.x for the new project.<br>
<br>
Shane<br>
<br>
On 04/10/12 01:06, Anil Saldhana wrote:<br>
</div>
<blockquote cite="mid:506C5465.3000506@redhat.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix">Shane,<br>
ahh. You could not wait a day or two. :) I am wondering
if we could have retained history via some form of "git mv".<br>
<br>
We should probably have PicketLink version as 3.0 for all
the code and rather than do individual releases, we can do a
collective PL3.x release.<br>
<br>
Cheers.<br>
<br>
On 10/02/2012 04:56 AM, Boleslaw Dawidowicz wrote:<br>
</div>
<blockquote
cite="mid:04BB470F-ADB3-49CC-A924-92E5E73791F1@redhat.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
I restored our branches and synced with Shane on IM.
<div><br>
</div>
<div>picketlink-idm/master will be nuked and only contain
some README pointing to new locations</div>
<div><br>
</div>
<div>Current picketlink-idm repo will be kept for few more
months at least and after we are in more calm situation
with GateIn/EPP it will be renamed into
picketlink-idm-legacy. </div>
<div><br>
</div>
<div>Things under control :)</div>
<div><br>
</div>
<div>Bolek</div>
<div><br>
<div>
<div>On Oct 2, 2012, at 11:08 AM, Boleslaw Dawidowicz
<<a moz-do-not-send="true"
href="mailto:bdawidow@redhat.com">bdawidow@redhat.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space; ">
<div>I must say I'm quite pissed off… even yesterday
I shared a link to one of configuration files in
1.4 branch with a consultants. We released twice
last month… how could have it happened without any
question?</div>
<div><br>
</div>
<br>
<div>
<div>On Oct 2, 2012, at 11:06 AM, Boleslaw
Dawidowicz <<a moz-do-not-send="true"
href="mailto:bdawidow@redhat.com">bdawidow@redhat.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta http-equiv="Content-Type"
content="text/html; charset=ISO-8859-1">
<div style="word-wrap: break-word;
-webkit-nbsp-mode: space; -webkit-line-break:
after-white-space; ">Have you just removed
picketlink-idm on github?
<div><br>
</div>
<div>We are actively working on 1.4 branch and
this is critical for EPP. Other branches are
still maintenance for older versions of
GateIn/EPP. I think I was fairly clear that
we need those. </div>
<div><br>
</div>
<div>This repo needs to be restored ASAP. </div>
<div><br>
<div>
<div>On Oct 2, 2012, at 12:30 AM, Shane
Bryzak <<a moz-do-not-send="true"
href="mailto:sbryzak@redhat.com">sbryzak@redhat.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<meta http-equiv="content-type"
content="text/html;
charset=ISO-8859-1">
<div bgcolor="#FFFFFF" text="#000000">
In the interests of presenting a clear
message to our developers, one of the
steps we'll be taking is to
consolidate the various PicketLink
projects into a single project and
presenting this as the "go to"
solution for application security.
For now I've merged the CDI and IDM
subprojects (these are now submodules
of the PicketLink project, with "CDI"
renamed to "Core") and the plan is to
eventually merge the social and
federation modules also.<br>
<br>
You can find the new GitHub repository
here:
<meta http-equiv="content-type"
content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true"
href="https://github.com/picketlink">https://github.com/picketlink</a>
(renamed from picketlink-cdi) and the
picketlink-idm repository has now been
deleted. For anyone working on these
modules, please use the new repository
from now on.<br>
<br>
Thanks!<br>
Shane</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
security-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:security-dev@lists.jboss.org">security-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/security-dev">https://lists.jboss.org/mailman/listinfo/security-dev</a>
</pre>
</blockquote>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
security-dev mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:security-dev@lists.jboss.org">security-dev@lists.jboss.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/security-dev">https://lists.jboss.org/mailman/listinfo/security-dev</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
security-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:security-dev@lists.jboss.org">security-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/security-dev">https://lists.jboss.org/mailman/listinfo/security-dev</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>