From 153674a2b98276a6aa5c2b4854160188ceffe4f2 Mon Sep 17 00:00:00 2001 From: Rok Garbas Date: Fri, 18 Dec 2020 14:10:14 +0100 Subject: [PATCH] removing ideas from the README.md since we already have them in tickets --- README.md | 27 +-------------------------- 1 file changed, 1 insertion(+), 26 deletions(-) diff --git a/README.md b/README.md index 097e9df..0299e4e 100644 --- a/README.md +++ b/README.md @@ -36,31 +36,6 @@ writing better search query. Suggesting feature should guide user to write better queries which in turn will produce better results. -## Ideas we want to explore - -Apart from searching packages and options we would like to: - -- Not only search for latest channels, but be enable to search in any - evaluation. We need to explore how much in the past we can go, I'm sure we - will have to make some compromises. -- Provide each maintainer with a page that lists packages that they - maintain. A page - later - could also show his ticket and opened Pull - Requests. -- Each package should have a page which would show versions in different - evaluations/channels. It could also show - at one point - ticket that this - package -- With all this information in the database it would be very useful to show - some sort of reports. Few examples that come to my mind: - - What packages and options were added/removed/changed between to evaluations? - This could be useful for Release Manager when making release notes or just - in general to see difference what has changed since last time. - - How are we doing with tickets/pull requests? Burn-down chart maybe. The - idea behind is to have a nicer view over current status of tickets/pull - requests. - -Probably there are more ideas I just need to remind myself to write them down. - - ## Development To start developing open a terminal and run: @@ -76,7 +51,7 @@ application. ## Deploying -- On each commit to `master` branch a GitHub Action is trigger. +- On each commit to `main` branch a GitHub Action is trigger. - GitHub Action then builds production version of the web application using `yarn prod` command. - The built web application (in `./dist`) is then deployed to Netlify.