Versions vs Milestones

Added by Maxim Krušina almost 10 years ago

From my point of view there is better to use Milestones than Versions. Why? We're using Redmine for lot of activities, not only for SW development. When we're using Redmine for things like DTP and advertising management, basicaly any non-sw projects, there are milestones rather than versions. I think that version is hust one kind of milestone. Or, there can be both milestones and versions, like in Trac. What others think?

Replies (71)

RE: Versions vs Milestones - Added by Holger Just almost 8 years ago

Peter Chester wrote:

What about baking some hooks into the core and then making a plugin that works with those hooks?

Let's put it that way:
The code written until now works as a plugin. I'm going to try to keep it that way, but will not promise anything. It might become a real mess when I start to refactor versions and move some of its behaviour to the new milestones.

On the other hand, a larger plugin and a few callbacks / refectorings might be easier to get approved :)

RE: Versions vs Milestones - Added by Eric Voisard almost 8 years ago

@Holger:

Sorry...

Hey, you don't have to be sorry, you're working for the community for free :-)
I must say that about everyday, I check if there's something new in this thread. I thought you were busy.

@Maxim:
You should re-read the thread because there have been new things and new ideas since two years. Holger has very interesting propositions :-)

Eric

RE: Versions vs Milestones - Added by Pieter Smith over 7 years ago

Is somebody still working on this? It's one of the sore points when trac users migrate to Redmine.

RE: Versions vs Milestones - Added by Shane Pearlman over 7 years ago

We will be building our take on milestones quite soon. Our budget plugin is in progress (we got the alpha from eric to play with last week). Milestones don't come into play until release 3 though if I remember, so probably october/nov.

RE: Versions vs Milestones - Added by Pieter Smith over 7 years ago

Thanks for the update. Please be so kind as to post further updated here or provide a forum where progress can be tracked.

RE: Versions vs Milestones - Added by Shane Pearlman over 7 years ago

@Pieter - just to be clear - this is not a core effort but a private plugin we are funding for ourselves. We asked the community to help us fund it and no one stepped up to bat. I might be down to share the code some day, but we have no accountability to the community what so ever on our effort. =)

RE: Versions vs Milestones - Added by Holger Winkelmann over 7 years ago

Hi, I tried to get in contact with the Community regarding this Feature. I mentioned this ön irc and spoke to Otter People in the Community. There is also the Option to Co fund this work. But it is Not easy to to spend 'some Budget As it is Not easy to speak to somebody if it gets commercial. It's even harder if it becomes a shared budget. Can somebody advise me what's the best way to raise funding fir a enhancement? And can someone explain how the dev process works

Thanks, Holger

RE: Versions vs Milestones - Added by Pieter Smith over 7 years ago

@Shane - I am well aware of this: Thank you for putting in the effort! I apologise if I gave another impression. My ruby skills are shoddy at best (improving though), but I am quite willing to contribute in any way you deem helpful (testing for example).

RE: Versions vs Milestones - Added by Michael Aye over 7 years ago

Actually, I speak no Ruby whatsover, but was able to change Versions to Milestones just by using Search/Replace in the redmine folders.
Try it out with a Bitnami stack, if you are scared to do it in running system.
Works fine here, just to let you know about simple hack.

Best regards,
Michael

RE: Versions vs Milestones - Added by Jan Wedekind over 7 years ago

Michael Aye wrote:

Actually, I speak no Ruby whatsover, but was able to change Versions to Milestones just by using Search/Replace in the redmine folders.

I just tried doing the same but I guess that just replacing the names in the locale "en.yml" is not enough? Could you be more specific where you have actually changed that?

RE: Versions vs Milestones - Added by Michael Aye over 7 years ago

Jan Wedekind wrote:

Michael Aye wrote:

Actually, I speak no Ruby whatsover, but was able to change Versions to Milestones just by using Search/Replace in the redmine folders.

I just tried doing the same but I guess that just replacing the names in the locale "en.yml" is not enough? Could you be more specific where you have actually changed that?

Unfortunately not, because it's too long ago.
'grep -R Versions *' in the redmine folder is your friend. ;)

RE: Versions vs Milestones - Added by Pieter Smith over 7 years ago

Michael Aye wrote:

Actually, I speak no Ruby whatsover, but was able to change Versions to Milestones just by using Search/Replace in the redmine folders.
Try it out with a Bitnami stack, if you are scared to do it in running system.
Works fine here, just to let you know about simple hack.

Best regards,
Michael

If you were to follow the discussion, you will realise that Versions and a Milestones differ by more than just the name. Refer to comments following this one for the requirements and structure. A simple search and replace will not address the issue. Holger and his merry band of brilliant hackers are busy integrating the requirements as part of a plugin.

