Released Yet Another MPEG Daemon today. Justin and Paul have been helping me with it and I expect (he he he) them to be contributors for the code soon.
Open Source Package Management
I found updating open source packages to take a lot of time even when understanding the process.
- cvs update
- Hack, test, hack, test
- cvs commit files with comments.
- Increase version/release number
- Build tar ball
- Build any number of binary packages.
- Update home page for product (ie: upload files and edit html)
- Upload files to source forge
- Use sourceforge interface to release tar ball and debian package (in the case of yamd that was a server, library and client, totalling six files).
- Enter new annoyncement in freshmeat with download locations and indexes(create appindex if necessary)
- Update my diary here.
And I am sure I have missed some steps. Things like making sure that the tar ball has had all temporary and CVS files removed.
I am wondering if there is a way to imporve this process. It is many ftp and web pages to fill in and only after all the builds.
In my rescent experiences these have been any architecture packages too, but if they where compiled then I may have to build a number of them.
I know there is build boxes for the packages etc. But I wonder also if there is programs that can do the rest of the manual releases. Well I will have a look around.
The great news about work is that Dan is back. Hopefully this means that my life will return to normal. It does however mean that both ours (and others) roles are going to hvae to change, and moulding those new roles is going to be interesting.