On 12/7/2014 3:59 AM, Dave Liquorice wrote:
Ultimatey it's the sort of thing that ought to be completely
automagic. Starting from when yum spots a new update being available
or perhaps better part of a script that makes the update available. I
see that there might be scripts about that already do some of these
functions.
Exactly.
I was doing this the hard way at
http://wellsi.homeip.net/rnotes/sme9/9bugreport.html (currently empty)
which tracked RPMs and Bugs generating release notes along the way. I'll
try to get the above link useful again at least for a few months until
it can be deprecated.
Now that all the architecture is all on koozali servers and there is
effort being put into infrastructure I see that the release process
should be fully automated apart from the Go/NoGo decision which would be
taken by the release manager.
As I am limited in what I can do now, I would like to help setting this
up at least in terms of detailing what was done and providing the
scripts that I had in as much as they are useful.
Dave I am sure that the community would love your help as you described
in your post - it seems very do-able.
Ian
_______________________________________________
Discussion about project organisation and overall direction
To unsubscribe, e-mail [email protected]
Searchable archive at http://lists.contribs.org/mailman/public/discussion/
