When we have Jira back we can remove those files. I was just trying to be
helpful.
On Sat, Apr 18, 2015 at 1:43 PM Andrea Aime
wrote:
> On Sat, Apr 18, 2015 at 10:10 PM, Andrea Aime <
> andrea.a...@geo-solutions.it> wrote:
>
>> I have set up a CHANGELOG.md for each branch populated from CodeHaus.
On Sat, Apr 18, 2015 at 10:10 PM, Andrea Aime
wrote:
> I have set up a CHANGELOG.md for each branch populated from CodeHaus.
>>
>> * https://github.com/geoserver/geoserver/blob/master/src/CHANGELOG.md
>> * https://github.com/geoserver/geoserver/blob/2.7.x/src/CHANGELOG.md
>> * https://github.com/
On Fri, Apr 17, 2015 at 9:39 PM, Jody Garnett
wrote:
> I have set up a CHANGELOG.md for each branch populated from CodeHaus.
>
> * https://github.com/geoserver/geoserver/blob/master/src/CHANGELOG.md
> * https://github.com/geoserver/geoserver/blob/2.7.x/src/CHANGELOG.md
> * https://github.com/geos
I have set up a CHANGELOG.md for each branch populated from CodeHaus.
* https://github.com/geoserver/geoserver/blob/master/src/CHANGELOG.md
* https://github.com/geoserver/geoserver/blob/2.7.x/src/CHANGELOG.md
* https://github.com/geoserver/geoserver/blob/2.6.x/src/CHANGELOG.md
In addition I have
Harrison Grundy do you have update / ETA for the team?
Time to kick it old school I guess - I have started a CHANGELOG as a
temporary measure:
* https://github.com/geoserver/geoserver/blob/2.7.x/src/CHANGELOG.md
This will let us mark down what issues have been resolved so we can fix the
issue t
Hi,
during the weekend me and Jody are going to cut GeoServer 2.6.3.
One trouble is that we are going to need to go out of our normal way
for it because the Jira migration is still in progress and we have a
notion of which tickets have been closed split among the two
Jira instances. (Harrison, cc'
