search

Mibew / mibew

Mibew Messenger - open-source live support application
https://mibew.org
Other
473 stars 204 forks source link

Changelogs from 2.1.2 to 2.2.0 ? #201

Closed nakupanda closed 7 years ago

nakupanda commented 7 years ago

Hi,

I would like to know where to get the change logs of the upgrade from previous version to current, I looked at issues, releases, and downloaded project but didn't find it.

thanks.

snewell92 commented 7 years ago

I'm not a Mibew, but I have a few ideas that could work for you.

What you can use instead of a changelog is look at the github releases page and do a diff between the release commits. Like this git diff 680059d cc55a13, that will show you the changes from 2.1.2 to 2.2.0.

You can also get a feel for what is currently going on by looking at the roadmap, development, and announcements pages (which you may have already looked at), but this information is still not as succinct or complete as a full changelog page like gitlab has (which gitlab automatically generates for those devs, so that would be neat to try to copy!).

In the vein of supporting this feature, I found an automatic changelog generator for github... but I don't know how viable of a solution that is.

faf commented 7 years ago

@nakupanda What exactly are you looking for?

If you want to know about changes between 2.2.0 and 2.1.2 that are significant for an end user, just have a look at the official release statement on the forum.

If you want to know about all changes between 2.2.0 and 2.1.2, do something like git log --oneline --decorate --color v2.1.2..v2.2.0 or use Github.

Frankly I don't see a compelling reason to auto generate changelog based upon the history of commits. It seems redundant.

dmcdaniel12 commented 7 years ago

@fedor I can see a use case for it if someone isn't that familiar with git or how to use it. However, I think most people are that use mibew.

On Thu, Mar 16, 2017 at 12:47 PM, Fedor A. Fetisov <notifications@github.com

wrote:

@nakupanda https://github.com/nakupanda What exactly are you looking for?

If you want to know about changes between 2.2.0 and 2.1.2 that are significant for an end user, just have a look at the official release statement on the forum https://mibew.org/forums/index.php/topic,192115.0.html.

If you want to know about all changes between 2.2.0 and 2.1.2, do something like git log --oneline --decorate --color v2.1.2..v2.2.0 or use Github https://github.com/Mibew/mibew/compare/v2.1.2...v2.2.0.

Frankly I don't see a compelling reason to auto generate changelog based upon the history of commits. It seems redundant.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Mibew/mibew/issues/201#issuecomment-287119212, or mute the thread https://github.com/notifications/unsubscribe-auth/ABPlZY33uJ1Rl74S3FCgRrqjiBB58jfrks5rmWeugaJpZM4MfDwL .

-- Derek McDaniel 614-664-3122

nakupanda commented 7 years ago

Thanks all, all helped.

I thought there was a list of issues here https://github.com/Mibew/mibew/issues?q=is%3Aissue+is%3Aclosed that got tagged 'fixed in 2.2.0' or something like that..

nakupanda commented 7 years ago

BTW no problem using GIT to get any detailed changes, just would like to go the easiest way first, looking at an issue list is that.

faf commented 7 years ago

@dmcdaniel12 I see it this way: git and its logs (the history of commits) are for developers. And release statements are for end users.

End user doesn't need to know about things like this or this. ;)

faf commented 7 years ago

@nakupanda I've got your point, but at the moment we don't use the issues that way.