Charly Coste
Charly Coste
Or maybe we want to convert some of the old docs from HTML to Sphinx (#339)?
It's not in my priorities, but making sure that changing the config is either impossible or straightforward is definitely something we want.
-1 on squashing history. An automatic changelog would be nice, but it's not important enough to destroy history, especially when there are cleaner solutions like adding custom `Changelog:` lines in...
When I'm looking into the history of a specific line or file I don't do it on GitHub, I do it locally with a git UI that makes it easier...
A tag would indeed protect the commits, they still wouldn't show up in the history though, so a `git blame` will lead you to a big squashed commit instead of...
@pjz Intermediate commits can be squashed into a smaller number of "complete" commits. I usually do that kind of rebasing before pushing, but it can also be done later and...
I don't know, but I don't see #473 as a blocker for 1.0 if that's what you're asking.
I've just noticed that there was [an old 1.0 milestone](https://github.com/AspenWeb/pando.py/milestone/1), so I've closed it.
And the [Simplify Simplates](https://github.com/AspenWeb/pando.py/milestone/3) milestone too.
Nope, especially since it still had an open issue. I closed the milestone because it was out-of-date since you've been using this issue for the 1.0 roadmap instead.