Comments (6)
how semantic rules work on this project? ... Could you please explain a little bit?
@soullivaneuh Sure!
MAJOR version when you make incompatible API changes
Major versions are released every time a path is broken (e.g.: a directory is renamed or moved into archive/
without having a replacement). This is done because I consider that to be a breaking change in the "API" as people who depend on that path will no longer have it.
MINOR version when you add functionality in a backwards-compatible manner
Minor versions are released mainly when the SVG version of a logo and/or a new logo is added.
PATCH version when you make backwards-compatible bug fixes
Patch versions are released when typos or links are fixed, images are further losslessly optimized, a better version of a logo is added by just replacing the existing images, etc..
I hope this helps!
I was on 3.* and just see you are on v22.
Yes, things move fast nowadays! :D
from browser-logos.
Thanks for the explanation. :-)
I think this should be added on the doc. 👍
I completly understand the new major for moving file, but you have to push a lot of them. Why not use a more BC keep method? Let me explain my suggestion:
Imagine you are on v1.0.x and you want to archive a logo. You could
- Move the logo on the
archive
folder. - Create a symbolic link of the old file, pointing to the archive folder (git and github manage symlinks like a charm).
Then, the old logo is archived but still accessible from user. Them, you can push v1.1 instead of v2.0.
When you have a lot of deprecated logos and want to clean up, then you can create a new major.
What do you think?
BTW, deleted/moved logos should be marked in the Changelog IMHO.
from browser-logos.
Create a symbolic link of the old file, pointing to the archive folder... them, you can push v1.1 instead of v2.0....
When you have a lot of deprecated logos and want to clean up, then you can create a new major
@soullivaneuh That would just complicate things a lot without any real benefit as far as I see. Plus, you're just prolonging the inevitable, namely, releasing new major
versions. Also, given enough time, you will still end up at versions such as 35.y.z
.
deleted/moved logos should be marked in the Changelog
That is usually stated (e.g.: Move X
logo into the archive/
), and if users want more detailed information, they can just read the commit messages or look at the commits.
from browser-logos.
That would just complicate things a lot without any real benefit as far as I see.
The benefit for user would be to have new update without have to check new majore every week. :-)
Also, given enough time, you will still end up at versions such as 35.y.z.
Not 35, but a lower number, less major versions...
But I understand, this is harder to maintain, this is just a suggestion. ;-)
from browser-logos.
have to check new majore every week. :-)
@soullivaneuh I don't think that's a big problem. From what I've seen, most users only care about the main browsers. Plus, when those browsers update their logos it is usually known, therefore, users will most probably only check / update at that point.
this is just a suggestion.
Sure thing, suggestions are always welcomed! 👍
from browser-logos.
deleted/moved logos should be marked in the Changelog IMHO.
Updated the CHANGELOG
and the releases
. ✨
from browser-logos.
Related Issues (20)
- Add `Finebits Internet Browser` logo HOT 1
- Quantifying the new browser criteria HOT 4
- Can't install the package via npm HOT 1
- Update Web (f.k.a. Epiphany) web browser logo? HOT 1
- Incorrect version info? HOT 1
- Add `SpiderMonkey` logo
- Add `wexond` logo HOT 2
- `internet-explorer_9-11.svg` is very large HOT 4
- Add the NodeJS logo HOT 2
- Add type declarations HOT 1
- Add new Chromium and Chrome logos HOT 25
- Chromium Logos and sources. HOT 2
- Logo Request: Waterfox browser logo HOT 1
- Firefox Focus archived?
- Add Arc's Logo HOT 1
- Internet Explorer Icon HOT 1
- PLease add LibreWolf browser logo
- Add Chrome for Testing logo HOT 1
- Add Atom browser logo
- Edge svg doesn't open in Figma HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from browser-logos.