Skip to content
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

Closed
tshepang opened this issue Nov 17, 2013 · 8 comments
Closed

am getting an extraneous separator between title and body #75

tshepang opened this issue Nov 17, 2013 · 8 comments
Milestone

Comments

@tshepang
Copy link

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).

screenshot from 2013-11-18 00 29 06

@talha131
Copy link
Member

@tshepang thank you for reporting this.

@tshepang
Copy link
Author

No, thanks for fixing it :)

BTW, how is it that you did not experience the bug? Maybe fact that you use Markdown?

@talha131
Copy link
Member

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.

@talha131
Copy link
Member

I will do a better job next time. 👍

@tshepang
Copy link
Author

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.

@talha131
Copy link
Member

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.

@tshepang
Copy link
Author

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.

@talha131
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants