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

Why don't you add Release notes after 10.1.0 ? #123

Closed
AknEp opened this issue Mar 23, 2016 · 10 comments
Closed

Why don't you add Release notes after 10.1.0 ? #123

AknEp opened this issue Mar 23, 2016 · 10 comments

Comments

@AknEp
Copy link

AknEp commented Mar 23, 2016

Where is release note for 11.1.1 ?

I cannot find it in below sites:

@hsbt
Copy link
Member

hsbt commented Mar 25, 2016

It caused by maintenance policy changes. I have no plan to create release note under doc directory. Please see History.rdoc

@hsbt hsbt closed this as completed Mar 25, 2016
@AknEp
Copy link
Author

AknEp commented Mar 25, 2016

Where does the policy described?
How user can know about this change?

you should write about this change in these pages.

I think this issue should not be closed yet.

@satoryu
Copy link
Contributor

satoryu commented Mar 25, 2016

According to README.rdoc, it seems that the official doc has been moved to http://docs.seattlerb.org/rake from rubyforge.com and the link to doc on rubygems.org also has been changed. but I could not find any document looking the maintenance policy yet.

The existence of rubyforge's one make developers misunderstanding about rake so it should be closed, I think.

@hsbt How do you think?

@hsbt
Copy link
Member

hsbt commented Mar 25, 2016

@AknEp I wonder why don't you see History.rdoc. ex. I noticed to remove RAKEVERSION constant at Rake 11. Is it insufficiency? Does Release notes solve your frustration?

@satoryu Exactly. rubyforge is already sunsets in Ruby ecosystem.

@AknEp
Copy link
Author

AknEp commented Mar 25, 2016

@hsbt Because Release Notes page are exists, I cannot guess that another document exists.
and I don't know this plovy changing.

If such important feature changing are well-documented , I solved my problem more speedy.
By not maintained these pages, you wasted my time, and will waste another ruby user's time.

@hsbt
Copy link
Member

hsbt commented Mar 25, 2016

Again. Is it insufficiency with History.rdoc? I documented it.

@hsbt
Copy link
Member

hsbt commented Mar 25, 2016

And I can not modify rubyforge page. Nobody change it. Even if I added release note, rubyforge page was not update release note. It does not solve your problem.

@AknEp
Copy link
Author

AknEp commented Mar 25, 2016

Hostory.rdoc is sufficient, it's good document. but, problem is not linked from old official (or seems to be official) docunents...

And I can not modify rubyforge page. Nobody change it. Even if I added release note, rubyforge page was not update release note.

oh my...
I think it is no good, but I understand constraints of rubyforge.
Thanks for your explaination.

Could you add link to history.rdoc in github's latest releases note? Is it permitted for you? This page is confusing.

@hsbt
Copy link
Member

hsbt commented Mar 25, 2016

It's ok. github's latest releases note means https://github.com/ruby/rake/releases/tag/v11.1.1 ?

I'm going to add feature changes and bug fixes information to release pages at next release.

@AknEp
Copy link
Author

AknEp commented Mar 25, 2016

Thank you. looks good.

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

3 participants