DevOps: Release Management?

[joeblankenship1]

Is there a release management system in place from LibreQDA?

I was beginning to migrate LibreQDA to Python 3 when I realized we should have some alpha release requirements & benchmarks in place as we head towards a good beta.

How should we proceed?

[marcbria]

The soft was delivered "as is" and installed in the server by the external enterprise.

During the development process we define a list of requirements and the external enterprise worked on them till dev hours finished. We can send to you this documentation (a "storyboard" with main screens and needs). It could be useful to see the UI, the features... In other words, where we like to go with libreQDA.

Unfortunately, there is no unit test, no staging process, no benchmark defined.

Please, feel free to suggest what you like best or you think fits better.

Right now we are reinstalling the server and we are thinking in dokerize it to keep things sorted, but docker is neither a decision.

[marcbria]

Missed to explain that, as you probably noticed, we have a list of issues/feature requests in this github.

Versions define the road map we have in mind:

• 1.0: Is considered the minimal release to open libreQDA to the public. Essential features need to be developed and bugs fixed. It will be the fist "Beta" version. Good for testing, but still not mature enough for real work.
• 1.1: Stuff that is not essential, but we believe it's important to be fixed to consider libreQDA a real competitor in the QDA scene. It will be the fist "full functional" release.
• ...

As always, discussion is open, so feel free to add new issues or comment the existing ones.

About TAGs I need to ask my fellows to review the list to be sure they are ok.
I'm also unsure if we really need all those tags... Personaly I will encourage here to use a shorter list (more standard) as:

• bug
• enhancement
• discussion
• documentation
• must be
• question
• duplicate
• invalid
• wontfix
• more info

[joeblankenship1]

I'm really sorry to hear that; I'll definitely start planning my development goals. That story also explains a lot about the project as it is now. I will review the issues in detail to get together a requirements list as soon as I can.

And the releases sounds good. I'll build to the existing functionality with fixed issues for 1.0 and save the JS visualizations, machine learning, and enhanced functionality for 1.1+.

Thank you for the clarification!

[marcbria]

Short update:
Server reinstallation is on the way and Docker is a must.
We are evaluating this branching model: http://nvie.com/posts/a-successful-git-branching-model

[joeblankenship1]

Thanks for the update and sorry for being out of the loop.
I like the branching model; should we start a wiki page outlining these procedures? I can start that this weekend if so.
I will also check out the docker file on my end.

[marcbria]

@jmunoz298 gave you access to the wiki section a week ago or so.
Please, let us know if all is working fine.

[joeblankenship1]

Thanks for the update! All is well; I actually wrote an English install guide in early February.

[joeblankenship1]

Hello team,
I'm very sorry I have not made any pull requests yet. I am still upgrading the Django framework incrementally from 1.4 to 1.10 (by recommendation of a Django guru). This should also make the 2.7 to 3.5 move much easier and with less dependency/test issues.
If there are any other issues that arise, please let me know.

[jmunoz298]

Thanks Joe for your work. As you know, we don't have django developers and we are not in a hurry so any help is welcome. No worry about the delay. Please, let us know if we can help you in some sense. Cheers, ```/ (o o) --------O--(_)--OOo-------- Juan Muñoz Justicia Departament de Psicologia Social Facultat de Psicologia Universitat Autònoma de Barcelona Edifici B - Despatx B5-034 08193 Bellaterra (Barcelona) España Tf.: 34-935812874 Fax: 34-935812125 http://juan.psicologiasocial.eu On Mon, May 15, 2017 8:29 PM, Joe Blankenship [email protected] wrote: Hello team, I'm very sorry I have not made any pull requests yet. I am still upgrading the Django framework incrementally from 1.4 to 1.10 (by recommendation of a Django guru). This should also make the 2.7 to 3.5 move much easier and with less dependency/test issues. If there are any other issues that arise, please let me know. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[joeblankenship1]

@marcbria @jmunoz298 @lupa18
There is a team of developers [ @nurruty @CariSoca @santicamou ] that is looking to create a Flask-variant of the existing LibreQDA using MongoDB and Angular.
There is a question as to what name they should call the project. My thought is that if this framework proves more functional than the existing one, the LibreQDA organization proper may consider adopting the repo in the future as "LibreQDA". I wanted to see if you all as the project leaders have any opinions on this issue.

[joeblankenship1]

@marcbria I believe @nurruty said they were working on a local version first. Would you like them to create a "LibreQDA-Flask" Git branch or repo so you can take a look?

[marcbria]

I removed former message when I found the repo here: https://github.com/nurruty/proyecto

I'm talking with the rest of the members of the project to decide what to do. @lupa18 pointed that a few months ago those guys contacted us but I didn't personally talk with them.

As we explained in former post, our team is formed but people that knows a lot about QDAs, but non of use know python so my fist sensation here is that I'm really happy someone likes to keep working on it.

We never had preferences about the programming lang, so if they like to clone it all to flask-angular-mongodb I think my fellows will be happy with it.

Would you like them to create a "LibreQDA-Flask" Git branch or repo so you can take a look?
Not yet. Let us one or two days to talk about it.

Thanks @joeblankenship1 to point us about the project.

[nurruty]

Hi Marc, as you said we talked to @lupa18 and @alenperez a few months ago to get to know the project. We are working on our final project at the university and we are planning to continue working on this tool.

Since then we have been talking to @joeblankenship1 and we have decided to reinvent the application, always taking into account the features that your team has highlighted.

Yesterday I pushed the angular2 project in that repo that you found. However, it is only a temporary place to start working on a prototype we have to show a few weeks from now. As Joe said earlier, we had some questions about the name and ownership of the new project.

[marcbria]

Ok @nurruty I'm starting to remember. :-)

After vacations, we can hangout/skype or if you prefer, publish here (in a new post) the questions that need to be answered.

Cheers,
m.

[joeblankenship1]

@marcbria @nurruty That sounds great!