[cle-release-team] Hoe to release an indie

[Anthony Whyte]

You should also remove references to ye olde Sakai Maven 2 repo listings in <distributionManagement>.

Anth


On Apr 23, 2012, at 11:37 AM, Matthew Jones wrote:

> Yea, I'd think you have to comment on that ticket to see the org.sakaiproject issues. I can't see anyone elses staged projects. You can try though before if you wanted. All you have to do is change your parent to the sonatype one and see what happens. You can deploy it from the command line if you have the credentials and skip Jenkins entirely, but I'm just trying to simplify it so more people will use it and we can keep track better of the versions released.
> 
> On Mon, Apr 23, 2012 at 11:26 AM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
> I already have an account on Sonatype for pushing through releases in other projects, do I need to be added to the Sakai group?
> 
> Cheers,
> Steve
> 
> Sent from my iPad
> 
> On 23/04/2012, at 11:53 PM, Matthew Jones <matthew at longsight.com> wrote:
> 
>> Yea, presently jenkins has the credentials stored to deploy it to sonatype.
>> 
>> To actually release something tagged to maven central, you actually have to login to the interface, verify that all of the files are there and the poms are correct. Close the deployment and release the deployment. This is mentioned in the pre-release step under "obtaining credentials" on how to do this (have to create a jira entry and have it approved).
>> 
>> I wouldn't say this is a huge deal because already Sam, Chris and myself can do this, and it takes around 4-6 hours anyway for the artifacts to make it into maven central. But if you (or someone else) is actually going to be active in this process, you can obtain this account.
>> 
>> Jenkins deploys it as a special account we setup, but we still login and close/release as our personal accounts.
>> 
>> On Mon, Apr 23, 2012 at 2:14 AM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
>> Ok that all sounds fine, thanks for the info.
>> 
>> In the past, whenever I've released a tool I go in and update master for that branch as well, so the next full release picks it up, so that's all good.
>> 
>> What I am really interested in is this:
>>> #3 - The final step (actually closing it and releasing the artifacts to sonatype) are currently limited to a select group. Maybe this group should be more limited than the people actually doing the actions on Jenkins? Maybe not? I'm not sure how complex we want it
>> 
>> 
>> So that sounds like we DO need to go to sonatype and push it through? 
>> 
>> cheers,
>> Steve
> 
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20120423/8c7d4b2c/attachment-0006.html