Hi everyone,
we're hoping to start the release process for GeoServer 1.6.1 tomorrow and release the new version on Wednesday.
We'll have a closer look at JIRA tomorrow, please do let me know if there is anything else that we need to watch out for.
Regards,
-Arne
Arne Kepp ha scritto:
Hi everyone,
we're hoping to start the release process for GeoServer 1.6.1 tomorrow and release the new version on Wednesday.
We'll have a closer look at JIRA tomorrow, please do let me know if there is anything else that we need to watch out for.
What about the 28 issues that we still need to fix? Sure we can delay
a few of them, reduce the list down to 10-15, but it's still a few days
of work.
We agreed to port the watermark code onto 1.6.1, but I still haven't managed to, and it's no small task. I'll be doing it tomorrow, not
sure when I'll be done.
I'd say start Wednesday or Thursday and announce on Monday next week instead?
Cheers
Andrea
I think we can probably push off most of the stuff to 1.6.2, including the watermarking stuff. One thing we should get in is the fix for the kml reflector since its a regression.
2c
-Justin
Andrea Aime wrote:
Arne Kepp ha scritto:
Hi everyone,
we're hoping to start the release process for GeoServer 1.6.1 tomorrow and release the new version on Wednesday.
We'll have a closer look at JIRA tomorrow, please do let me know if there is anything else that we need to watch out for.
What about the 28 issues that we still need to fix? Sure we can delay
a few of them, reduce the list down to 10-15, but it's still a few days
of work.
We agreed to port the watermark code onto 1.6.1, but I still haven't managed to, and it's no small task. I'll be doing it tomorrow, not
sure when I'll be done.
I'd say start Wednesday or Thursday and announce on Monday next week instead?Cheers
Andrea-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:4007,47c32a0e183291096210785!
--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com
This is the last email I can find mention a date for 1.6.1 release - what was the decision here?
I see that GEOS-1765 has been pushed off to 1.6.2, has the release date of 1.6.1 been set yet? I will check the IRC meeting logs next...
Jody
I think we can probably push off most of the stuff to 1.6.2, including the watermarking stuff. One thing we should get in is the fix for the kml reflector since its a regression.
2c
-Justin
Andrea Aime wrote:
Arne Kepp ha scritto:
Hi everyone,
we're hoping to start the release process for GeoServer 1.6.1 tomorrow and release the new version on Wednesday.
We'll have a closer look at JIRA tomorrow, please do let me know if there is anything else that we need to watch out for.
What about the 28 issues that we still need to fix? Sure we can delay
a few of them, reduce the list down to 10-15, but it's still a few days
of work.
We agreed to port the watermark code onto 1.6.1, but I still haven't managed to, and it's no small task. I'll be doing it tomorrow, not
sure when I'll be done.
I'd say start Wednesday or Thursday and announce on Monday next week instead?Cheers
Andrea-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:4007,47c32a0e183291096210785!
Last published logs were February 12th so I am out of luck...
So guys when is 1.6.1 going to be released?
Jody
I think we can probably push off most of the stuff to 1.6.2, including the watermarking stuff. One thing we should get in is the fix for the kml reflector since its a regression.
2c
-Justin
Andrea Aime wrote:
Arne Kepp ha scritto:
Hi everyone,
we're hoping to start the release process for GeoServer 1.6.1 tomorrow and release the new version on Wednesday.
We'll have a closer look at JIRA tomorrow, please do let me know if there is anything else that we need to watch out for.
What about the 28 issues that we still need to fix? Sure we can delay
a few of them, reduce the list down to 10-15, but it's still a few days
of work.
We agreed to port the watermark code onto 1.6.1, but I still haven't managed to, and it's no small task. I'll be doing it tomorrow, not
sure when I'll be done.
I'd say start Wednesday or Thursday and announce on Monday next week instead?Cheers
Andrea-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:4007,47c32a0e183291096210785!
Jody Garnett ha scritto:
Last published logs were February 12th so I am out of luck...
So guys when is 1.6.1 going to be released?
It was going to be released today if it weren't for your
patches, but since we're trying to accomodate them in,
we delayed the gt2 release to tomorrow,
and the gs one right afterwards.
I am supposed to review your patches tomorrow, make sure
they don't break the cite tests. If they do, would you
mind if I roll them back, make the release, and roll
them in again?
Cheers
Andrea
Andrea Aime wrote:
Jody Garnett ha scritto:
Last published logs were February 12th so I am out of luck...
So guys when is 1.6.1 going to be released?I am supposed to review your patches tomorrow, make sure
they don't break the cite tests. If they do, would you
mind if I roll them back, make the release, and roll
them in again?
Not at all; that would be fine. Thanks for waiting for me; it would be nice
to have these bugs fixed.
Jody