Features for 0.8.0

Added by Ignacio Carrera over 9 years ago

I've been watching the Roadmap for 0.8.0 ever since #1110 has been marked as resolved, as that is something I really need.

Since then, I've seen the list grow with what seems to be new features or low-priority bug fixes1. The main issue holding it back seems to be #337, and I can't see what has been done for it or what's left. Furthermore, I see other issues without commits or even a single comment blocking the release.

So, I get the sense that #337 is not gaining much traction, but only holding back a nice release. Could we postpone it for 0.8.1?

The alternative is to deploy trunk, but having many changes, that's not comfortable.

Not trying to start a flamewar, as I really appreciate the effort of all those who contributed (which I still didn't). Redmine rocks.

Perhaps Jean is waiting to acumulate more features to justify a minor version change..

Thank you,

nacho

[1] Someone may think they aren't "low priority", that can get subjective, but my point is that they can wait for 0.8.1.

Replies (4)

RE: Features for 0.8.0 - Added by John Reynolds over 9 years ago

I'd like to add my support for an earlier release and some issues bumping to 8.1.
I've been seeing the same thing as far as features just getting added on more and more in the same release schedule. There are a few things that would really be nice to have sooner than later.

Most appreciated!

Cheers,

John

RE: Features for 0.8.0 - Added by Eric Davis over 9 years ago

So, I get the sense that #337 is not gaining much traction, but only holding back a nice release. Could we postpone it for 0.8.1?

I don't know if that would be a 0.8.x release or 0.9.x release. Private tickets will probably require a database change, thus it shouldn't go into a minor release.

The alternative is to deploy trunk, but having many changes, that's not comfortable.

Depending on your current version, the migration could be difficult. But once you are on trunk, the incremental upgrades are really easy and stable. I've been running trunk since 0.6.

As far as the 0.8 blockers, here is my opinion. I'm going off the major issues planned for 0.8 and not the "related issues" list (since anyone and everyone is marking issues as 0.8) this is what I see:

Ticket submission via email (#1110)

Basic support for this is done and I've used it personally in production. Some more keywords can be added but it shouldn't block 0.8.

Private tickets (#337)

You are correct with saying this is kinda halted. Last update to the issue was 56 days ago. Personally, I might use the issue but I don't care if it's in 0.8 or a later release.

Cross-project search engine

I believe this is working in trunk. Looks like issue #791

User groups

It looks like this was developed in the work/groups branch. I'll have to check to the history to see if it has been merged into trunk yet.

http://www.redmine.org/boards/1/topics/show/707

Wiki page protection

I've seen this in trunk.

Wiki page hierarchy (#528)

Appears this is in trunk already.

Textile caching

I don't remember seeing any activity on this. I for one would love to have some caching, my Redmine has been running a bit slow recently.

Diff viewer for attachments

I've seen this on the patch and diff files.

Others

A major feature I'd like to see getting into 0.8 is the new plugin API and generator. It's currently being worked on in a branch and should be merged into trunk soon.

Summary

So in summary; some of the major features are already in trunk, some are in branches and need merged, and some haven't had any work on. Jean-Philippe, what are your thoughts?

Eric

RE: Features for 0.8.0 - Added by Ignacio Carrera over 9 years ago

Thanks for the panorama. The Related Issues list blinded me into thinking that it was worse that it really is (it doesn't help that those get to influence the progress bar :( ).

My main focus is #1110 as that's quite stable and is a big feature (it would alone merit the 0.8 version name).

Great work,

nachokb

RE: Features for 0.8.0 - Added by Milton Taylor over 9 years ago

It is frustrating - and I don't mean that as a criticism - to see a feature such as #337 (private issues) and #1018 (user groups) still not yet implemented. With the latter one, it seems to be largely complete, but "stuck" in a working branch...what's holding this back from being rolled into trunk? It would be nice to get some sense of the sequence on which the unimplemented features would be worked on.

(1-4/4)