Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The latest released version is now six years old #1141

Closed
amilcarlucas opened this issue May 21, 2019 · 6 comments
Closed

The latest released version is now six years old #1141

amilcarlucas opened this issue May 21, 2019 · 6 comments
Assignees

Comments

@amilcarlucas
Copy link
Collaborator

amilcarlucas commented May 21, 2019

Please do a "Mavlink 1.0.12" release version. I am working on the product where I need to list the released version of all the software components that I use.
I would realy like to use a recent mavlink version.

I maybe have the permissions to do that myself. Should I try that?
Edit: I can tag, push and do releases. :)

@amilcarlucas amilcarlucas changed the title The latest released version is six years old The latest released version is now six years old May 21, 2019
@hamishwillee
Copy link
Collaborator

If you use the current version it is the latest version - 6 years old or otherwise :-).

I'd like an update too, mostly because there is some tidying we might reasonably do in a new release. But not just "in order to have a release". The trigger I was hoping for was @tridge making his concrete proposal for a new parameter protocol.

Others might feel differently?

@amilcarlucas
Copy link
Collaborator Author

I do vote for a release for the sake of releasing.
We can always do another release later.

@amilcarlucas amilcarlucas added the Dev Call Issues to be discussed during the Dev Call label May 22, 2019
@amilcarlucas
Copy link
Collaborator Author

The dev call is today at 18H00 CET right?

@hamishwillee
Copy link
Collaborator

Next week, 5pm AEST. Easiest way to check is the dronecode calendar linked from here: https://mavlink.io/en/about/support.html#schedule

@hamishwillee
Copy link
Collaborator

Hi @amilcarlucas

Done in https://github.com/mavlink/mavlink/releases/tag/1.0.12 - sorry for the delay.

We really need to clarify the release process and (possibly) co-ordinate source code, built library and subversion updates. That is deferred to #1149.

@hamishwillee hamishwillee self-assigned this May 29, 2019
@hamishwillee hamishwillee removed the Dev Call Issues to be discussed during the Dev Call label May 29, 2019
@amilcarlucas
Copy link
Collaborator Author

Thanks !!!! that is a great help :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants