Infrastructure help

[Kevin Meyer - KMZ <ke...@kmz.co.za>]

Hi all,

Partly to keep a hand in, partly to contribute in other ways, I will be 
working on providing some scripts and tools to help with some "admin" 
tasks..

First, since it's easier, I plan on improving the existing script for testing 
releases (adding error checking, etc).

After that... Please send me recommendations. For example, what can 
be done to help automate (some of) the release process?

Regards,
Kevin

Re: Infrastructure help

[Dan Haywood <da...@haywood-associates.co.uk>]

Hi Kevin,



On 10 June 2014 20:07, Kevin Meyer - KMZ <ke...@kmz.co.za> wrote:

> Hi all,
>
> Partly to keep a hand in, partly to contribute in other ways, I will be
> working on providing some scripts and tools to help with some "admin"
> tasks..
>
> First, since it's easier, I plan on improving the existing script for
> testing
> releases (adding error checking, etc).
>
>
ie the verify script.




> After that... Please send me recommendations. For example, what can
> be done to help automate (some of) the release process?
>
>
A good starting point would do a trial release on your own PC, just done
manually first, following the instructions in [1], [2], [3].

Since I wrote it for me, and only I've ever used it, there are bound to be
some gaps here and there (though I don't think they are in too bad nick).

You could even do the staging up to nexus, actually, though obviously the
staging repositories must be dropped, not released.

After that (and tidying up any documentation bugs), you could have a go at
testing/improving my release.sh script [4].  This is basically most of the
steps in [2], but I've never actually used it "in anger".

Other things that could be done include:
- keeping the STATUS file (in git home dir), doap_isis.rdf (in site home
dir) and release-matrix.md (in site home dir) in sync (eg use one as the
canonical form, generate others)
- building the release-matrix.md by parsing the various pom.xml files

~~~
A much bigger jtask (but would be very valuable) would be to write a full
Selenium regression test suite against the todo app (or more generally
against the TCK DOMs).  This is more to do with the "verify" task that you
mentioned earlier.

Hope some of that sounds appealing...

Cheers
Dan



Cheers
Dan


[1] http://isis.apache.org/contributors/release-process.html
[2] http://isis.apache.org/contributors/release-process-one-pager.html
[3] http://isis.apache.org/contributors/release-checklist.html
[4] http://isis.apache.org/contributors/resources/release.sh



[1] http://isis.apache.org/contributors/release-process.html



> Regards,
> Kevin
>
>