I am happy to move forward in whatever way makes life easier for most of us.
If we have a BACKLOG.md then anyone who wanted to would be able to add to it and would be able to select any ticket from the list to work on. Is that correct? If someone adds to the BACKLOG I would like to discuss it here before that action is taken. Since we already have a 0.16.1 version should we create a branch for patches and keep master for the next release? Would this be a good point to rename "master" to "main" or "trunk"? @Jean-Baptiste Onofré <jeanbaptiste.ono...@gmail.com> in Karaf, how do you record the target and fix versions. Would this work with the idea of the BACKLOG.md file? On Wed, Feb 14, 2024 at 9:07 PM P. Ottlinger <pottlin...@apache.org> wrote: > Hi *, > > I like the overview and the logical sorting of things ..... thanks for > the valuable input, Claude! > > @Claude: would you want to have epics for > BUILD, CORE, CLI - these should be available as components in Jira or we > could create any missing ones? > > Personally I'd prefer epics to be some use-case-oriented way to > structure the tickets, such as: > * "Implement configuration changes to unify the usage of RAT from CLI, > Ant and Maven" > > In the past we didn't have any epics and "just" applied code changes for > each of the topics/tickets - is your proposed list sorted by priority? > > I'd prefer to have a sorted backlog by priority and put tickets into > logical releases (=fixVerson) in order to have smaller release packages. > > Would you mind checking in your list as some sort of BACKLOG.md? > > This would allow to have some simple roadmap planning and ease to > cut/prepare logical release steps. > > WDYT? > > Cheers, > Phil > -- LinkedIn: http://www.linkedin.com/in/claudewarren
