<div dir="ltr">Hi Everyone,<br><br>Thanks for the replies. Chris I read the wiki link you posted and from this it would seem that editing the release would be the way to go, as there are no bugs that I can find, or the need to update any of the packages being loaded. Frank, you have suggested I create a new package, however. Can I ask why you suggest a new release? I am open to going with either approach if we decide to make this a community supported package, but I don't have enough information yet to understand why I would choose one approach or the other.<br>
<br>Thanks again,<br>Jeff<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jan 4, 2013 at 9:15 AM, Chris Muller <span dir="ltr"><<a href="mailto:asqueaker@gmail.com" target="_blank">asqueaker@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">> So I have two questions:<br>
><br>
> 1) Can we make OCompletion into a Community Supported Package? I believe<br>
> that it provides considerable benefits when developing in Squeak<br>
<br>
</div>Its up to Levente. Levente would you prefer the SM catalog entry for<br>
OCompletion to be Community-Supported or do you prefer to maintain<br>
that yourself?<br>
<div class="im"><br>
> 2) Once it is community supported, do I just select "Edit Release" on the<br>
> 4.2 compatible release, change the compatibility level to Squeak 4.4, update<br>
> the name and enter my squeak map id/password? I want to get some experience<br>
> doing this, but I'd rather not learn by doing it wrong the first time and<br>
> ending up with some egg on my face.<br>
><br>
> Maybe a bit of a tutorial on how to go about editing a community supported<br>
> package would be helpful.<br>
<br>
</div><a href="http://wiki.squeak.org/squeak/6180" target="_blank">http://wiki.squeak.org/squeak/6180</a><br>
<br>
</blockquote></div><br></div>