Release stable version 7.x-1.0

Hiya. Thank you for the nice words.

However instead i'd prefer you to test, review and report the module...
We're currently lacking feedback from the community. The D7 port is very rarely used.

Stable will follow once we have fixed our critical issues and users start to test thoroughly.

The latest development snapshot is always available at the project page as version 7.x-1.x-dev.

I went through the issue list and committed a few cosmetic patches today.

As there are no more open bugs for 7.x (only a few low priority feature requests), I think we're ready to at least create a 7.x-1.0-beta1 release. I already created the related tag at the repo, but it seems like I lack the permissions to create the release itself. Would be great if someone (@miro_dietiker?) could do that :-)

Also, someone has to do #1222726: Update project page for version 7.x in the near future...

As we have a growing number of users which use the beta1 version and therefore don't get the latest -dev changes but are more likely to update to the next beta, I tagged the latest commit as 7.x-1.0-beta2.
@miro_dietiker: Could you please create a new release? :-)

Created. Available.
Changelog missing (it is common to write what's been updated since versions...)

Oh sorry, I'll add a short changelog to the tag next time :-)

There should be a CHANGELOG.txt in the root with issue references.
One paragraph per version.

See sample of views:
http://drupalcode.org/project/views.git/blob/refs/heads/7.x-3.x:/CHANGEL...

Since we are on git, one could easily consult git log to build this file. However it should be present for serious projects.
I think for a final stable version (latest) we should add the history file.

Three years later.... Still no stable 1.0 release. Is it ever going to happen?

I should add that I'm successfully using the dev version on a number of projects (we're making extensive use of the exportable optionsets with features) and we're including it in a Distro we're building as well. A stable version would be very nice to be able to rely on a solid foundation, and pave the way for processing through the 200+ open issues safely.

Hm.. We have pushed galleria a lot, 3 years ago. Then kroimon took over and provided an awesome UI improvement.
Most of our projects are not using galleria anymore and we maintain tons of modules. That's why we stopped pushing the project.
Without a current background of active projects using it, you simply can't properly maintain a module.

Beta3 is a pretty fine state for a module. I would never release a stable version as long as there are open known bugs. And i see no one caring about all these issues.
I agree though, that a next release like Beta4 would make sense. However, considering the issues, i fear a Beta4 would trigger Beta3 users into new bugs... I didn't follow kroimons final development steps and our strict rule of maintenance and experience collected, is a solid test coverage for formal quality assurance. This is preventing me from further releases.

If you like to see improvements in this situation, you would need to involve someone in your projects that is responsible for all the maintenance work.