Deadlines for Platform 11.3 and Joomla 2.5?

[Hannes Papenberg]

Hi folks,
I wanted to ask what the deadlines for the platform 11.3 and Joomla 2.5
are and which platform version is going to be included in 2.5.
Basically, there are a number of pull requests open on the platform that
would have great benefits for Joomla and I have some code that I'd like
to contribute myself and need to finish. It would be good to know how
much time I have left for preparing that code.

Hannes

[Andrew Eddie]

Hi Hannes

The plan is for 11.3 to be tagged this month sometime. I believe the
CMS will then merge as soon as possible after that, but best to ask on
the CMS list about that. I would think that J2.5 will run on 11.4 so
in terms of stuff you want to through in, but keep in mind that
December is really busy time for everyone so I'd be aiming to get your
work finished by early November to allow enough time for processing.

Regarding the pull requests, Louis and I tried to put a dent in them
yesterday but we came across more and more instability in the unit
tests as we started merging. We changed gears and started to clean
them up a bit and the first phase of that
https://github.com/joomla/joomla-platform/pull/428

That took us the afternoon. Our aim is to address the rest of the
remaining pulls (one way or the other) while I'm in San Jose in
between ZendCon.

Regards,
Andrew Eddie
http://learn.theartofjoomla.com - training videos for Joomla 1.7 developers

> --
> You received this message because you are subscribed to the Google Groups "Joomla! Framework Development" group.
> To post to this group, send an email to joomla-dev...@googlegroups.com.
> To unsubscribe from this group, send email to joomla-dev-frame...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/joomla-dev-framework?hl=en-GB.
>
>

[Mark Dexter]

The general plan for 2.5 is as follows:

Nov 10: release 1.7.x (probably 1.7.3) -- last planned maintenance release for 1.7
Nov 11: start merging in any new features. Note that features should be tested, including all system tests passing and reasonable documentation available.
Dec 10: End new feature merging for 2.5.
Dec 15: 2.5 beta released
Jan 10, 2012: 2.5.0 released

I would like to emphasize that the top priorities for 2.5 in my opinion are stability and backward compatibility. It is always great to get new features in, but only if they don't cause problems for existing users. Keep in mind that all 1.7.x users must upgrade to 2.5, so we need to make this as painless as possible for 1.7 users.

For version 3.0, we will be able to be more ambitious, since users won't have to upgrade production sites to 3.0.

The PLT is going to be discussing the detailed process for approving and merging changes for 2.5 in the next couple of weeks. In the meantime, the process for submitting enhancements is the same as it has been:

1. Make a branch or patch.
2. Create an issue in the CMS Feature Tracker (http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8549).
3. Make sure the system tests pass and that there is good documentation for how the feature works and what it does.
4. Get people to test and comment on the feature.
5. When a feature is ready to be reviewed for merging, change the status to Ready for review.

Thanks. Mark

[elin]

Andrew does that mean that 11.4 will be tagged after the feature merges are done around December 10 but before a 2.5 beta? 

I'm asking as a practical matter since I think it is preferable for the CMS to have as close to a tagged platform as possible in 2.5 and it is almost inevitable that testing of feature patches will uncover platform issues.

Elin

[Hannes Papenberg]

Hi Mark,
regarding the process for approval of changes: Please take a look at the
Feature Patch Tracker. I opened an issue there, but to be honest, I'm
not really convinced that anybody is looking into this tracker. Most of
the issues have been opened and at least feel like they were never
touched again after that. There is a lot more response on this
mailinglist and in the pull requests on github than on the feature
tracker...

Hannes

Am 16.10.2011 17:16, schrieb Mark Dexter:
> The general plan for 2.5 is as follows:
>
> Nov 10: release 1.7.x (probably 1.7.3) -- last planned maintenance
> release for 1.7
> Nov 11: start merging in any new features. Note that features should
> be tested, including all system tests passing and reasonable
> documentation available.
> Dec 10: End new feature merging for 2.5.
> Dec 15: 2.5 beta released
> Jan 10, 2012: 2.5.0 released
>
> I would like to emphasize that the top priorities for 2.5 in my
> opinion are stability and backward compatibility. It is always great
> to get new features in, but only if they don't cause problems for

> existing users. Keep in mind that /all 1.7.x users must upgrade to
> 2.5/, so we need to make this as painless as possible for 1.7 users.

>
> For version 3.0, we will be able to be more ambitious, since users
> won't have to upgrade production sites to 3.0.
>
> The PLT is going to be discussing the detailed process for approving
> and merging changes for 2.5 in the next couple of weeks. In the
> meantime, the process for submitting enhancements is the same as it
> has been:
>
> 1. Make a branch or patch.
> 2. Create an issue in the CMS Feature Tracker
> (http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8549

> <http://joomlacode.org/gf/project/joomla/tracker/?action=TrackerItemBrowse&tracker_id=8549>).

> <hack...@googlemail.com <mailto:hack...@googlemail.com>> wrote:
> > Hi folks,
> > I wanted to ask what the deadlines for the platform 11.3 and
> Joomla 2.5
> > are and which platform version is going to be included in 2.5.
> > Basically, there are a number of pull requests open on the
> platform that
> > would have great benefits for Joomla and I have some code that
> I'd like
> > to contribute myself and need to finish. It would be good to
> know how
> > much time I have left for preparing that code.
> >
> > Hannes
> >
> > --
> > You received this message because you are subscribed to the
> Google Groups "Joomla! Framework Development" group.
> > To post to this group, send an email to
> joomla-dev...@googlegroups.com

> <mailto:joomla-dev...@googlegroups.com>.

> > To unsubscribe from this group, send email to
> joomla-dev-frame...@googlegroups.com

> <mailto:joomla-dev-framework%2Bunsu...@googlegroups.com>.

> > For more options, visit this group at
> http://groups.google.com/group/joomla-dev-framework?hl=en-GB.
> >
> >
>
> --
> You received this message because you are subscribed to the Google
> Groups "Joomla! Framework Development" group.
> To post to this group, send an email to
> joomla-dev...@googlegroups.com

> <mailto:joomla-dev...@googlegroups.com>.

> To unsubscribe from this group, send email to
> joomla-dev-frame...@googlegroups.com

> <mailto:joomla-dev-framework%2Bunsu...@googlegroups.com>.

[Andrew Eddie]

Hannes, you need to raise those things on the CMS list, and then keep
trying and keep trying. Unfortunately you sort of have to be your own
marketing manager and hope that some other developers are interested
in your feature as well, remembering you can't force them to be. It's
frustrating, I know, but that's the price we pay for community driven
development.

On that particular issue, we'll get to looking at the pull request,
but to be honest I really want to see buy-in from the CMS as well and
testing from their end first to make sure nothing breaks (which is a
very high risk when anyone touches the router).

Regards,
Andrew Eddie
http://learn.theartofjoomla.com - training videos for Joomla 1.7 developers

[Mark Dexter]

We need a place to keep track of work on an issue. It's fine to have discussions on the list and so on, but at the end of the day I think it is easier if we have one place to look for information about a feature. I'm open to other options, but for now I think the Feature Tracker is the only one we have. Mark

[Hannes Papenberg]

Andrew, the point was exactly, that all relevant communication happens
through the mailinglist and that so far I haven't seen any activity on
the tracker. To me, Marks instructions sounded like "This is the
official and only way and only this way will guarantee you at least some
attention by us."

Regarding my particular issue: I wouldn't want it approved by the
framework if the CMS doesn't tag along either. It is especially
important for me, that the CMS adopts this and as soon as I find some
more time, I will invest that into fixing the code and proofing it.

Hannes

[Hannes Papenberg]

While I'm still a noob regarding GIT, github has proven to be invaluable
for this kind of thing, especially since it really keeps track of
everything. I know that the CMS wont switch today or tomorrow to github.
The tracker however does not seem like the best place. I don't know how
current the repo on github is, but if it is kept in sync with SVN, new
features might as well go in there and bugfixes can still be done in
subversion, gradually moving over.

Hannes

> <mailto:hack...@googlemail.com

> <mailto:hack...@googlemail.com>>> wrote:
> > > Hi folks,
> > > I wanted to ask what the deadlines for the platform 11.3 and
> > Joomla 2.5
> > > are and which platform version is going to be included in 2.5.
> > > Basically, there are a number of pull requests open on the
> > platform that
> > > would have great benefits for Joomla and I have some code that
> > I'd like
> > > to contribute myself and need to finish. It would be good to
> > know how
> > > much time I have left for preparing that code.
> > >
> > > Hannes
> > >
> > > --
> > > You received this message because you are subscribed to the
> > Google Groups "Joomla! Framework Development" group.
> > > To post to this group, send an email to
> > joomla-dev...@googlegroups.com
> <mailto:joomla-dev...@googlegroups.com>

> > <mailto:joomla-dev...@googlegroups.com

> <mailto:joomla-dev...@googlegroups.com>>.
> > > To unsubscribe from this group, send email to
> > joomla-dev-frame...@googlegroups.com
> <mailto:joomla-dev-framework%2Bunsu...@googlegroups.com>

> > <mailto:joomla-dev-framework%2Bunsu...@googlegroups.com
> <mailto:joomla-dev-framework%252Buns...@googlegroups.com>>.

> > > For more options, visit this group at
> > http://groups.google.com/group/joomla-dev-framework?hl=en-GB.
> > >
> > >
> >
> > --
> > You received this message because you are subscribed to the
> Google
> > Groups "Joomla! Framework Development" group.
> > To post to this group, send an email to
> > joomla-dev...@googlegroups.com
> <mailto:joomla-dev...@googlegroups.com>

> > <mailto:joomla-dev...@googlegroups.com

> <mailto:joomla-dev...@googlegroups.com>>.
> > To unsubscribe from this group, send email to
> > joomla-dev-frame...@googlegroups.com
> <mailto:joomla-dev-framework%2Bunsu...@googlegroups.com>

> > <mailto:joomla-dev-framework%2Bunsu...@googlegroups.com
> <mailto:joomla-dev-framework%252Buns...@googlegroups.com>>.

[Andrew Eddie]

Yep, that's fine for communication (centrally). My point was just
posting it on the tracker is maybe not going to give you the exposure
you want for other people to catch the vision, or whatever (responding
to your comment that nobody is looking at it). In other words, use
the CMS list, Twitter, Google+, Facebook, et al to spread the love.
Then use the tracker as the point of truth, as Mark suggests.

If, on the other hand, you mean that the PLT is driving your feature
through the system, then I'd have to say that's not the way the system
was designed.

Hope that helps.

Regards,
Andrew Eddie
http://learn.theartofjoomla.com - training videos for Joomla 1.7 developers

[Mark Dexter]

Hi Hannes. I agree with you (and Andrew) that the tracker is not the only or maybe even the best place to discuss the new features. So I encourage you to discuss features anywhere that makes sense. However, as far as documenting what has been done on a feature, in terms of testing, code, docs, and such, please use the tracker. For example, if there are some threads where the feature was discussed, you could just link those threads in the tracker.

We have to have one list of new features to be tested and evaluated. Until we can come up with a better alternative, the Feature Tracker is that one list. But it should not inhibit discussion in other places.

Hope that helps. Mark

[elin]

You might consider is that if you think no one is looking at issues in the feature tracker is that you could look at and test other people's work and provide them constructive feed back. " It's all about giving first and getting later.  Be the change you seek. 

Personally, I look through  the features at least weekly and try out things I find interesting, but for my own I always am pestering people to test, and that's how it is when it's your itch and not theirs. Of course response on the mailing list is always greater, it doesn't involve actual work. 

Elin