Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Hi,
hostmaster is being stabilized to reach beta quality so we can release the first version of it.
Adrian (Hostmaster's author) is focusing on the release in the coming weeks.
Currently you can check it out from CVS, we are trying to help in documentation and bug fixing so if you're in a contributer mindeset feel free to check it out and start publishing comments or bug reports.
best regards
Lior
I wasn't creating dev snapshots because it was moving too quickly. As in, several commits a day.
Removing the d.o tarballing process removes another point of failure / miscommunication for a project in such active development. Because HM spans several projects, you'd end up having to re-download all the various tarballs every day (if the latest one is even available yet)
While in such active development (and especially because this is an install profile.. with install wizard), testing this system involves wiping it out and re-installing it several times a day. As such, i'm not providing an upgrade path yet, as it would slow down development considerably.
So i'm hesitant to provide a tarball until I can guarantee that the user experience using it is right, and that means getting close to feature parity and having an upgrade path for all users.
And in personal experience, I've had actual end users start using software that really wasn't ready because it had a -dev release, regardless of warnings. When I do make a release, it will be ready for these people too.
Comments
Comment #1
liorkesos commentedHi,
hostmaster is being stabilized to reach beta quality so we can release the first version of it.
Adrian (Hostmaster's author) is focusing on the release in the coming weeks.
Currently you can check it out from CVS, we are trying to help in documentation and bug fixing so if you're in a contributer mindeset feel free to check it out and start publishing comments or bug reports.
best regards
Lior
Comment #2
mlncn commentedWhy not enable snapshot revisions? Don't list on the project page, and keep the warnings, but let people download a dev tarball from "All releases."
Is knowledge of CVS otherwise necessary for testing?
Comment #3
adrian commentedCheck http://groups.drupal.org/hm2/overview.
I wasn't creating dev snapshots because it was moving too quickly. As in, several commits a day.
Removing the d.o tarballing process removes another point of failure / miscommunication for a project in such active development. Because HM spans several projects, you'd end up having to re-download all the various tarballs every day (if the latest one is even available yet)
While in such active development (and especially because this is an install profile.. with install wizard), testing this system involves wiping it out and re-installing it several times a day. As such, i'm not providing an upgrade path yet, as it would slow down development considerably.
So i'm hesitant to provide a tarball until I can guarantee that the user experience using it is right, and that means getting close to feature parity and having an upgrade path for all users.
And in personal experience, I've had actual end users start using software that really wasn't ready because it had a -dev release, regardless of warnings. When I do make a release, it will be ready for these people too.
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.