Skip to content
This repository has been archived by the owner on Jan 1, 2020. It is now read-only.

Tag a new release #51

Closed
flack opened this issue Feb 15, 2013 · 8 comments
Closed

Tag a new release #51

flack opened this issue Feb 15, 2013 · 8 comments

Comments

@flack
Copy link
Collaborator

flack commented Feb 15, 2013

The 0.8.0 release is already six months old and there have been quite a few changes since, so I guess it would be a good time to start thinking about a new release.

This ticket is basically a request for comments from various stakeholders, @dbu, @adou600 and anyone else who might be interested: In your opinion, which tickets should be addressed before a new release, and how do we want to call it, 0.8.1 or 0.9.0?

@dbu
Copy link
Collaborator

dbu commented Feb 16, 2013

Makes sense and be very useful for us. Lets find a solution for the specialized mappers first, if possible. 0.9 would indicate minor bc breaks. Do we have some?

----- Reply message -----
Von: "flack" [email protected]
An: "flack/createphp" [email protected]
Cc: "David Buchmann" [email protected]
Betreff: [createphp] Tag a new release (#51)
Datum: Fr., Feb. 15, 2013 18:46
The 0.8.0 release is already six months old and there have been quite a few changes since, so I guess it would be a good time to start thinking about a new release.

This ticket is basically a request for comments from various stakeholders, @dbu, @adou600 and anyone else who might be interested: In your opinion, which tickets should be addressed before a new release, and how do we want to call it, 0.8.1 or 0.9.0?

Reply to this email directly or view it on GitHub.

@flack
Copy link
Collaborator Author

flack commented Feb 16, 2013

Well, off the top of my head I remember that we changed the RdfMapper interface slightly two months ago (store() takes entity instead of object), and we changed the configuration format in December (nodeType, childtypes etc.). So for 0.8 users, some manual adjustments will be required when updating.

But yes, let's solve the multiple mapper question (#48) before releasing anything, I guess that shouldn't be too difficult.

@dbu
Copy link
Collaborator

dbu commented Feb 16, 2013

alright, then we should call it 0.9.0. i wil look into #48 on monday

@dbu
Copy link
Collaborator

dbu commented Oct 2, 2013

as #48 did not happen and won't happen very soon, i propose that we up the version on this bundle. packagist seems to not even see the 0.8.0 release...

@flack would be great if you could add such a tag this week. we are about to release 1.0 of the symfony cmf and having the CmfCreateBundle depend on a known release would be very useful.

@flack
Copy link
Collaborator Author

flack commented Oct 3, 2013

@dbu I have some dependent code to review first, but that schouldn't take too long I think, so a week seems realistic. I'll keep #48 open for reference for now (an implementation basically would be along the lines of #48 (comment), so there won't be a BC break involved, and it can be implemented whenever the need arises)

@dbu
Copy link
Collaborator

dbu commented Oct 8, 2013

@flack would be great if you could tag tonight. at least on our side, we do not need any new features right now, just a tag that we can depend on when we release the CmfCreateBundle...

@flack
Copy link
Collaborator Author

flack commented Oct 8, 2013

@dbu Done. Good luck with your release!

@flack flack closed this as completed Oct 8, 2013
@dbu
Copy link
Collaborator

dbu commented Oct 9, 2013

thanks a lot!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants