Hmm I have to manually add them all, I thought we could do something to import all issues from all our repos there. That's fair, I can start adding them as we progress through the backlog. Thanks!
On Tue, Nov 21, 2023 at 4:25 PM Alex Porcelli <[email protected]> wrote: > Absolutely! You can import any GitHub Issue in the project board. > > On Tue, Nov 21, 2023 at 9:37 AM ricardo zanini fernandes > <[email protected]> wrote: > > > > Pretty cool! Many thanks for this work. I liked the emoticons too :P > > > > Q: can we add all the other repos to this board? > > > > Cheers! > > > > On Mon, Nov 20, 2023 at 2:07 PM Alex Porcelli <[email protected]> wrote: > > > > > Dear Apache KIE podling community, > > > > > > This thread aims to inform all community members about an updated > > > version of the public Apache KIE podling GitHub Project Board [1]. > > > > > > Last Friday, Eduardo and I took some time to update it, intending to > > > bring a bit of better visibility of the current status for the > > > upcoming highly anticipated 10.0.0 release. > > > > > > I took the initiative to create a few different views of the project > > > board; here's a brief description of each: > > > > > > - ❇️ My Issues: it should be pretty obvious. It's a board that filters > > > issues assigned to the currently logged user > > > - Main: this is the main board, which covers all issues registered in > > > the project. > > > - ✈️ Release board: this board has all activities organized by > releases. > > > - 🗞️ Comms board: it's a board to track all issues related to comms, > > > including, but not limited to, websites, mailing lists, docs, etc. > > > - 🐞 Bugs: any issue labeled as a bug will be displayed on this board > > > - 👮 Security: any issue labeled as security will be displayed on this > > > board (i.e. CVEs) > > > - 🍰 Good first issues: it should be pretty obvious, targeting new > > > contributors with a list of issues that are good candidates to get > > > your first contribution. > > > - 📝 Epics: although GitHub Issues don't have a formal definition of > > > epics, we can create issues that group other issues and assign the > > > is_epic field to yes. > > > - 📈 Trending: this is a helpful board to provide quick feedback on > > > critical work and its trend (green, yellow, and red). > > > - Everything: a board with no filter and lists in table format all > > > issues associated with the project. > > > > > > The board has the following status to organize issues progress: > > > - Parking Lot: issues that might be blocked or not planned to be > > > tackled anytime soon. > > > - Todo: Backlog > > > - In Progres: Issues that are actively being worked > > > - In Review: Issue that is under review > > > - Done: Issues that have been completely done or closed as won't fix. > > > > > > For releases, I created 8.45.0.Final and 10.0.0. Anything associated > > > with 8.45.0.Final should consider the blocker activities related to CI > > > stabilization that will lead us to branch and set the main to 10.0.0 > > > to start working on the planned first Apache release. > > > > > > I hope you find this board useful, and let's try to keep it updated, > > > so we can have better visibility on how far we are to get our first > > > release out. > > > > > > [1] - https://github.com/orgs/apache/projects/295 > > > > > > - > > > Alex > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [email protected] > > > For additional commands, e-mail: [email protected] > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
