eZ Community » Forums » General » Roadmap for version 4.2.1 ;)
expandshrink

Roadmap for version 4.2.1 ;)

Roadmap for version 4.2.1 ;)

Tuesday 02 March 2010 8:23:32 am - 17 replies

Hello guys,

I've been slightly disconnected from eZ affairs recently, so maybe I am missing or misunderstanding some approach change regarding the "heartbeat cycles" or company strategy or whatever - if so, please let me know.

It's been 5 months now since 4.2.0, which is a very stable release from my experience and we're very pleased with it. That's great. However, 4.2.1 doesn't seem to be anywhere near releasing. This provokes my two thoughts/questions:

  1. When will the 4.2.1 be released (if ever)?
  2. Could this situation be caused by the fact that eZ now strongly promotes and depends on the premium services, and so it's a bit against their interest to release bugfixes otherwise?

Cheers,
Piotrek

Modified on Tuesday 02 March 2010 8:24:02 am by Piotr Karaś

Tuesday 02 March 2010 9:35:19 am

Hi, there will be eZ Publish 4.3 release - March 30th, 2010.

greetz Andi

Tuesday 02 March 2010 9:51:59 am

Well, yeah, sure. But that's not exactly maintenance, is it? blunk.gif Emoticon 4.3 will introduce some significant improvements and changes, which means that:

  • It could bring new bugs around.
  • Clients will have to be faced with new functionalities, admin interface revolution etc.

And even if that could be considered a maintenance of sorts, do you think having them every 6 months is satisfactory?

Happy to learn other point of views.

Cheers,
Piotrek

Tuesday 02 March 2010 11:07:15 am

Hi Piotrek!

AFAIK there wil be no more maintainance-releases. This is off course to encourage users to choose Premium. The bugfixes will, however, be available via svn.

This, IMHO, is a good thing. I have no problem with ez earning money. On the other hand, I can still get the latest code from svn whenever I want.

Felix

Tuesday 02 March 2010 11:46:23 am

I have nothing against eZ earning money and the premium services do make the entire eZ offer a better solution rather than worse. But bugs are located, submitted and often fixed/discussed by the community members, too. Quality of eZ Publish is also partially owed to the community and open source model. I would say this is discouraging at least for some contributors...

A provocative question then would be: who is a community partner or a contributor? What's their/our role?

I think there is still room for business in a huge difference between automated maintenance, immediate updates etc. and a bugfix release every 2-3 months that requires an upgrade process, some additional effort etc. I also don't question the general strategy, just the scope - half a year without bugfix release (or maybe none at all) doesn't even sound good.

I am very curious of what's the official policy on this subject.

Modified on Tuesday 02 March 2010 11:46:54 am by Piotr Karaś

Tuesday 02 March 2010 3:35:51 pm

My 2 cents, if even that much value ;~}

Must agree with Felix. As long as everything is openly available in SVN, cannot see that eZ developers must share with community what they get paid to do.

Same with docs, if community wants better docs besides code, community can build it.

Core developers have plenty to do in their day jobs. It is on their nickel when they pop in to share knowledge. .

The goal of noobs should be to work their way up to the developers level via community participation and contributions. Sweat equity with some direction from above.

Like Piotrek, 879 posts, that is contributing back, whether or not we agree on fine details of this one subject. SVN works for me. There is an RSS feed to subscribe for bugs, to be sure do not get caught unawares between releases?

Thursday 04 March 2010 5:21:08 pm

Hi guys,

This topic ressembles another one, to which i replied. This should, i hope, help clarify things :

http://share.ez.no/forums/general...ntenance-releases-again#comment57481

Best Regards and thanks for this feedback !

Thursday 04 March 2010 7:07:39 pm

Hi all,

Regarding roadmap, please stay tuned, as announced but not yet done, we will update this very quickly.

Cheers,

Roland

Friday 05 March 2010 7:06:23 am

Hi guys,

Nicolas, thank you for pointing to that thread (I completely missed it) because it provides some interesting details and answers on the subject and I agree that it should have been communicated better (outside of the conference).

