question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

This is actually a continuous thing, but we need to start. I think doing it according to this: http://keepachangelog.com/en/0.3.0/ is a good idea.

The section Project history from README.md should be moved there (rewrite it according to that format) because it belongs there and we don’t want to have a mile-long README. Also, we should add the stuff that’s been changed so far.

The main reason for this is that people are actually starting to use this AlexaPi repo and it’s a good idea to write at least breaking changes somewhere.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:12 (12 by maintainers)

github_iconTop GitHub Comments

1reaction
reneklimentcommented, Oct 22, 2016

@illperipherals

Because we will be working in branches, lets just increment when pushed to master. Does that cause any kind of problem?

I’m not sure I get what you mean. We would do versioning only on master, because I don’t think it does make sense on feature-branches or any other branches for that matter (also, we’d have collisions and stuff).

Yes, I’m feeling the need for some announcements / stuff space / talk too. Therefore:

  1. I’m starting this change log, where users can see what’s new with the project and to be aware of important changes.
  2. I’ve started on the wiki here. It would be great if we could build a decent documentation there - mainly regarding audio. Feel free to add stuff in there. I’m gonna send a small PR in a bit, that removes stuff from README that’s moved there and puts links to the wiki so people are more aware of it.
  3. I’ve requested Gitter for this repo, but @sammachin needs to approve this first as the org owner. I’ll try to get in touch with him to speed it up.
0reactions
reneklimentcommented, Oct 26, 2016

So Sam gave me some sweet permissions and now we can chat over at https://gitter.im/alexa-pi/Lobby! I’ll be sure to update the docs so people can find it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Keep a Changelog
A changelog is a file which contains a curated, chronologically ordered list of notable changes for each version of a project. Why keep...
Read more >
Changelog - Wikipedia
A changelog is a log or record of all notable changes made to a project. The project is often a website or software...
Read more >
What is Changelog & Example of ARN Change Log Format
Perhaps you've heard of the term “changelog” but aren't quite sure what it is. Simply put, changelog is a documented record of all...
Read more >
News and podcasts for developers |> Changelog
Podcasts from Changelog. Weekly shows about software development, developer culture, open source, building startups, artificial intelligence, brain science, and ...
Read more >
Change Logs (GNU Coding Standards)
Keep a change log to describe all the changes made to program source files. The purpose of this is so that people investigating...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found