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

[Matthew Jones]

FYI, the *ideal* goal of indies is that we release kernel only when needed,
and master gets released whenever we do a full release.

If we have people monitoring the individual tools, we don't need to release
them as part of the full release and can skip them. For some tools that
have no project teams that nobody (or only cle-release-team) are watching,
for 2.10 I'd like to split the api/impl to separate versions, release the
api and fold the rest of the tool back up into the core to make it easier
for local customization.

That's a conference discussion though but one I'd talked to Anthony about
for at least a couple of years.

On Mon, Apr 23, 2012 at 1:09 AM, Matthew Jones <matthew at longsight.com>wrote:

> Hi Steve,
>
> Right now that guide is mostly just me taking notes for myself or anyone
> else that might want to take over the release process as it currently is,
> or maybe improve it for the better. Like you said it's a guide for doing an
> *entire release* (like the next beta) since there hasn't been anyone yet
> emailing me or demanding on the Thursday meetings that they release their
> tool.
>
> This has worked so far in the beta since I've been pumping out a new
> release every 3 weeks or so, much faster now than a typical release
> schedule (which in the past has had months between releases).
>
> The goal for all this work and getting it on Jenkins though was for
> someone who had an active indie tool to be able to login to Jenkins, click
> on your tool (2.9.x version or whatever) click the button "Perform Maven
> Release", fill in the release version, the snapshot version and your SVN
> credentials and it would do a single tool release.
>
> There are a few minor things unfinished with this
> #1 - I haven't tested this, while it should work I'm not 100% sure it will
> :)
> #2 - If an individual is doing a release, I feel like they should put in
> *their* SVN credentials. I don't think cle-release-team should release it
> right?
> #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
> #4 - I have to somehow know that a new release is done so master can be
> updated correctly for the next "full release" currently we aren't keeping
> track of that anywhere.
> #5 - I could probably also put a much simpler UI in front of #2-#5 that
> would just ask for the tool, release version, dev version. It would perform
> the release and keep track of the release version for whoever is doing the
> full build.
>   - I could also possibly do this in a "post-build" script. Speaking of
> post-build script, that still needs to be written to reset the parent back
> to SNAPSHOT.
>
> All of this can for sure get done by the conference. A lot got done
> between this last beta already.
>
> It looks like you (Steve) have an account on Jenkins. So if you want to
> try it out, go for it.
> - Click profile 2.9.x -> Perform Maven Release -> Fill in the details ->
> See what happens
>
> You probably have to update the 2.9.x branch parent back after the release
> if I don't add the post-build step before you try it, and might have to
> remove tags if something goes wrong for some reason.
>
> Just let me know what version of Profile2 you'd want for the b06 tag.
>
>  On Sun, Apr 22, 2012 at 9:03 PM, Steve Swinsburg <
> steve.swinsburg at gmail.com> wrote:
>
>> Hi all,
>>
>> I'm wondering how we now release indie tools individually. I have seen
>> this guide:
>> https://confluence.sakaiproject.org/display/REL/Sakai+CLE+release+guide
>>
>> but it assumes we are releasing everything.
>>
>> Basically, I want to know how I might go and release a version of
>> something (say Profile2) whenever I want to.
>>
>> I know how to use Jenkins to do it, but do I then need to go and push
>> them through the various stages in Sonatype?
>>
>> Also, if I was to make a release of something that is currently going
>> through the 2.9 alpha/beta release process is anyone going to get upset? I
>> have some fixes I want to use in a release.
>>
>> thanks,
>> 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/c37469f2/attachment-0006.html