Skip to content
This repository has been archived by the owner on Jul 22, 2022. It is now read-only.

tree-browser and resource-rest stable ETA #373

Closed
soullivaneuh opened this issue May 10, 2016 · 8 comments
Closed

tree-browser and resource-rest stable ETA #373

soullivaneuh opened this issue May 10, 2016 · 8 comments
Assignees
Labels

Comments

@soullivaneuh
Copy link
Member

Have you an ETA for symfony-cmf/tree-browser-bundle and symfony-cmf/resource-rest-bundle stable release?

I would like to push a new major for sonata-admin 3.0 support and deprecate the 1.x one but those bundle are already required with unstables versions.

Thanks.

cc dbu @lsmith77 @dantleech @sjopet @rmsint

@dbu
Copy link
Contributor

dbu commented May 11, 2016

@wouterj is most active with the tree browser. can you please check the milestones and make sure the relevant issues that need to be done are there? and maybe label things as nicetohave that we could also do without?

@wouterj
Copy link
Contributor

wouterj commented May 11, 2016

The biggest "problem" is Puli. It has to be released stable in order to mark ResourceRestbundle stable.

@wouterj
Copy link
Contributor

wouterj commented May 11, 2016

ping @webmozart, what are the plans to release Puli 1.0 stable?

@iBasit
Copy link

iBasit commented May 31, 2016

+1

it will really help to get basic stable versions for all the chained bundles

@soullivaneuh
Copy link
Member Author

I will start dev-kit integration.

1.x will be the stable branch for now, but not compatible with the new ecosystem.

When all dependencies will be stable on master, we will release a 2.x tag and deprecate the 1.x.

@dbu
Copy link
Contributor

dbu commented Jun 5, 2016 via email

@wouterj
Copy link
Contributor

wouterj commented Jan 8, 2017

Fyi, we're now about to release RC's of CMF 2.0. Expect a stable release this month.

@stale
Copy link

stale bot commented Jan 30, 2020

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the wontfix label Jan 30, 2020
@SonataCI SonataCI removed the wontfix label Jan 30, 2020
@core23 core23 added the stale label Feb 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants