Use github INFRA to create release and CHANGELOG.md

[gilbertoca]

This one is not a issue, but an improvement. After read about changelog files from Keep a Changelog and searching for something that other open-source projects uses, I think the DoUML project could make release from the last changes using the following tool: GitHub Changelog Generator
WDYF?

[mobius3]

I like the idea and I'm willing to put it in motion, but I think if we're doing releases, we should discuss how that would work for us. We have to consider the following points:

• Work on DoUML does not happen regularly nor we have a fixed set of developers. There are many contributions but they happen occasionally
• I'm not sure about the stability of the software. I see a lot of issues, but I'm not sure if they're showstopping bugs. Do you think it is solid enough to make a release of it?
• We don't have any roadmap, no plan whatsoever. We only have issues and improvements

Keeping that in mind, what would be the release plan for us? How does other projects similar to DoUML in terms of contributions schedule their releases?

[gilbertoca]

Work on DoUML does not happen regularly nor we have a fixed set of developers. There are many contributions but they happen occasionally

This happen because it seems to be dormant. I'm user of BoUML and now DoUML for a long time(including helping @Zeks ), but in recent projects the priority were to use active tools - could not argument against it.

Do you think it is solid enough to make a release of it?

Yes, I think so! We need to show, mainly for linux distributions, that DoUML is the tool to use when thinking in UML.

We don't have any roadmap, no plan whatsoever. We only have issues and improvements

That's the point, no one is trying or using DoUML because the project was not "in motion". How can we improve the usage or update to UML spec without this workforce?

Ah, thank you! I know how difficulty is to work in project without funds - at least initially, DoUML can bring us good results.

[habipyesilyurt]

I think we sould make a release with a notification warning users to back up their work in short periods. That's the only way to test it and get feedback.
I am working on windows platform and using DoUML actively. So we can make a windows release also.

[habipyesilyurt]

I have reviewed all of the issues @mobius3. There is no showstopping bug.
I do not know who is responsible for closing issues, but some issues should be.

[mobius3]

I'm not sure about releasing executables, I don't know if GitHub releases support them. By releasing I mean marking source code as release ready.

I think releasing every 6 months if there's enough work and everything is stable. What do you guys think about it?

Shall we make a 1.0 release then?

[habipyesilyurt]

I think we should make a source release. We should also put windows prebuilt binaries.
Linux users are interested in compiling, but windows users usually wants prebuilt binaries. I can make a windows prebuilt binaries bundle.

[pasgui]

I'm aso able to build binaries for ubuntu.

[pasgui]

commit fa322b available here:
https://launchpad.net/~pasgui/+archive/ubuntu/ppa

[habipyesilyurt]

That's great @pasgui.
I'll spend my 1-week holiday in my hometown where my internet access will be limited. So I will build windows binaries a week later, when I come back.

[mobius3]

That's great indeed! But I think that first we need to tag releases, so that you guys build binaries using that instead of latest commit.

Is there any relevant bug to be fixed before that?

[habipyesilyurt]

I have listed issues in different categories below. List does not include enhancement issues. I think those issues sould not stop us making release.

I am using Douml actively in my work. That is how I caugth serious bugs. So in order to reveal the bugs, douml should be used actively ...

fixed: #132, #125, #121, #115, #110, #105, #84, #79 #78, #77, #76, #51, #33, #24, #20, #15, #12, #2

should be checked: #131, #130, #129, #128, #123, #118, #72, #71, #70, #67, #66, #65, #60, #54, #48, #47, #45, #44, #40, #35, #34, #10, #9

no idea: #128, #124, #83, #81, #29

should be fixed: #101, #100

[gilbertoca]

Initial build test on openSUSE Build Service is ready: DoUML
Done with the last commit: 580b288
The tag release would come in hand now, so the DoUML users can report issues in the right version.
I've already found two ones.

[mobius3]

Ok, I'll tag-release ASAP.

[mobius3]

BTW, thanks for building it for openSUSE!