You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@creadur.apache.org by Claude Warren <cl...@xenei.com> on 2024/02/14 11:59:51 UTC
Re: [DISCUSS] proposed JIRA tickets for 0.17
I proposed this list awhile back, does anyone have any comments? Do we
have a way to make an Epic to track all of these as a release target?
On Tue, Jan 23, 2024 at 11:01 AM Claude Warren <cl...@xenei.com> wrote:
> I walked through the list of Jira tickets and picked out the ones I think
> should be in 0.17 (it is most of them). I further broke them into
> sections. I tried to note where items reached across the sections. Let's
> discuss this and see if there are things that should not be included or
> things that I missed.
>
> The ??? indicate things that don't have a Jira ticket yet.
>
> BUILD
> 345- dependency updates for 0.17
> 344 - multiple outputs in run.
> 336 - assertj in RAT tests
> 324 - add tests for UI updates of ReportConfiguration
>
> CORE
>
> *Configuration changes*
> ??? - Define matcher text from file.
> 352 - wildcards in exclude file
> 330 - Simplify the definition of file types (e.g. *.md, *.txt)
> 327 - add definition for all ASF approved licenses
> 313 - Support new license type EUPL
> 259 - read list of files to be scanned from a text file.
> 246 - .gitignore not honored
> 240 - exclude file does not allow full path.
> 209 - ignore short files when checking licenses.
> 182 - make binary file types configurable
>
>
> *Helper files*
> ??? - create a module that contains usefull extensions. This could
> include RAt-313 and RAT-263
>
> - 337 - Add github action
> - 313 - Support new license type EUPL
> - 356 - HTML Cli help output
>
>
>
> *Documentation*
> 358 - Update documentation to match configuration options and files
> 350 - fix javadoc warnings
> 323 - Harmonize UIs.
>
> *Processing changes*
> ??? -- Check file types
>
> - 334 - verify NOTICE file
> - ??? - verify contentest of archive files where possibel (e.g. jar
> should have LICENSE file)
>
> 248 - Duplicate exclusion list
> 355 - Export XML config
> 255 - Insert copyright headers consistently (part of 330)
> 333 - force option will change file permissions
> 332 - force option can cause system error
> 323 - Harmonize UIs.
> 301 - Rat check identifies chinese characters as binary files.
> 265 - Certain wildcard filters do not work anymore
> 238 - broken symlinks result in crash
> 237 - read license/copyright info from image metadata
> 235 - symlinks not recognized in compressed tarball.
> 190 - false negatives when encoding different.
> ??? -- Binary Guesser Epic
>
> - 183 - binary guesser - display percentage of binary chars used.
> - 178 - binary checker ignores IOexceptions.
> - 176 - binary guesser isBinary returns false on null, should throw
> exception
> - 211 - xml output must be well formed even if BinaryGuesser fails.
>
>
>
> *CLI*
> 323 - Harmonize UIs.
> 356 - HTML Cli help output
>
> Maven Plugin
> 241 - rat plugin fails with forkcount=0
> 199 - support m2e in Eclipse
> 323 - Harmonize UIs.
>
> ANT Tasks
> 323 - Harmonize UIs.
>
>
> --
> LinkedIn: http://www.linkedin.com/in/claudewarren
>
--
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: [DISCUSS] proposed JIRA tickets for 0.17
Posted by "P. Ottlinger" <po...@apache.org>.
Hi *,
I've augmented the existing Jira components - hopefully it eases the work.
Cheers,
Phil
Re: [DISCUSS] proposed JIRA tickets for 0.17
Posted by Claude Warren <cl...@xenei.com>.
My proposed list is not sorted by priority and I am fairly certain there
are cross issue dependencies that need to be sorted out to git a true order
of implementation.
Re: [DISCUSS] proposed JIRA tickets for 0.17
Posted by Claude Warren <cl...@xenei.com>.
I think we should add the following components in Jira:
Build
Client - command line
Client - Maven
Client - Ant
Configuration
Core
Documentation
What I listed as "Helper Files" in the original documentation should be
filed under "Build" or "Configuration"
--
LinkedIn: http://www.linkedin.com/in/claudewarren
Re: [DISCUSS] proposed JIRA tickets for 0.17
Posted by Claude Warren <cl...@xenei.com>.
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é <je...@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 <po...@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
Re: [DISCUSS] proposed JIRA tickets for 0.17
Posted by "P. Ottlinger" <po...@apache.org>.
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
Re: [DISCUSS] proposed JIRA tickets for 0.17
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Claude
It looks good to me. In some projects (like Apache Karaf for
instance), we have target version (where we plan to fix a ticket) and
fix version (when the fix is actually done and included in the
release).
Regards
JB
On Wed, Feb 14, 2024 at 12:59 PM Claude Warren <cl...@xenei.com> wrote:
>
> I proposed this list awhile back, does anyone have any comments? Do we
> have a way to make an Epic to track all of these as a release target?
>
> On Tue, Jan 23, 2024 at 11:01 AM Claude Warren <cl...@xenei.com> wrote:
>
> > I walked through the list of Jira tickets and picked out the ones I think
> > should be in 0.17 (it is most of them). I further broke them into
> > sections. I tried to note where items reached across the sections. Let's
> > discuss this and see if there are things that should not be included or
> > things that I missed.
> >
> > The ??? indicate things that don't have a Jira ticket yet.
> >
> > BUILD
> > 345- dependency updates for 0.17
> > 344 - multiple outputs in run.
> > 336 - assertj in RAT tests
> > 324 - add tests for UI updates of ReportConfiguration
> >
> > CORE
> >
> > *Configuration changes*
> > ??? - Define matcher text from file.
> > 352 - wildcards in exclude file
> > 330 - Simplify the definition of file types (e.g. *.md, *.txt)
> > 327 - add definition for all ASF approved licenses
> > 313 - Support new license type EUPL
> > 259 - read list of files to be scanned from a text file.
> > 246 - .gitignore not honored
> > 240 - exclude file does not allow full path.
> > 209 - ignore short files when checking licenses.
> > 182 - make binary file types configurable
> >
> >
> > *Helper files*
> > ??? - create a module that contains usefull extensions. This could
> > include RAt-313 and RAT-263
> >
> > - 337 - Add github action
> > - 313 - Support new license type EUPL
> > - 356 - HTML Cli help output
> >
> >
> >
> > *Documentation*
> > 358 - Update documentation to match configuration options and files
> > 350 - fix javadoc warnings
> > 323 - Harmonize UIs.
> >
> > *Processing changes*
> > ??? -- Check file types
> >
> > - 334 - verify NOTICE file
> > - ??? - verify contentest of archive files where possibel (e.g. jar
> > should have LICENSE file)
> >
> > 248 - Duplicate exclusion list
> > 355 - Export XML config
> > 255 - Insert copyright headers consistently (part of 330)
> > 333 - force option will change file permissions
> > 332 - force option can cause system error
> > 323 - Harmonize UIs.
> > 301 - Rat check identifies chinese characters as binary files.
> > 265 - Certain wildcard filters do not work anymore
> > 238 - broken symlinks result in crash
> > 237 - read license/copyright info from image metadata
> > 235 - symlinks not recognized in compressed tarball.
> > 190 - false negatives when encoding different.
> > ??? -- Binary Guesser Epic
> >
> > - 183 - binary guesser - display percentage of binary chars used.
> > - 178 - binary checker ignores IOexceptions.
> > - 176 - binary guesser isBinary returns false on null, should throw
> > exception
> > - 211 - xml output must be well formed even if BinaryGuesser fails.
> >
> >
> >
> > *CLI*
> > 323 - Harmonize UIs.
> > 356 - HTML Cli help output
> >
> > Maven Plugin
> > 241 - rat plugin fails with forkcount=0
> > 199 - support m2e in Eclipse
> > 323 - Harmonize UIs.
> >
> > ANT Tasks
> > 323 - Harmonize UIs.
> >
> >
> > --
> > LinkedIn: http://www.linkedin.com/in/claudewarren
> >
>
>
> --
> LinkedIn: http://www.linkedin.com/in/claudewarren