-
Notifications
You must be signed in to change notification settings - Fork 189
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
am getting an extraneous separator between title and body #75
Comments
@tshepang thank you for reporting this. |
No, thanks for fixing it :) BTW, how is it that you did not experience the bug? Maybe fact that you use Markdown? |
I did notice the bug and was investigating it that you reported it here 😄 I don't have any hard data on how many people are using development version of Elegant. So sometimes these sort of problems happen. After releasing V2.0, all development will be done on a dev branch to avoid issues like this. |
I will do a better job next time. 👍 |
I think you should just simplify things by keeping things the way they are, at least for now. If you maintain a dev branch, you may not get as many testers as you do now. |
Excellent point. I agree and have thrown away the dev branch idea. |
One thing you might wanna do though is maintain a "stable" that matches the latest "stable" Pelican version. That way, we who care about new-things-now should be able to take the pain of constant breakage, and those who want "rock-solid" could stick to "released" versions. But maybe you don't feel that the theme is mature enough (or is popular enough) to care about this yet. |
Actually I want people who care of stable version to download it from here. If you are getting it from Git repo then I guess you are knowledgeable enough to tackle such issues. Anyway, we will soon reach our 2.0 milestone, which I hope will be the stable version for a long long time. |
I did not notice this until recently, so could be a recent change (I have latest git versions of the 3 tools: pelican, pelican-plugins, and elegant).
The text was updated successfully, but these errors were encountered: