PhileCMS / Phile

A flat file CMS with a swappable parser and template engine.
https://philecms.github.io/
Other
257 stars 49 forks source link

[TASK] Forgo v1.2.1 and go to v.2.0 #124

Closed james2doyle closed 10 years ago

james2doyle commented 10 years ago

Since we just dropped PHP 5.3 that would be considered a breaking change, therefore we should have a version bump.

According to semver:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards-compatible manner, and PATCH version when you make backwards-compatible bug fixes.

NeoBlack commented 10 years ago

I do not think we should go to version 2.0. we had much earlier to drop the support for 5.3, maybe before 1.0.0 of phile.

james2doyle commented 10 years ago

Here is the changelog as of this moment.

I dont think going to 1.2.1 makes sense. Maybe going to 1.3.0 now?

NeoBlack commented 10 years ago

1.3.0 is ok for me, but we should merge the two last pull request before next release, then we have also a good base for unit testings. I will move all issues and pull request to milestone 1.3.0

james2doyle commented 10 years ago

Yeah that is what I am suggesting. For the next version bump we should definitely do 1.3.0

james2doyle commented 10 years ago

I will generate the new changelog and bump the versions

NeoBlack commented 10 years ago

result from the last merge for next release: Tests: 33, Assertions: 42, Incomplete: 1. looks good :) I think we should make a feature freeze and release 1.3.0 next week after some manual testings.

james2doyle commented 10 years ago

Sure. I have a branch ready on my Github with the bump so if everything is good it will be fine.

https://github.com/james2doyle/Phile/commit/3e4facece9ed8a0c6e9f5b777ee0aac2137219a8

NeoBlack commented 10 years ago

yeah, cool. I love GIT :) But in your changelog are a lot of URL which looks like this: https://github.com/AUTHOR/REPO/commit/68281e5ffd15447d76a23e88e9ae6d82c1160aa0

because the /AUTHOR/REPO/ the links not working.

james2doyle commented 10 years ago

Oh whoops I need to fix that

On Friday, August 22, 2014, Frank Nägler notifications@github.com wrote:

yeah, cool. I love GIT :) But in your changelog are a lot of URL which looks like this: AUTHOR/REPO@68281e5 https://github.com/AUTHOR/REPO/commit/68281e5ffd15447d76a23e88e9ae6d82c1160aa0

because the /AUTHOR/REPO/ the links not working.

— Reply to this email directly or view it on GitHub https://github.com/PhileCMS/Phile/issues/124#issuecomment-53119276.

James Doyle

t: @james2doyle https://twitter.com/james2doylew: ohdoylerules.com http://ohdoylerules.com

NeoBlack commented 10 years ago

I change the travis file to use PHPUnit 4.2.2, now all tests passed also under hhvm.

james2doyle commented 10 years ago

I would be curious to see the hhvm performance vs normal PHP. Also seeing PHPng performance would be cool too

NeoBlack commented 10 years ago

Ok, i think we are now ready for 1.3.0. can you Update your branch and create a new changelog file and pull request?

NeoBlack commented 10 years ago

release 1.3.0 is out now, I will close this issue