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

Update UG to say ‘latest jar’ instead of addressbook.jar #28

Merged
merged 1 commit into from
Jul 30, 2024

Conversation

brein62
Copy link

@brein62 brein62 commented Jul 20, 2024

Fixes #23. Changes UserGuide.md by replacing "latest addressbook.jar" with "latest .jar file":

- 1. Download the latest `addressbook.jar` from [here](https://github.com/se-edu/addressbook-level3/releases).
+ 1. Download the latest `.jar` file from [here](https://github.com/se-edu/addressbook-level3/releases).

Copy link

@drustanyjt drustanyjt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@damithc
Copy link

damithc commented Jul 26, 2024

@brein62 can you provide a commit message body too?

Follow the guidelines given in https://se-education.org/guides/conventions/git.html

@jyue487
Copy link

jyue487 commented Jul 27, 2024

LGTM.

I have another suggestion. Is it okay if we directly include the jar file link itself, meaning clicking on the link will automatically download the.jar file instead of redirecting them to the release page first, it could ease the users more as one working step is reduced, but we will have to ensure the link is correct and valid every time we make updates to the jar file.

Currently, every time a new release is done, developers would have to
update the file name to reflect the latest JAR file published. This
can be difficult to keep track of.

Let's change the JAR download step (step 2) in the Quick Start section
in the user guide to say "latest `.jar` file" instead of "latest
`addressbook.jar`".

This serves to make the JAR download step generic, eliminating the need
for developers to update the file name every time a new release is
published.
@brein62
Copy link
Author

brein62 commented Jul 27, 2024

LGTM.

I have another suggestion. Is it okay if we directly include the jar file link itself, meaning clicking on the link will automatically download the.jar file instead of redirecting them to the release page first, it could ease the users more as one working step is reduced, but we will have to ensure the link is correct and valid every time we make updates to the jar file.

@jyue487 This is a good idea from a user standpoint. However, this would not improve developers' workflows when a release is published since they would still have to update the link to reflect the newest release of the JAR file.

Since #23 aims to reduce the additional workload of developers having to update the UG to reflect the new name of the JAR file with each new release, this suggestion might not be a great improvement compared to what we have previously.

@drustanyjt
Copy link

drustanyjt commented Jul 27, 2024

will have to ensure the link is correct and valid every time we make updates to the jar file.

@jyue487 I think this would add more inconvenience (from having to remember to change 1 extra link) than effort saved. Maybe it could be changed to link to the latest release by using "https://github.com/se-edu/addressbook-level3/releases/latest" instead? This way the link doesn't need to be changed every release, but still directs the user to the correct .jar file to download.

Personally I prefer leaving it as is now because it gives students an opportunity to get familiar with the GitHub releases page as a whole.

@aureliony
Copy link

aureliony commented Jul 27, 2024

Personally, I recommend linking the releases/latest page as suggested by @drustanyjt. As this is for the UG (not DG), having multiple jar files on the same page might confuse users that are not familiar with GitHub. It depends on the project's target audience. Ideally, the link should lead to a download page on the project's own website, not GitHub, but this is not possible for tp.

@damithc damithc merged commit 3da04ac into nus-oss:master Jul 30, 2024
3 checks passed
@damithc
Copy link

damithc commented Jul 30, 2024

Thanks for the PR @brein62 and others for the inputs.
For now, let's merge this as is (except a few column width adjustments to the commit message).

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

Successfully merging this pull request may close these issues.

Update UG to say ‘latest jar’ instead of specific file name
5 participants