On 13/01/13 20:42, Charlie Brady wrote:
> 
> 
> I know from work I have done at Mitel that moving the code to a CentOS6 
> base is not a hugely difficult task.
> 
> I don't think there is an urgent need to do anything drastic. I think the 
> ball is largely in Filippo's court. Do they wish to inject direction, 
> energy and technological developments into this community, or do they wish 
> to supplant this community with one of their own?
> 
> In the meantime, we could look at their code, and decide whether there are 
> some improvements that they have made which could easily be incorporated 
> into, say, SME8.1.
> 

I think we would all be interested to hear Filippos comments on all
this. That may influence thinking all round.

If, as you say, moving to CentOS 6 is not too difficult and the
consensus is to push forward regardless, bearing in mind the limited
resources available, would it not make more sense to go directly to that
base rather than trying to make small tweaks to the current version,
which seems to have much of what people want at the minute ?

Unfortunately with so many distros on rapid schedules, lots of users
want latest and greatest. Though I don't completely subscribe to that
theory, it would seem that trying to at least keep vaguely up to date is
a good thing. It would undoubtedly save people starting to hack the base
more and more as time goes by - e.g. people wanting/needing PHP 5 on v7
( I was one who did)

CentOS 5 is EOL in March 2017. Even if work started NOW on v9/CentOS 6
bearing in mind the gestation period for v8, would it get out the door
by then ? And by which time CentOS 6 will be getting on with current EOL
in Nov 2020 (gawd that seems a long time away!)

On a side note, funny how after such a burst of activity on the Devs
list, nothing much comes up here :-) The silence is sadly deafening...
_______________________________________________
Discussion about project organisation and overall direction
To unsubscribe, e-mail [email protected]
Searchable archive at http://lists.contribs.org/mailman/public/discussion/

Reply via email to