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

Create CHANGELOG.md #1675

Closed
ctrl-brk opened this issue Dec 23, 2016 · 13 comments
Closed

Create CHANGELOG.md #1675

ctrl-brk opened this issue Dec 23, 2016 · 13 comments
Assignees
Labels
Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add
Milestone

Comments

@ctrl-brk
Copy link

ctrl-brk commented Dec 23, 2016

Would be very beneficial. The current process for me is go to primefaces web site, click on forum, click on topic, go to blog to read what changed in a new version. That's a long way.

@cagataycivici cagataycivici added the Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add label Jun 19, 2017
@cagataycivici
Copy link
Member

Thanks, we will consider it after 4.1.

@ghost
Copy link

ghost commented Oct 30, 2017

@cagataycivici version 4.3.0 has been released, still no change log in releases....

@Klinton90
Copy link

@ghost
Copy link

ghost commented Oct 30, 2017

@Klinton90 Blog entry describes 8 important changes, while full changelog has 85 closed issues. I don't want to waste my time going through 85 issues. And I don't want to waste my time going to github -> web site -> forum -> topic -> blog

@brian428
Copy link
Contributor

@cagataycivici Any progress on this? You've got a great library here, but understanding what has been changed/fixed/added between versions is way more difficult than it should be. Can't whoever is writing the various blog posts and forum posts just update a CHANGELOG.md file as well? Or use a package like conventional-changelog to generate a CHANGELOG? Please consider addressing this. Thanks.

@rafa-suagu
Copy link

Totally agree, must be present

@MattiJarvinen
Copy link

Currently looking at primeeng 4.2.2 upgrade to 5.2.4 no clue what has changed & where to look for that backwards incompatible change.

@szechyjs
Copy link

The lack of a CHANGELOG in this project is very frustrating! The only way I can figure out what changed is to go through the commit history, and even that is a pain as the commit messages only list Issue numbers.

screen shot 2018-04-25 at 11 42 16 am

@brian428
Copy link
Contributor

The bizarre thing is that they post occasional version updates on their blog, which means someone is doing some level of tracking on what has changed. Why they've decided to post these to their blog (where few will see it) instead of updating a README is truly baffling.

@ctrl-brk
Copy link
Author

With 5.2.7 release there's not even a blog post. Go figure...

@brian428
Copy link
Contributor

Just updating today and once again realizing how absurd it is that there's no CHANGELOG, so once again I get to do manual version comparisons to try and determine what actually changed.

Could the PrimeNG folks please add a CHANGELOG? It'd be two years late, but better late than never.

@viceice
Copy link

viceice commented Oct 11, 2018

Additionally they even add new features or breaking changes in bugfix releases. 😞

@cagataycivici cagataycivici added this to the 6.1.6 milestone Oct 18, 2018
@cagataycivici
Copy link
Member

Here is the initial version, we'll add more info about breaking changes as well so it will be maintained/updated from now on.

https://github.com/primefaces/primeng/blob/master/CHANGELOG.md

mertsincan added a commit that referenced this issue Oct 18, 2018
@cagataycivici cagataycivici modified the milestones: 6.1.6, 7.0.0-beta.1 Oct 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Enhancement Issue contains an enhancement related to a specific component. Additional functionality has been add
Projects
None yet
Development

No branches or pull requests

9 participants