[Geoserver-devel] 1.6.x branch version

GeoServer GeoServer Developer
1

Greetings,

I downloaded the 1.6.x branch, which after compiling it shows
1.6.1-beta version.

Is this branch aligned with the 1.6.3 release and showing an earlier
version, or does one need to download 1.6.3 source from somewhere
else?

Thanks in advance,
Alex

2

Alexander Petkov ha scritto:

Greetings,

I downloaded the 1.6.x branch, which after compiling it shows
1.6.1-beta version.

Is this branch aligned with the 1.6.3 release and showing an earlier
version, or does one need to download 1.6.3 source from somewhere
else?

We just never changed the i18n files that have that "1.6.1-beta"
string, but rest assured you have the latest in your hands.
Cheers
Andrea

3

On Tue, May 20, 2008 at 8:47 AM, Andrea Aime <aaime@anonymised.com> wrote:

Alexander Petkov ha scritto:

Greetings,

I downloaded the 1.6.x branch, which after compiling it shows
1.6.1-beta version.

Is this branch aligned with the 1.6.3 release and showing an earlier
version, or does one need to download 1.6.3 source from somewhere
else?

We just never changed the i18n files that have that "1.6.1-beta"
string, but rest assured you have the latest in your hands.
Cheers
Andrea

Cool, I thought that might be the case :slight_smile:

Alex

4

Should we be handling version numbers on branches differently? I too have gotten confused by this on a few occasions? Is there a Best Practice for this sort of thing?

Thanks,
Mike Pumphrey
Outreach Engineer
The Open Planning Project

Alexander Petkov wrote:

On Tue, May 20, 2008 at 8:47 AM, Andrea Aime <aaime@anonymised.com> wrote:

Alexander Petkov ha scritto:

Greetings,

I downloaded the 1.6.x branch, which after compiling it shows
1.6.1-beta version.

Is this branch aligned with the 1.6.3 release and showing an earlier
version, or does one need to download 1.6.3 source from somewhere
else?

We just never changed the i18n files that have that "1.6.1-beta"
string, but rest assured you have the latest in your hands.
Cheers
Andrea

Cool, I thought that might be the case :slight_smile:

Alex

-------------------------------------------------------------------------
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:4051,4832e50a216194901796417!

5

Mike Pumphrey ha scritto:

Should we be handling version numbers on branches differently? I too have gotten confused by this on a few occasions? Is there a Best Practice for this sort of thing?

No, it's just that some would have to go into the i18n files
after each release and change the name to GeoServer 1.6.n+1-snapshot,
for example, after the current release, make it 1.6.5-snapshot or
1.6.5-beta

Cheers
Andrea

6

Well, I already do that for handling the tagged releases, so it's not so hard to do it on 1.6.x as well. I'll add it to the release guide (which is slowly being made sane).

http://geoserver.org/display/GEOSDOC/7+Releasing

Thanks,
Mike

Andrea Aime wrote:

Mike Pumphrey ha scritto:

Should we be handling version numbers on branches differently? I too have gotten confused by this on a few occasions? Is there a Best Practice for this sort of thing?

No, it's just that some would have to go into the i18n files
after each release and change the name to GeoServer 1.6.n+1-snapshot,
for example, after the current release, make it 1.6.5-snapshot or
1.6.5-beta

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:4051,4832f1f7258941849620573!

7

This has been done. 1.6.x files now are uniformly listed as 1.6.5-beta. They were variously listed as:

1.6-SNAPSHOT
1.6.0
1.6.0-beta
1.6.1-beta

Thanks,
Mike

Mike Pumphrey wrote:

Well, I already do that for handling the tagged releases, so it's not so hard to do it on 1.6.x as well. I'll add it to the release guide (which is slowly being made sane).

http://geoserver.org/display/GEOSDOC/7+Releasing

Thanks,
Mike

Andrea Aime wrote:

Mike Pumphrey ha scritto:

Should we be handling version numbers on branches differently? I too have gotten confused by this on a few occasions? Is there a Best Practice for this sort of thing?

No, it's just that some would have to go into the i18n files
after each release and change the name to GeoServer 1.6.n+1-snapshot,
for example, after the current release, make it 1.6.5-snapshot or
1.6.5-beta

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

-------------------------------------------------------------------------
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:4051,4834405b201851096210785!