2024-02-04 21:14:21 -08:00

276 lines
23 KiB
HTML
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

<!DOCTYPE html> <html lang='sr'> <head> <meta charset='utf-8'> <meta content='IE=edge' http-equiv='X-UA-Compatible'> <meta content='width=device-width, initial-scale=1.0' name='viewport'> <meta content='Ne dajte prijateljima da trpaju git logove u changelogove.' name='description'> <meta content='https://www.facebook.com/olivier.lacan.5' property='og:article:publisher'> <meta content='Vodite changelog' property='og:title'> <meta content='article' property='og:type'> <meta content='https://keepachangelog.com/sr/1.0.0/' property='og:url'> <meta content='Ne dajte prijateljima da trpaju git logove u changelogove.' property='og:description'> <meta content='https://keepachangelog.com/assets/images/keep-a-changelog-opengraph-851f2d20.png' property='og:image'> <link href='/assets/images/favicon.ico' rel='shortcut icon' type='image/x-icon'> <link href='https://keepachangelog.com/sr/1.0.0/' rel='canonical'> <title>Vodite changelog</title> <link href='https://fonts.googleapis.com' rel='preconnect'> <link crossorigin='true' href='https://fonts.gstatic.com' rel='preconnect'> <link href="//fonts.googleapis.com/css?family=Muli:400,700&amp;display=swap" rel="stylesheet"/> <link href="//fonts.googleapis.com/css?family=Source+Code+Pro:400,700&amp;display=swap" rel="stylesheet"/> <link href="/assets/stylesheets/application-d3e51c0c.css" rel="stylesheet"/> <script src="/assets/javascripts/all-466c2b8a.js" defer="defer"></script> </head> <body> <article> <header> <div class='last-version-notice'> The latest version (1.1.0) is not yet available in this language but <a href="/en/1.1.0">you can read it in English</a> for now and <a href="https://github.com/olivierlacan/keep-a-changelog/issues">help translate </a> it. </div> <nav class='locales' role='navigation'> <label for='language-select' title='Pick one of the 28 translations'>Languages (28):</label> <select id='language-select' name='language'> <option label='1.0.0 العربية' value='ar'> 1.0.0 العربية </option> <option label='1.1.0 Čeština' value='cs'> 1.1.0 Čeština </option> <option label='1.1.0 Dansk' value='da'> 1.1.0 Dansk </option> <option label='1.1.0 Deutsch' value='de'> 1.1.0 Deutsch </option> <option label='1.1.0 English' value='en'> 1.1.0 English </option> <option label='1.1.0 Español' value='es-ES'> 1.1.0 Español </option> <option label='1.1.0 Français' value='fr'> 1.1.0 Français </option> <option label='1.0.0 Hrvatski' value='hr'> 1.0.0 Hrvatski </option> <option label='1.0.0 Indonesia' value='id-ID'> 1.0.0 Indonesia </option> <option label='1.1.0 Italiano' value='it-IT'> 1.1.0 Italiano </option> <option label='1.1.0 日本語' value='ja'> 1.1.0 日本語 </option> <option label='1.1.0 Norsk (Bokmål)' value='nb'> 1.1.0 Norsk (Bokmål) </option> <option label='1.1.0 Nederlands' value='nl'> 1.1.0 Nederlands </option> <option label='1.1.0 polski' value='pl'> 1.1.0 polski </option> <option label='1.1.0 Português do Brasil' value='pt-BR'> 1.1.0 Português do Brasil </option> <option label='1.1.0 română' value='ro'> 1.1.0 română </option> <option label='1.1.0 Pyccкий' value='ru'> 1.1.0 Pyccкий </option> <option label='1.0.0 Slovenčina' value='sk'> 1.0.0 Slovenčina </option> <option label='1.0.0 ქართული' value='ka'> 1.0.0 ქართული </option> <option label='1.1.0 Slovenščina' value='sl'> 1.1.0 Slovenščina </option> <option label='1.0.0 Srpski' selected value='sr'> 1.0.0 Srpski </option> <option label='1.1.0 Svenska' value='sv'> 1.1.0 Svenska </option> <option label='1.1.0 Türkçe' value='tr-TR'> 1.1.0 Türkçe </option> <option label='1.1.0 Українська' value='uk'> 1.1.0 Українська </option> <option label='1.1.0 简体中文' value='zh-CN'> 1.1.0 简体中文 </option> <option label='1.1.0 正體中文' value='zh-TW'> 1.1.0 正體中文 </option> <option label='1.0.0 한국어' value='ko'> 1.0.0 한국어 </option> <option label='1.1.0 فارسی' value='fa'> 1.1.0 فارسی </option> </select> </nav> <img src="/assets/images/keep-a-changelog-mark-f8b06a42.svg" width="130" height="100" class="mark" alt=""/> </header> <div class='main' role='main'> <div class='header'> <div class='title'> <h1>Vodite changelog</h1> <h2>Ne dajte prijateljima da trpaju git logove u changelogove.</h2> </div> <a href="https://github.com/olivierlacan/keep-a-changelog/blob/main/CHANGELOG.md">Verzija <strong>1.0.0</strong> </a><pre class='changelog' lang='en'># Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
### Added
- v1.1 Brazilian Portuguese translation.
- v1.1 German Translation
- v1.1 Spanish translation.
- v1.1 Italian translation.
- v1.1 Polish translation.
- v1.1 Ukrainian translation.
### Changed
- Use frontmatter title &amp; description in each language version template
- Replace broken OpenGraph image with an appropriately-sized Keep a Changelog
image that will render properly (although in English for all languages)
- Fix OpenGraph title &amp; description for all languages so the title and
description when links are shared are language-appropriate
### Removed
- Trademark sign previously shown after the project description in version
0.3.0
## [1.1.1] - 2023-03-05
### Added
- Arabic translation (#444).
- v1.1 French translation.
- v1.1 Dutch translation (#371).
- v1.1 Russian translation (#410).
- v1.1 Japanese translation (#363).
- v1.1 Norwegian Bokmål translation (#383).
- v1.1 &quot;Inconsistent Changes&quot; Turkish translation (#347).
- Default to most recent versions available for each languages.
- Display count of available translations (26 to date!).
- Centralize all links into `/data/links.json` so they can be updated easily.
### Fixed
- Improve French translation (#377).
- Improve id-ID translation (#416).
- Improve Persian translation (#457).
- Improve Russian translation (#408).
- Improve Swedish title (#419).
- Improve zh-CN translation (#359).
- Improve French translation (#357).
- Improve zh-TW translation (#360, #355).
- Improve Spanish (es-ES) transltion (#362).
- Foldout menu in Dutch translation (#371).
- Missing periods at the end of each change (#451).
- Fix missing logo in 1.1 pages.
- Display notice when translation isn&#39;t for most recent version.
- Various broken links, page versions, and indentations.
### Changed
- Upgrade dependencies: Ruby 3.2.1, Middleman, etc.
### Removed
- Unused normalize.css file.
- Identical links assigned in each translation file.
- Duplicate index file for the english version.
## [1.1.0] - 2019-02-15
### Added
- Danish translation (#297).
- Georgian translation from (#337).
- Changelog inconsistency section in Bad Practices.
### Fixed
- Italian translation (#332).
- Indonesian translation (#336).
## [1.0.0] - 2017-06-20
### Added
- New visual identity by [@tylerfortune8](https://github.com/tylerfortune8).
- Version navigation.
- Links to latest released version in previous versions.
- &quot;Why keep a changelog?&quot; section.
- &quot;Who needs a changelog?&quot; section.
- &quot;How do I make a changelog?&quot; section.
- &quot;Frequently Asked Questions&quot; section.
- New &quot;Guiding Principles&quot; sub-section to &quot;How do I make a changelog?&quot;.
- Simplified and Traditional Chinese translations from [@tianshuo](https://github.com/tianshuo).
- German translation from [@mpbzh](https://github.com/mpbzh) &amp; [@Art4](https://github.com/Art4).
- Italian translation from [@azkidenz](https://github.com/azkidenz).
- Swedish translation from [@magol](https://github.com/magol).
- Turkish translation from [@emreerkan](https://github.com/emreerkan).
- French translation from [@zapashcanon](https://github.com/zapashcanon).
- Brazilian Portuguese translation from [@Webysther](https://github.com/Webysther).
- Polish translation from [@amielucha](https://github.com/amielucha) &amp; [@m-aciek](https://github.com/m-aciek).
- Russian translation from [@aishek](https://github.com/aishek).
- Czech translation from [@h4vry](https://github.com/h4vry).
- Slovak translation from [@jkostolansky](https://github.com/jkostolansky).
- Korean translation from [@pierceh89](https://github.com/pierceh89).
- Croatian translation from [@porx](https://github.com/porx).
- Persian translation from [@Hameds](https://github.com/Hameds).
- Ukrainian translation from [@osadchyi-s](https://github.com/osadchyi-s).
### Changed
- Start using &quot;changelog&quot; over &quot;change log&quot; since it&#39;s the common usage.
- Start versioning based on the current English version at 0.3.0 to help
translation authors keep things up-to-date.
- Rewrite &quot;What makes unicorns cry?&quot; section.
- Rewrite &quot;Ignoring Deprecations&quot; sub-section to clarify the ideal
scenario.
- Improve &quot;Commit log diffs&quot; sub-section to further argument against
them.
- Merge &quot;Why cant people just use a git log diff?&quot; with &quot;Commit log
diffs&quot;.
- Fix typos in Simplified Chinese and Traditional Chinese translations.
- Fix typos in Brazilian Portuguese translation.
- Fix typos in Turkish translation.
- Fix typos in Czech translation.
- Fix typos in Swedish translation.
- Improve phrasing in French translation.
- Fix phrasing and spelling in German translation.
### Removed
- Section about &quot;changelog&quot; vs &quot;CHANGELOG&quot;.
## [0.3.0] - 2015-12-03
### Added
- RU translation from [@aishek](https://github.com/aishek).
- pt-BR translation from [@tallesl](https://github.com/tallesl).
- es-ES translation from [@ZeliosAriex](https://github.com/ZeliosAriex).
## [0.2.0] - 2015-10-06
### Changed
- Remove exclusionary mentions of &quot;open source&quot; since this project can
benefit both &quot;open&quot; and &quot;closed&quot; source projects equally.
## [0.1.0] - 2015-10-06
### Added
- Answer &quot;Should you ever rewrite a change log?&quot;.
### Changed
- Improve argument against commit logs.
- Start following [SemVer](https://semver.org) properly.
## [0.0.8] - 2015-02-17
### Changed
- Update year to match in every README example.
- Reluctantly stop making fun of Brits only, since most of the world
writes dates in a strange way.
### Fixed
- Fix typos in recent README changes.
- Update outdated unreleased diff link.
## [0.0.7] - 2015-02-16
### Added
- Link, and make it obvious that date format is ISO 8601.
### Changed
- Clarified the section on &quot;Is there a standard change log format?&quot;.
### Fixed
- Fix Markdown links to tag comparison URL with footnote-style links.
## [0.0.6] - 2014-12-12
### Added
- README section on &quot;yanked&quot; releases.
## [0.0.5] - 2014-08-09
### Added
- Markdown links to version tags on release headings.
- Unreleased section to gather unreleased changes and encourage note
keeping prior to releases.
## [0.0.4] - 2014-08-09
### Added
- Better explanation of the difference between the file (&quot;CHANGELOG&quot;)
and its function &quot;the change log&quot;.
### Changed
- Refer to a &quot;change log&quot; instead of a &quot;CHANGELOG&quot; throughout the site
to differentiate between the file and the purpose of the file — the
logging of changes.
### Removed
- Remove empty sections from CHANGELOG, they occupy too much space and
create too much noise in the file. People will have to assume that the
missing sections were intentionally left out because they contained no
notable changes.
## [0.0.3] - 2014-08-09
### Added
- &quot;Why should I care?&quot; section mentioning The Changelog podcast.
## [0.0.2] - 2014-07-10
### Added
- Explanation of the recommended reverse chronological release ordering.
## [0.0.1] - 2014-05-31
### Added
- This CHANGELOG file to hopefully serve as an evolving example of a
standardized open source project CHANGELOG.
- CNAME file to enable GitHub Pages custom domain.
- README now contains answers to common questions about CHANGELOGs.
- Good examples and basic guidelines, including proper date formatting.
- Counter-examples: &quot;What makes unicorns cry?&quot;.
[unreleased]: https://github.com/olivierlacan/keep-a-changelog/compare/v1.1.1...HEAD
[1.1.1]: https://github.com/olivierlacan/keep-a-changelog/compare/v1.1.0...v1.1.1
[1.1.0]: https://github.com/olivierlacan/keep-a-changelog/compare/v1.0.0...v1.1.0
[1.0.0]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.3.0...v1.0.0
[0.3.0]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.2.0...v0.3.0
[0.2.0]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.1.0...v0.2.0
[0.1.0]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.0.8...v0.1.0
[0.0.8]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.0.7...v0.0.8
[0.0.7]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.0.6...v0.0.7
[0.0.6]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.0.5...v0.0.6
[0.0.5]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.0.4...v0.0.5
[0.0.4]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.0.3...v0.0.4
[0.0.3]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.0.2...v0.0.3
[0.0.2]: https://github.com/olivierlacan/keep-a-changelog/compare/v0.0.1...v0.0.2
[0.0.1]: https://github.com/olivierlacan/keep-a-changelog/releases/tag/v0.0.1
</pre> </div> <div class='answers'> <h3 id='what'> <a aria_hidden='true' class='anchor' href='#what'></a> Šta je changelog? </h3> <p> Changelog je datoteka koja sadrži uređeni hronološki poređani popis značajnih promena unutar svake verzije projekta. </p> <h3 id='why'> <a aria_hidden='true' class='anchor' href='#why'></a> Zašto voditi changelog? </h3> <p> Kako bi korisnici i saradnici detaljno videli značajne promjene među pojedinim izdanjima (ili verzijama) projekta. </p> <h3 id='who'> <a aria_hidden='true' class='anchor' href='#who'></a> Kome treba changelog? </h3> <p> Ljudima. Bilo da su uobičajeni korisnici ili programeri, krajnji su korisnici softvera ljudska bića kojima je stalo do toga od čega je sastavljen. Kada se softver menja, korisnici žele znati kako i zašto. </p> </div> <div class='good-practices'> <h3 id='how'> <a aria_hidden='true' class='anchor' href='#how'></a> Kako kreirati dobar changelog? </h3> <h4 id='principles'> <a aria_hidden='true' class='anchor' href='#principles'></a> Glavna načela </h4> <ul> <li> Changelogs služi <em> ljudima</em>, ne mašinama. </li> <li> Potrebno je stvoriti unos za svaku verziju. </li> <li> Slične promene potrebno je grupisati. </li> <li> Verzije i odeljci trebaju imati vezu. </li> <li> Poslednja verzija treba biti na prvom mestu. </li> <li> Datum izdavanja svake pojedine verzije treba biti vidljiv. </li> <li> Navesti prati li se <a href="https://semver.org/">Semantičko verzioniranje</a>. </li> </ul> <a aria_hidden='true' class='anchor' href='#types'></a> <h4 id='types'>Vrste promena</h4> <ul> <li> <code>Added</code> za nove funkcionalnosti. </li> <li> <code>Changed</code> za promene u postojećim funkcionalnostima. </li> <li> <code>Deprecated</code> za funkcionalnosti koje će se ukloniti u budućim verzijama. </li> <li> <code>Removed</code> za uklonjene funkcionalnosti. </li> <li> <code>Fixed</code> za ispravke bagova. </li> <li> <code>Security</code> za slučaj sigurnosnih propusta. </li> </ul> </div> <div class='effort'> <h3 id='effort'> <a aria_hidden='true' class='anchor' href='#effort'></a> Kako održavati changelog sa što manje napora? </h3> <p> Na vrh postavite <code>Unreleased</code> sekciju gde ćete navoditi nadolazeće promene. </p> <p>To radimo iz dva razloga:</p> <ul> <li> Korisnici mogu videti promene koje mogu očekivati u nadolazećim izdanjima </li> <li> Kod izdavanja nove verzije, moguće je <code>Unreleased</code> sekciju samo preimenovati u novo izdanje. </li> </ul> </div> <div class='bad-practices'> <h3 id='bad-practices'> <a aria_hidden='true' class='anchor' href='#bad-practices'></a> Može li changelog biti loš? </h3> <p>Naravno. Postoji nekoliko slučajeva u kojima changelog može biti beskoristan.</p> <h4 id='log-diffs'> <a aria_hidden='true' class='anchor' href='#log-diffs'></a> Commit log diffovi </h4> <p> Korištenje commit log diffova u svrhu changeloga nije dobra ideja: puni su šuma. Npr. merge commitovi, commitovi s nejasnim naslovima, promene u dokumentaciji i sl. </p> <p> Svrha commita je da beleži korake u razvoju izvornog koda. U nekim projektima se comittovi čiste, no ponekad i ne. </p> <p> Svrha unosa u changelogu je da beleži značajne razlike, a često kroz više commitova i jasno ih prenese krajnjem korisniku. </p> <h4 id='ignoring-deprecations'> <a aria_hidden='true' class='anchor' href='#ignoring-deprecations'></a> Ignorisanje uklonjenih funkcionalnosti </h4> <p> Kad korisnici nadograde softver na noviju verziju, treba biti potpuno jasno da postoji mogućnost da će se neki deo pokvariti. Softver treba biti moguće nadograditi na verziju koja će navesti funkcionalnosti koje trebaju biti uklonjene, uklanja takve te se kasnije može nadograditi na verziju gde su već uklonjene. </p> <p> U najmanju ruku, potrebno je u changelogu navoditi funkcionalnosti koje će biti uklonjene, funkcionalnosti koje su uklonjene i promene koje će uticati na rad softvera (breaking change). </p> <h4 id='confusing-dates'> <a aria_hidden='true' class='anchor' href='#confusing-dates'></a> Nejasni datumi </h4> <p> Regionalni formati datuma variraju delom sveta, pa je često teško pronaći format datuma koji će odgovarati svima. Prednost datuma u formatu <code>2017-07-17</code> je to što je poređan od veće prema manjoj jedinici: godina, mesec, dan. Ovaj je format takođe teško zameniti s drugim regionalnim formatima, za razliku od nekih koji, primera radi, menjaju poziciju oznake meseca i dana. Iz tog razloga, a i zbog toga što je navedeni format <a href="https://www.iso.org/iso-8601-date-and-time-format.html">ISO standard</a>, taj se format preporučuje za changelog unose. </p> <aside> Ali to nije sve. Pomozite u prikupljanju primera loše prakse <a href="https://github.com/olivierlacan/keep-a-changelog/issues">otvorivši issue</a> ili pull request. </aside> </div> <div class='frequently-asked-questions'> <h3 id='frequently-asked-questions'> <a aria_hidden='true' class='anchor' href='#frequently-asked-questions'></a> Česta pitanja </h3> <h4 id='standard'> <a aria_hidden='true' class='anchor' href='#standard'></a> Postoji li standardni changelog format? </h4> <p> Zapravo ne. Postoji <a href="https://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html#Style-of-Change-Logs">GNU changelog stilski priručnik</a>, i <a href="https://www.gnu.org/prep/standards/html_node/NEWS-File.html#NEWS-File">GNU NEWS file</a> "priručnik od dva odlomka". Nijedan nije adekvatan ni dovoljan. </p> <p> Cilj ovoga projekta <a href="https://github.com/olivierlacan/keep-a-changelog/blob/main/CHANGELOG.md">kvalitetniji changelog standard.</a> Nastao je prikupljanjem primera dobra prakse u open source zajednici. </p> <p> Konstruktivna kritika, raprave i predlozi za poboljšanje <a href="https://github.com/olivierlacan/keep-a-changelog/issues">su dobrodošli.</a> </p> <h4 id='filename'> <a aria_hidden='true' class='anchor' href='#filename'></a> Kako nazvati changelog datoteku? </h4> <p> Dajemo joj naziv <code>CHANGELOG.md</code>. Neki projekti još koriste <code>HISTORY</code>, <code>NEWS</code> ili <code>RELEASES</code>. </p> <p> Iako može delovati da naziv changelog datoteke i nije toliko bitan, čemu otežavati korisnicima da dođu do informacije o promjenama? </p> <h4 id='github-releases'> <a aria_hidden='true' class='anchor' href='#github-releases'></a> Šta s GitHub Releases? </h4> <p> To je ozbiljna inicijativa. <a href="https://docs.github.com/en/github/administering-a-repository/releasing-projects-on-github/managing-releases-in-a-repository">Releases</a> se mogu koristiti kako bi git oznake (npr. git oznaka <code>v1.0.0</code>) pretvorili u opširnije beleške o izdanju, upisujući ih ručno ili pak preuzimajući anotirane git oznake i pretvarajući ih u unose. </p> <p> GitHub Releases stvara statični changelog vidljiv korisnicima unutar GitHub repozitorijuma. Moguće ih je urediti u format koji bi odgovarao Vodite changelog formatu, no često je nešto opširniji. </p> <p> Trenutna GitHub releases verzija i nije baš sasvim vidljiva korisnicima, za razliku od uobičajenih datoteka označenih velikim slovima (<code>README</code>, <code>CONTRIBUTING</code>, itd.). Još je jedan manji problem što trenutno interfejs ne nudi poveznice na commit logove između izdanja. </p> <h4 id='automatic'> <a aria_hidden='true' class='anchor' href='#automatic'></a> Mogu li changelogovi automatski parsirati? </h4> <p> Teže, jer se koriste vrlo različiti formati, kao i nazivi datoteka. </p> <p> <a href="https://github.com/tech-angels/vandamme/">Vandamme</a> je Ruby gem koji je kreirao Gemnasium tim i može parsirati mnoge (ali ne sve) changelogove projekata otvorenog koda. </p> <h4 id='yanked'> <a aria_hidden='true' class='anchor' href='#yanked'></a> Šta s povučenim izdanjima? </h4> <p> Povučena ili 'Yanked' izdanja su verzije koje su uklonjene zbog ozbiljnijeg baga ili sigurnosnog propusta. Takva se izdanja najčešće i ne pojavljuju u changelogu, iako bi trebala. Trebala bi biti navedena na sledeći način: </p> <p><code>## [0.0.5] - 2014-12-13 [YANKED]</code></p> <p> <code>[YANKED]</code> oznaka jasno je istaknuta s razlogom. Bitno je da ju je lako primetiti. Buduće da je okružena zagradama, takođe ju je lakše parsirati. </p> <h4 id='rewrite'> <a aria_hidden='true' class='anchor' href='#rewrite'></a> Da li je potrebno prepravljati changelog? </h4> <p> Naravno. Često postoje dobri razlozi da bismo poboljšali changelog. Ja često otvaram pull requestove kako bih dodao nedostajuća izdanja projektima otvorenog koda, koji ne održavaju changelogove. </p> <p> Moguće je, takođe da otkrijete, kako ste zaboravili navesti promenu koja bi uticala na rad (breaking change). U tom slučaju je, očito, vrlo bitno ažurirati changelog. </p> <h4 id='contribute'> <a aria_hidden='true' class='anchor' href='#contribute'></a> Kako doprineti? </h4> <p> Ovaj dokument nije <em>Sveto Pismo</em>; ovo je samo pažljivo razmotreno mišljenje, uz informacije i primere koje sam skupio. </p> <p> Razlog je tome to što želim da zajednica postigne konsenzus. Verujem, takođe, da je i sama rasprava bitna kao i krajnji rezultat. </p> <p> Zato, molimo <strong><a href="https://github.com/olivierlacan/keep-a-changelog">uskočite</a></strong>. </p> </div> <div class='press'> <h3>Razgovori</h3> <p> Gostovao sam na <a href="https://changelog.com/podcast/127">The Changelog podcastu</a> gde sam pokušao objasniti zašto začetnici projekata i saradnici trebaju brinuti o changelogovima te motivaciji iza ovog projekta. </p> </div> <footer class='footer clearfix' role='contentinfo'> <img src="/assets/images/keep-a-changelog-mark-f8b06a42.svg" width="30" height="30" class="mark" alt=""/> <p class='about'> This project is <a href="https://choosealicense.com/licenses/mit/">MIT Licensed</a> // <a href="https://github.com/olivierlacan/keep-a-changelog/">Created & maintained</a> by <a href="https://olivierlacan.com/">Olivier Lacan</a> <a href="https://ruby.social/@olivierlacan" rel="me" aria-label="Link to Olivier Lacan's Mastodon account"></a> // Designed by Tyler Fortune </p> </footer> </div> </article> </body> <script>
var _gauges = _gauges || [];
(function() {
var t = document.createElement('script');
t.type = 'text/javascript';
t.async = true;
t.id = 'gauges-tracker';
t.setAttribute('data-site-id', '5389808eeddd5b055a00440d');
t.src = '//secure.gaug.es/track.js';
var s = document.getElementsByTagName('script')[0];
s.parentNode.insertBefore(t, s);
})();
</script> </html>