0.6 release schedule?

[petri]

Has a release date been committed to? A week? A month? Just checking to
make sure GeoLocation 0.2 branch will be in a "releaseable" state for
ER 0.6.

GL 0.2 is btw planned to be a "dual" release; there'll be a package
released for both plone 2.0 & 2.1.

Petri

[Justin Ryan]

Petri - is GeoLocation a separate package? Sorry, I've only been
peripherally following.

[Michael Reitsma]

what will the geolocation branch do exactly ?

2005/10/10, Justin Ryan <just...@gmail.com>:

--
met vriendelijke groeten / with kind regards

Michael Reitsma

[Justin Ryan]

On 10/10/05, Michael Reitsma <mrei...@gmail.com> wrote:
> what will the geolocation branch do exactly ?
>

Locations will be a separate object attached to registrations, or
maybe registrants? I believe we are using a separate package so that
other zope / plone products who wish to store geographic location data
can reuse code and interchange objects with us.

[Michael Reitsma]

does this branch work already with Plone2.1 ?

2005/10/10, Justin Ryan <just...@gmail.com>:

[Justin Ryan]

Howdy Michael,

On 10/10/05, Michael Reitsma <mrei...@gmail.com> wrote:
> does this branch work already with Plone2.1 ?
>

The state of various branches is unclear to me.
jmcvetta_atct_and_location should have a great deal to do with 2.1
integration, since all default types are ATCT now, and basically
anything non-AT works all funky these days.

I know that trunk won't install in 2.1, perhaps we can both give some
of these branches a shot and report our success / failure.

Cheers!

-=JR

[petri]

I cannot comment for other branches, but the
geolocation-0.2-integration contains my GeoLocation 0.2 integration
work and some small location-related featurelets (such as finding
"nearby" locations). I think Jason has worked on integration in
jmcvetta_atct_and_location branch, too.

To answer a prior question here as well, GeoLocation is a different
package. GeoLocation 0.2 release is planned to be released in sync with
ER 0.6 and will be available as two different packages; one for Plone
2.0 & one for 2.1.

If you'd like to know more, it has a google group as well, and a Plone
Software Center entry. There's also a related plain-python library
called "geolocator" (see PyPI / Cheese Shop).

Regards,

Petri

[Jason McVetta]

No firm release date for 0.6.   If you know someone who wants to pay for its development, it would definitely move faster.  As it is now, it's comming along on a "when I have time" basis.. which is not too fast right now, since all my time is being consumed with visits to family & old friends.  It'll probably move faster once I'm back in California, with better net access and more free time. 

I do have the install system working with Plone 2.1 now (so that it doesn't conflict with ATEvent when installed, and nicely restores ATEvent when uninstalled). 

The actively developed branch has been jmcvetta-atct_and_location.  That name is less than obvious, so I am renaming it to "0.6-devel".  Additionally, I have cleaned up the branches folder a little by deleting "SignUpSheet" (it was a 2.0.x-based experiement). 

I intend to develop 0.6 with the latest Plone 2.1 version of GeoLocation.  Petri, which branch should I be tracking?

Jason

On 10/10/05, petri <pet...@gmail.com> wrote:

[Justin Ryan]

On 10/10/05, petri <pet...@gmail.com> wrote:
>

> Has a release date been committed to? A week? A month? Just checking to
> make sure GeoLocation 0.2 branch will be in a "releaseable" state for
> ER 0.6.

I'm in the process of modeling ER in Argo and cleaning up some code in
a derivative branch of 0.6, though I'm not sure if anything will
materialize before 0.6 release. I have noticed some code moving
through there, although it still doesn't install in 2.1.

> GL 0.2 is btw planned to be a "dual" release; there'll be a package
> released for both plone 2.0 & 2.1.
>

Do you need some help keeping this 2.0 and 2.1 code in one product?
what's different? you should aim for a smooth upgrade path and avoid
a maintenance nighmare..

cheers,

-=jr

[petri]

Justin, thanks for the offer. I'd highly appreciate any help having
both 2.0 & 2.1 code inside a single release if possible, rather than
releasing two versions. A single release was my original plan anyway,
but I was not confident it's feasible enough. How about discussing this
on irc, at #geolo...@irc.freenode.net? I tend to hang around on the
channel during GMT working hours just in case someone wants to drop in
to discuss the package.

As a result of the effort, we could also compile a how-to on the topic.
I would guess that'd be of some interest to the community at large as
well.

Thanks,

Petri