Update Readme

Author: swissmanu

.github/workflows/main.yml

@@ -1,21 +1,21 @@
 on:
   push:
-    # Sequence of patterns matched against refs/tags
     tags:
-    - 'v*' # Push events to matching v*, i.e. v1.0, v20.15.10
+    - 'v*'
 
-name: Upload Release Asset
+name: Build and Upload Release Assets
 
 jobs:
   build:
-    name: Upload Release Asset
+    name: Build and Upload Release Assets
     runs-on: ubuntu-latest
     steps:
-      - name: Get the version
+      - name: Extract Version from Tag
         id: get_version
         run: echo ::set-output name=VERSION::${GITHUB_REF/refs\/tags\//}
       - name: Checkout code
         uses: actions/checkout@v2
+
       - name: Build LaTeX
         uses: xu-cheng/latex-action@v2
         with:
@@ -26,6 +26,7 @@ jobs:
             minted fvextra xstring framed
           extra_system_packages: py-pygments
           latexmk_shell_escape: true
+
       - name: Create Release
         id: create_release
         uses: actions/create-release@v1
@@ -42,7 +43,7 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         with:
-          upload_url: ${{ steps.create_release.outputs.upload_url }} # This pulls from the CREATE RELEASE step above, referencing it's ID to get its outputs object, which include a `upload_url`. See this blog post for more info: https://jasonet.co/posts/new-features-of-github-actions/#passing-data-to-future-steps
+          upload_url: ${{ steps.create_release.outputs.upload_url }}
           asset_path: ./paper.pdf
           asset_name: manuel-alabor-debugging-of-rxjs-based-application-${{ steps.get_version.outputs.VERSION }}.pdf
           asset_content_type: application/pdf

README.md

@@ -2,11 +2,11 @@
 
 > RxJS is a popular library to implement data-flow-oriented applications with JavaScript using reactive programming principles. This way of programming bears new challenges for traditional debuggers: Their focus on imperative programming limits their applicability to problems originated in the declarative programming paradigm. The goals of this paper are: (i) to understand how software engineers debug RxJS-based applications, what tools do they use, what techniques they apply; (ii) to understand what are the most prevalent challenges they face while doing so; and (iii) to provide a course of action to resolve these challenges in a future iteration on the topic. We learned about the debugging habits of ten professionals using interviews, and hands-on war story reports. Based on this data, we designed and executed an observational study with four subjects to verify that engineers predominantly augment source code with manuel trace logs instead of using specialized debugging utilities. In the end, we identified the lack of fully integrated RxJS-specific debugging solutions in existing development environments as the most significant reason why engineers do not make use of such tools. We decided to elaborate on how to resolve this situation in our future work.
 
-## Releases
+## Download Paper
 
 ![Build PDF](https://github.com/swissmanu/mse-pa1/workflows/Build%20PDF/badge.svg)
 
-- none so far
+See https://github.com/swissmanu/mse-pa1-paper-debugging-of-rxjs-based-applications/releases for the latest version.
 
 ## Further Resources