symfonyのリリースなどに関する議論

Jonathan H. Wage @jwage

Damn, this blog post stings a little bit... http://bit.ly/def2Jc

Peter Bowyer @peterbowyer

@jwage He has got valid points, but seems to have one tone of injured righteousness for all his posts :)

alcaeus @alcaeus

@n1k0 Seriously? Just the "#Symfony 1.0 is not supported anymore, therefor they suck" argument makes me want to throw up //ping @jwage

@n1k0@mamot.fr @n1k0

@alcaeus I was more thinking of choice between 1.4 and 2.0, very tricky to do atm #symfony

alcaeus @alcaeus

@n1k0 Yes, that is a valid point. Still, the blog post raises too much FUD IMO. #symfony

Jonathan H. Wage @jwage

@peterbowyer @n1k0 I don't think his points are valid. We have problems but the cause is not simply because things are ignored in spite.

@n1k0@mamot.fr @n1k0

@jwage sure lot af FUD there, but lot of clients of mine having to make a choice between 1.x and 2 are totally lost

Jonathan H. Wage @jwage

@n1k0 I don't know how to reply to that. I don't see how we could do anything different to change that.

@n1k0@mamot.fr @n1k0

@jwage I mean, for a lot of people 2012 is too near from now to start with 1.4, while 2 is not stable enough yet :/

@lsmith@mastodon.green (he/him) @lsmith

@n1k0 well thats the nature of the time between the announcement of BC breaking new version and its arrival in a mature version /cc @jwage

PierreJoye @PierreJoye

@n1k0 time to explain your clients the idea behind sw lifecycle and release mgt? :) /cc @jwage

Dennis Benkert @denderello

@n1k0 What will stop #symfony 1.4 working as soon as #symfony2 is released? For me it's ok to start with a 1.x project right now.

Jonathan H. Wage @jwage

@n1k0 We have a very small group of people actually working on symfony and we're stretched super thin already. Where is all the help? OSS

Jonathan H. Wage @jwage

@n1k0 Sure, ok we'll away the community initiative. Nothing is stopping someone from grabbing the bull by the horn and making it happen.

@n1k0@mamot.fr @n1k0

@jwage same here, lot of clients asks if they'll have to pay support for 1.4 support after its EOL, and I fear answering "probably" :/

@n1k0@mamot.fr @n1k0

@jwage if you want one single easy tip, moving 1.x dev to smthg like git(hub) would probably help a lot its community-driven maintenance

@lsmith@mastodon.green (he/him) @lsmith

@n1k0 #symfony 1.4 is a ggood today, people seem to want 1.5 for the sake of it, are there actually things on the table that require a 1.5?

marc_hugon @marc_hugon

@n1k0 are you sure that your clients really "need" sf2? Do you think they'll discover new bugs in 2-3 years in the framework? I don't ;)

Jonathan H. Wage @jwage

@n1k0 Disagree, someone still has to manage it, apply patches, decide the ramifications of a patch. Revert a patch when it breaks BC.

Jonathan H. Wage @jwage

@n1k0 It would "help" but we still need someone to manage, if one of us then it takes away from the forward progress we're making elsewhere.

Jonathan H. Wage @jwage

@n1k0 But yes, we need to get off svn and trac completely. Something that is in the works. It just can't come fast enough.

@n1k0@mamot.fr @n1k0

@marc_hugon problem is the lot of hype created around sf2, and paradoxal marketing messages ;)

marc_hugon @marc_hugon

@n1k0 I know about the hype, but the hype isn't pragmatic ;) If your client can wait for sf2 just for the hype, let him wait...

@n1k0@mamot.fr @n1k0

@jwage yeah I know what you're talking about, remember? ;) how about asking officially for such hands?

Peter Bowyer @peterbowyer

@jwage Today I ran into a 2yr old sf bug thats open in trac. I can't fix (requires stack/internals knowledge), but it shows the problm @n1k0