View Single Post
Old 03-29-2015, 10:21 PM   #4
user_none
Sigil & calibre developer
user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.user_none ought to be getting tired of karma fortunes by now.
 
user_none's Avatar
 
Posts: 2,487
Karma: 1063785
Join Date: Jan 2009
Location: Florida, USA
Device: Nook STR
Quote:
Originally Posted by eschwartz View Post
The packages link is dead.
This has been fixed. GitHub won't allow you to make a release without a tag.

Quote:
Originally Posted by eschwartz View Post
The blog post mentions the whole lots-of-changes thing, and that there is no source revision to look at.
There is now.

Quote:
Originally Posted by eschwartz View Post
Can I suggest for the sake of less confusion, that in the future development
happens on a feature branch, and HEAD is reserved for completed changes? Then we can, like, tag a release...

It is traditional, after all...
Um... No, that's asinine. You can easily create a branch based on a tag and use that for the basis of bug fixes. Really for each release it should get it's own maintenance branch so head isn't tied up and not able to accept changes.

Realize that even complete feature changes made to head aren't always suitable for a bug fix/maintenance, PATCH release. So this situation wouldn't have been averted by only accepting complete feature changes into head. The only way to truly allow for patch release while continuing development is for me not to be lazy and to create maintenance branches for every release so fixes like this can be tracked.
user_none is offline