I feel partially relieved, and that is because of two promises:

  • There is some counterbalance to cutting the bugfix releases in form of a stronger QA
  • A package between the 6-monthly releases, should a major issue arise (now it's just curious what would be considered a major issue?)

Yes, I can see positive sides of the change and of the new approach, I just don't have that much faith in being able to produce a bug-free release, especially when new major, complex functionalities are introduced. I hope I am wrong about it.

Thanks for sharing your thoughts.

Piotrek

Friday 26 March 2010 7:12:51 am

So, back to the simple question: what's the policy on 4.2.1? It seems like almost all the issues have been resolved:
http://issues.ez.no/RoadMap.php?Id=1199&ProjectId=3

Will 4.2.1 ever be packaged or will it remain internal?

I would be very grateful for any response on this issue. I don't want to argue whether it is good or not, I think we just deserve to know. Thanks!

Friday 26 March 2010 8:15:31 am

Certainly with the recent security issues that have been discovered and fixed for 4.1 and 4.2 in mind, this is an important topic IMHO. Of course there have been released patches for them but strangely enough it doesn't seem like these issues were fixed in the svn repository (or not yet?).

Regardless of that, I will package a 4.2.1 community release myself if eZ doesn't, and make it publicly available. Stay tuned.

Modified on Friday 26 March 2010 8:18:13 am by Kristof Coomans

Friday 26 March 2010 12:40:22 pm

Will 4.2.1 ever be packaged or will it remain internal?

I would be very grateful for any response on this issue. I don't want to argue whether it is good or not, I think we just deserve to know. Thanks!

Hello Piotr !

As explained there , there will be no 4.2.1 package made. But 4.3 is ready soon, so moving to 4.3 is an option.

Cheers !

Modified on Friday 26 March 2010 12:41:31 pm by Nicolas Pastorino

Friday 26 March 2010 12:43:42 pm

Certainly with the recent security issues that have been discovered and fixed for 4.1 and 4.2 in mind, this is an important topic IMHO. Of course there have been released patches for them but strangely enough it doesn't seem like these issues were fixed in the svn repository (or not yet?).

Not yet, indeed. Please read the updated blog post, bringing all information you are asking for :
http://share.ez.no/blogs/ez/secur...ptly-patch-your-ez-publish-instances

Cheers,

Friday 26 March 2010 1:43:07 pm

Hello Piotr !

As explained there , there will be no 4.2.1 package made. But 4.3 is ready soon, so moving to 4.3 is an option.

Cheers !

Thank you, it wasn't crystal clear to me.

Unfortunately, no - 4.3 is not always an option, or at least not an easy one. 4.3 brings some significant changes, which means:

  • additional client training may be required
  • custom work (extensions, design, etc - 95% of what we do with eZ, no ezwebin-based sites) must be adopted and tested
  • catching new bugs is highly probable, so some time will be required to see if the new version is stable enough (since we won't have another "tricky" upgrade opportunity for another six months...)

But I think we've already covered this issue well enough. I was just hoping at least this one bugfix release will be packaged.

Piotrek

Friday 26 March 2010 2:42:39 pm

Piotr,

you have no obligation or reason to believe me here I guess, but as for version 4.2, ezp 4.3 has really been toroughly tested. Actually more than 4.2, since our QA processes have evolved a lot in between. This testing involves automatic tests (selenium + unit tests), manual testing by ourselves and an external team + various contributors.

It is quite safe to say it will be usable as a stable version, unlike indeed most .0 versions before 4.2.

Friday 26 March 2010 3:37:38 pm

Piotr,

you have no obligation or reason to believe me here I guess, but as for version 4.2, ezp 4.3 has really been toroughly tested. Actually more than 4.2, since our QA processes have evolved a lot in between. This testing involves automatic tests (selenium + unit tests), manual testing by ourselves and an external team + various contributors.

It is quite safe to say it will be usable as a stable version, unlike indeed most .0 versions before 4.2.

Hello Bertrand,

I have no reason not to believe you. As I already mentioned, 4.2 had already proven itself to be a great stable release and I really appreciate it. But things happen blunk.gif Emoticon

We'll see how things go blunk.gif Emoticon

Saturday 27 March 2010 9:03:26 pm

I am happy to announce you I've been preparing a first test build of eZ Publish 4.2.1 community release. Feel free to test it and let me know if any issues occur.

The test build is available from http://code.google.com/p/ezpublish-community/.

Sunday 28 March 2010 7:28:08 pm

I am happy to announce you I've been preparing a first test build of eZ Publish 4.2.1 community release. Feel free to test it and let me know if any issues occur.

The test build is available from http://code.google.com/p/ezpublish-community/.

Great news and great initiative! We'll be testing it this week!

Cheers,
Piotrek

expandshrink

You must be logged in to post messages in this topic!

36 542 Users on board!

Forums menu

Proudly Developed with from