Permalink
Browse files

Update the hybrid-base.pot file.

  • Loading branch information...
1 parent 5ed2ee0 commit d1f1e2fa8b1eeca5ba4407f8c3be08df3029090d @justintadlock committed Aug 19, 2015
Showing with 255 additions and 963 deletions.
  1. +255 −963 languages/hybrid-base.pot
Oops, something went wrong.

4 comments on commit d1f1e2f

@lkraav
lkraav commented on d1f1e2f Aug 20, 2015

Heya. Is the date-based tag an intermediary thing or is the versioning scheme changing permanently? major.minor actually helped me run things quite sane for a long while, it'd be cool if that scheme continued.

@justintadlock
Owner

I'm thinking of not having any versioning for Hybrid Base. The point is to get you started from version 1.0.0. Tagging releases by date makes some sense for this.

I'm not sure yet.

@lkraav
lkraav commented on d1f1e2f Aug 20, 2015

Well yeah. I'm looking at it from an agency perspective, which has all the fun stuff like maintaining all of the legacy versions, branches, etc. I realize this may be like 0,000001% of your userbase tho. Anyway, switching to date versioning, we probably wouldn't be able to tell the difference between 20150420 and 20150502 off the top of our heads. For 0.2 and 1.0 there's a clear major difference and helps keep discussions clear. I see traditional versioning being able to keep that clarity, since there's not going to be a whole lot of major versions. For dates, everything looks the same.

@justintadlock
Owner

The idea is to make Hybrid Base versionless and not have releases. How to best go about that is something I'm working out at the moment.

You really shouldn't be keeping up with Hybrid Base versioning. Rather, you should be keeping up your own versions of your own themes. For example, you'd never update from "version 1.0" to "version 2.0" of Hybrid Base.

Please sign in to comment.