Maybe, we can create at every end or begin of a month a new stable release.
So the stable release of this month if we use the format "year.month", would be: "15.05" for example, the stable release of june would be "15.06".
This allows easy recognition of the "release date" of this build. And not random like 0.1; 0.2 etc.
The question is, if this stable release should be scheduled for the same date in every month, or should it be individual created "if it's ready".
I think it should be scheduled for a specific date in every month. For example the last day in every month. So we can say, one week before this last day in the month, were the stable will be released, is feature freeze in the stable branch, and only fixes can come up in this branch, to guarantee stability. And finally the stable release can be pushed. After this, the schedule can begin again.
So the stable release of this month if we use the format "year.month", would be: "15.05" for example, the stable release of june would be "15.06".
This allows easy recognition of the "release date" of this build. And not random like 0.1; 0.2 etc.
The question is, if this stable release should be scheduled for the same date in every month, or should it be individual created "if it's ready".
I think it should be scheduled for a specific date in every month. For example the last day in every month. So we can say, one week before this last day in the month, were the stable will be released, is feature freeze in the stable branch, and only fixes can come up in this branch, to guarantee stability. And finally the stable release can be pushed. After this, the schedule can begin again.