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

wron directory name for release archive for 3.0.3 #43

Closed
GoogleCodeExporter opened this issue Mar 22, 2015 · 4 comments
Closed

wron directory name for release archive for 3.0.3 #43

GoogleCodeExporter opened this issue Mar 22, 2015 · 4 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Download latest release of muparserx from 
http://articles.beltoforion.de/article.php?a=muparserx&p=download&s=idPageTop&ad
=1#idPageTop

2.unzip archive and the release folder is muparserx 3.0.3 as opposed to the 
archive name muparserx 3.0.2

What is the expected output? What do you see instead?

download an archive with 3.0.3?


What version of the product are you using? On what operating system?




Please provide any additional information below.


Original issue reported on code.google.com by rasha...@gmail.com on 15 Mar 2015 at 3:27

@GoogleCodeExporter
Copy link
Author

Current Version number in SVN repository is 3.0.5. So 3.0.2 is the last binary 
release which should be fine. I could not find a changelog for 3.0.3-3.0.5 so i 
presume the changes were of cosmetic nature that do not require a release.

Original comment by ib...@gmx.info on 15 Mar 2015 at 9:00

@GoogleCodeExporter
Copy link
Author

No. there is no need for any release. 

And yes, change is cosmetic. which btw is to have a muparserx_3.0.2 directory 
when extracting muparserx_3.0.2.zip

Original comment by rasha...@gmail.com on 15 Mar 2015 at 9:04

@GoogleCodeExporter
Copy link
Author

I will create a new release within in the next few days

Original comment by ib...@gmx.info on 20 Mar 2015 at 8:59

@GoogleCodeExporter
Copy link
Author

Thanks, a new release is much awaited!

Original comment by rasha...@gmail.com on 20 Mar 2015 at 9:04

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

No branches or pull requests

2 participants