Yes I know, it’s like a year since the last development release of Backup Manager has been published, I should be ashamed of such a huge idleness.
But actually, If you ask me, I’m not. Instead of writing long lines of haiku to apologize for being so late at releasing, here is an illustrated reason why it was so loooong.
Dear lazyweb, this sunday afternoon, I opened BackupManager’s Bugzilla and started squashing bugs. There was 54 bugs opened that requested a review. 15 of them are now tagged “pending” (meaning they’re closed in SVN and will be shiped with the next release).
All of the patches submited - that made sense - were applied, thanks to all the reporters for their help, by the way.
So, fear a new release soon…
Hey Yay, Backup Manger 0.7.6 came out of the SVN repo!
Expect the Debian package to be uploaded soon in sid.
During my christmas holydays, I managed to find some time for backup-manager (it was hard last months to do so because of my paid-work).
The good news is that there is only one 0.8-blocker left in the bug database.
I’ve closed all the others, including a security issue regarding the way BM handles the MySQL client password and some fixes about the way encryption is performed.
I hope I can close that last bug soon, and at last, release 0.8…
Stay tuned.
That’s pretty cool to have such a useful environment like alioth for handling collaborative maintenance.
I joined the Debian Perl Group recently in order to put my Perl packages into the hand of the team, and that reminded me how alioth is a powerful tool when you’re about handling a debian package with others.
As I receive quite often some po/po-debconf updates for the package backup-manager, I decided to exhume the pkg-backup-mngr project, in order to handle the source with subversion, and to let the translators commit their changes. I now use enormously svn-buildpackage and I feel pretty happy about that.
I even think about opening an alioth project for every single package I maintain (and of course, which cannot be handled by an already existing team).
Update
I apprently forgot the last paragraph of that post in my mind, and the mail Philipp Kern sent me made me aware of that (pointing to Raphaël Hertzog announcement about collab-maint). Indeed, Philipp, I wanted to conclude my post with something about collab-maint, I guess it’s done now. Thanks!
I’ve created a new mailing list for translations coordination : backup-manager-i18n. Every one involved in the translation of Backup Manager should subscribe to that list.
Now that my Debian packages are in a better shape, I’m focusing on closing as much upstream bugs as I can in the BackupManager source tree. The more I close, the more I think it’s time to freeze the code for targetting a new stable release.
I’d like very much to manage to release Backup Manager 0.8 before Debian enter its frozen-prerelase phase; providing a mature version of BM within “etch” would rock.
I finnaly took the time to package 0.7.4 for Debian, thanks to Philipp Kern, it has just been uploaded.
This package closes about ten bugs and provide the last available “development” release of Backup Manager. I hope this package will please those who will “apt-get” into it.
I now plan to fix as much upstream bugs as I can, and moreover, work on the inclusion of rdiff-backup.
I finally managed to get my new servers up-and-running (got all the worst issues you can imagine with my hardware provider), hosted in the french data-center “TeleHouse 2″.
It’s a Dual Core AMD 64 that runs a “Debian 3.1 Sarge” system, rock on babe!
Now, it’s time to move everything from nyx.sukria.net (my home-hosted box) to hypnos.sukria.net…
(…and yeah, @backup-manager.org services are affected by these changes)
The 0.7.4 release of Backup Manager was published a few days ago, it provides a couple of bug fixes (most of them coming from the 0.7.3 version) and support a new feature : purging over SSH.
The current “work-in-progress” stuff is, randomly :
I’m also rewriting the purging stuff within backup-manager-upload in order to apply the same purging rules as for local purging. This is almost done for FTP and SSH uploads now, it only remains the Amazon S3 method, whcih is maintained by Brad.
I’m also willing to take the time to plan a release roadmap for the next stable version : 0.8. My goal is to sync BM’s stable release with Debian’s…
