Hi.
Le mer. 6 mars 2019 à 15:20, Benedikt Ritter a écrit :
>
> I think for all non cosmetic changes there should be jira issue for the PR.
+1
> Source code platforms can come and go (think of SourceForge) so we should
> not rely on the GitHub PR as documentation.
+1
And I'd like to stress
On Wed, Mar 6, 2019 at 9:20 AM Benedikt Ritter wrote:
> I think for all non cosmetic changes there should be jira issue for the PR.
> Source code platforms can come and go (think of SourceForge) so we should
> not rely on the GitHub PR as documentation.
>
I created a JIRA issue and updated the
I think for all non cosmetic changes there should be jira issue for the PR.
Source code platforms can come and go (think of SourceForge) so we should
not rely on the GitHub PR as documentation.
Benedikt
Am Mi., 6. März 2019 um 15:14 Uhr schrieb Gary Gregory <
garydgreg...@gmail.com>:
> On Wed,
On Wed, Mar 6, 2019 at 9:06 AM sebb wrote:
> On Wed, 6 Mar 2019 at 13:54, Gary Gregory wrote:
> >
> > Hi All:
> >
> > I'll start with this example from Commons VFS and its changes.xml:
> >
> >
> > Update Apache Commons Collections from 4.2 to 4.3.
> >
> >
> >
> >
On Wed, 6 Mar 2019 at 13:54, Gary Gregory wrote:
>
> Hi All:
>
> I'll start with this example from Commons VFS and its changes.xml:
>
>
> Update Apache Commons Collections from 4.2 to 4.3.
>
>
>
> Add support for customizing FTP transfer aborted status codes.
Hi All:
I'll start with this example from Commons VFS and its changes.xml:
Update Apache Commons Collections from 4.2 to 4.3.
Add support for customizing FTP transfer aborted status codes.
GitHub PR #51.
The first entry uses a JIRA reference as
