I highly recommend creating them for pretty much everything except format correction. Helps determine where the changes occurred and what should be tested (or at least acknowledging that something is low risk enough not to test).
Though I don't think it makes sense to retroactively go back for minor issues if someone forgot to create one :-) On Fri, Jan 10, 2014 at 1:51 AM, Jérôme LELEU <lel...@gmail.com> wrote: > Good catch ! > > Generally, a JIRA is mandatory for tracking and common work. Though, in > that case, I think that we can forget it... > > Thanks. > Best regards, > Jérôme > > > > 2014/1/9 John Gasper <jgas...@unicon.net> > >> Hi all, >> >> As I was doing some code comparison I found that the root index.jsp file >> had duplicate license text. I know it is a small thing, but I yanked it: >> https://github.com/Jasig/cas/pull/385 (master) & >> https://github.com/Jasig/cas/pull/386 (3.5.x) >> >> Should I create a Jira issue for it or can this just be merged as is? >> >> Thanks, >> John >> >> >> -- >> You are currently subscribed to cas-dev@lists.jasig.org as: >> lel...@gmail.com >> >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-dev >> > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > scott.battag...@gmail.com > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
