<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<br>
<div class="moz-cite-prefix">On 06/02/2015 12:00 AM, Johan Brichau
wrote:<br>
</div>
<blockquote
cite="mid:F38DF64F-61D1-4C27-BC71-7A446AA95243@inceptive.be"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Hey Dale,
<div class=""><br class="">
</div>
<div class="">Creating a fork will be the way to go. I think it’s
clearer to follow the same pattern everywhere.</div>
<div class="">I intend this to be applicable for Seaside 3.2 and
beyond.</div>
</blockquote>
Makes sense ...<br>
<blockquote
cite="mid:F38DF64F-61D1-4C27-BC71-7A446AA95243@inceptive.be"
type="cite">
<div class=""><br class="">
</div>
<div class="">My intention is to get Seaside 3.2 for Gemstone
working by ESUG. For that, I will start from the Seaside31 repo
on GsDevKit and merge in the changes from Seaside3.2</div>
</blockquote>
Let me know if there's anything you need help with .. I'd like to
help where I can, but I don't want to get in your way ... at a
minimum, I will make sure that this works in GemStone3.3 when it's
ready enough for that ...<br>
<blockquote
cite="mid:F38DF64F-61D1-4C27-BC71-7A446AA95243@inceptive.be"
type="cite">
<div class=""><br class="">
</div>
<div class="">I’m more puzzled on how to approach Grease. The <a
moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://github.com/SeasideSt/G">https://github.com/SeasideSt/G</a>rease
repo works for all platforms and ideally the GsDevKit repo is a
fork of this one, but that will disturb a lot of Metacello
loads… so I think I will not touch that one for now.</div>
</blockquote>
<br>
Are there differences between the two in terms of
packaging/structure? Or is mainly the comit stream that you are
thinking of?<br>
<br>
Dale<br>
<br>
</body>
</html>