In my opinion a LTS lower then 3 years might be a deal for more enterprise
customers which would want to use Symfony2 for a backbone/backend application
(I'm not talking here about a simple marketing application).
I live more in the enterprise consulting sphere (SAP business consulting) and
n
On Wed, Sep 19, 2012 at 11:19:37PM +0200, Christophe COEVOET wrote:
> composer supports 4 level of numbers for the version number.
>
> But anyway, if people are using composer, update from a maintenance
> release to the next one is simply a matter of running "composer
> update" without changing a
On 9/19/12 11:40 PM, Florin Patan wrote:
I was thinking to upgrade to a .a revision level rather that release a
maintenance version sooner that planned/wanted.
Think for example if something appears in the YAML component and needs
to be patched asap but at the same time you want to wait for a ce
I was thinking to upgrade to a .a revision level rather that release a
maintenance version sooner that planned/wanted.
Think for example if something appears in the YAML component and needs to
be patched asap but at the same time you want to wait for a certain event
to happen before releasing
Le 19/09/2012 23:09, Florin Patan a écrit :
What about the release of separate components / bundles shipped with
Symfony Standard? How would that be handled?
Currently if a component needs an upgrade, say for a security patch,
then a new release needs to be done, if I'm right, which basically
What about the release of separate components / bundles shipped with
Symfony Standard? How would that be handled?
Currently if a component needs an upgrade, say for a security patch, then a
new release needs to be done, if I'm right, which basically goes against
the idea of having the framework
Le 17/09/2012 18:29, jB!nfo a écrit :
+2 for the proposal;
Yaml component is also used by many third-party code, i think it will
be good to place it with the low level components;
I also find the idea of Lukas Smith is good, release manager profile :)
finally, is there is a plane for transl
+2 for the proposal;
Yaml component is also used by many third-party code, i think it will be
good to place it with the low level components;
I also find the idea of Lukas Smith is good, release manager profile :)
finally, is there is a plane for translating the documentation ?
--
If you wan
On 9/17/12 12:39 PM, Sven Paulus wrote:
Hi Fabien,
thank you for the symfony release roadmap!
I have one little question concerning non LTS releases:
On Monday, September 17, 2012 7:01:18 AM UTC+2, Fabien Potencier wrote:
Maintenance
---
After Symfony 2.3, non LTS release
Hi Fabien,
thank you for the symfony release roadmap!
I have one little question concerning non LTS releases:
On Monday, September 17, 2012 7:01:18 AM UTC+2, Fabien Potencier wrote:
> Maintenance
> ---
>
> After Symfony 2.3, non LTS releases will be maintained for 8 months to
> give
On 9/17/12 8:06 AM, David R wrote:
Sounds like a healthy release plan.
Two questions, though:
1) for clarification: It looks like the versioning scheme matches the
"Semantic Versioning" model (http://semver.org). Can you explicitly
confirm this? If not, how do you intend to differ?
Yes, I con
Like Javier said, one of the problems that I see would be people needing to
make the changes for the documentation/upgrade files even if their PR might
not be accepted in the end.
Maybe having some sort of two steps process where first a PR is accepted
for merge then the rest of the things are d
Sounds like a healthy release plan.
Two questions, though:
1) for clarification: It looks like the versioning scheme matches the
"Semantic Versioning" model (http://semver.org). Can you explicitly
confirm this? If not, how do you intend to differ?
2) Will there be a roadmap outlining the planned
13 matches
Mail list logo