RE: Versions vs Milestones - Added by Emilio González Montaña over 7 years ago

Please, consider to use my Redmine plugin Advanced roadmap: http://ociotec.com/redmine/projects/advanced-roadmap (take a look at the wiki).

With this plugin you can define milestones, and attach them versions, from the project or others. A total is presented, also additional information is presented.

Give it a chance, and tell me later your opinion, this is an screenshot:

RE: Versions vs Milestones - Added by Michael Aye over 7 years ago

Pieter Smith wrote:

Michael Aye wrote:

Actually, I speak no Ruby whatsover, but was able to change Versions to Milestones just by using Search/Replace in the redmine folders.
Try it out with a Bitnami stack, if you are scared to do it in running system.
Works fine here, just to let you know about simple hack.

Best regards,
Michael

If you were to follow the discussion, you will realise that Versions and a Milestones differ by more than just the name. Refer to comments following this one for the requirements and structure. A simple search and replace will not address the issue. Holger and his merry band of brilliant hackers are busy integrating the requirements as part of a plugin.

If someone expects different functionality, yes.
If someone just doesn't want the current functionality to be displayed as Versions and preferred it to be called Milestones, because it otherwise confuses people outside the world of software development, a simple search and replace does solve this particular issue.
As it works fine here, I thought I share this little hack for the people in the same boat just don't liking the word Versions, but I'm sorry, if it leads to confusion in the matters.

RE: Versions vs Milestones - Added by Pieter Smith over 7 years ago

Changing the label field_version in ./config/locales/en.yml is the easy (and appropriate) way of doing this. :)
The label is however used for a number of things that you may NOT want changed from Version to Milestone. :(

You may have to add a new field_milestone label and patch only those instances of field_version that you want changed. Slightly more work, but not rocket-science. Keep in mind that you will have to merge / maintain such changes whenever you upgrade.

RE: Versions vs Milestones - Added by Jan Wedekind over 7 years ago

If you were to follow the discussion, you will realise that Versions and a Milestones differ by more than just the name. Refer to comments following this one for the requirements and structure. A simple search and replace will not address the issue. Holger and his merry band of brilliant hackers are busy integrating the requirements as part of a plugin.

If someone expects different functionality, yes.
If someone just doesn't want the current functionality to be displayed as Versions and preferred it to be called Milestones, because it otherwise confuses people outside the world of software development, a simple search and replace does solve this particular issue.
As it works fine here, I thought I share this little hack for the people in the same boat just don't liking the word Versions, but I'm sorry, if it leads to confusion in the matters.

Thanks for all the tips. I actually saw the discussions on the difference of milestones and versions and I agree that it needs some refinement or overhaul in the future. But what I needed right now was what Michael did - just change the name for now, because we actually use versions as milestones and people from outside of SW development just get confused.

Thanks also to Emilio for the plugin tip! We've really just started using it and at the moment I try to work with the trunk as it is. But I will definitely give it a try once I know my way around the code a bit more! But maybe until then a new RM release will have changed that behavior anyway.

Great to see so many people are following up here, thanks a million.

RE: Versions vs Milestones - Added by Michael Aye over 7 years ago

Jan Wedekind wrote:

Great to see so many people are following up here, thanks a million.

It's obviously a topic close at many people's hearts. ;)

RE: Versions vs Milestones - Added by Pieter Smith over 7 years ago

Holger Winkelmann wrote:

Hi, I tried to get in contact with the Community regarding this Feature. I mentioned this ön irc and spoke to Otter People in the Community. There is also the Option to Co fund this work. But it is Not easy to to spend 'some Budget As it is Not easy to speak to somebody if it gets commercial. It's even harder if it becomes a shared budget. Can somebody advise me what's the best way to raise funding fir a enhancement? And can someone explain how the dev process works

Thanks, Holger

Hi Holger,

We are considering funding or contributing financially to this effort. Have you managed to get any advice on how this could go?

RE: Versions vs Milestones - Added by snow windwaves over 7 years ago

I am interested in this plugin as well as I am in the construction business not software development

RE: Versions vs Milestones - Added by Joshua DeClercq almost 5 years ago

I've outlined a drastically different solution to this subject over at issue #13387. This conversation was extensive, but it's very old and none of the requests or plugins really resolved the many possible use cases. Instead of building a system on top of versions, I'm taking the approach of expanding the existing functionality, adopting the issue relations model to connect versions to each other in all kinds of ways, and increasing the functionality of the existing custom fields that can be added to versions (but don't really do anything right now).

1 2 3 (51-71/71)