5.x-2.x - Rewrite to match new version of event module

Thanks fine with me.

Quick questions just for my own education:

Are we moving away from Unix timestamps for performance?
Are we allowed to do this because Drupal doesn't support mysql 3 as of Drupal 5?
Will this break support for date module? If so, will date module be moving in this direction?

Sorry if some of those are dumb questions, I just want to make sure I understand. Thanks!

Sorry, I thought I had responded to this, and I just noticed that I hadn't.

Feel free to use HEAD. If any changes come up that I think need to go in there, I'll let you know before I do it, just so you know the state of the code.

Changing the name of this issue just to help keep the battle plan straight.

A 5.x-2.x branch has been created from head. Marking this as fixed. Please post additional issues and patches for this version as the proper branch (it should be showing up in the list soon).

It's been almost a month and it is still not showing up! What's up?

I created a release for 5.x-2.x-dev a while back, but it's now showing up on the module page. Not sure why. I removed the "New Features" tag, thinking maybe it will show up now. You can see it on the "View all releases page." You can also get it from cvs.

If anyone has a hint on how to make it show up on the module page, let me know.

Did you 'Add new release'? That does it for me with new branches.

BTW, has this effort stalled?

Still not sure why this is not showing up on the project page, but it is listed under releases.

The 5.x-2.x branch has a few things that need to be fixed (exceptions being a big one), but otherwise I think killes, etc., have finished their version. You can see the issues in the queue. I'll try to take a look at wrapping these up soon. As always patches welcome.

Hmm, maybe I am missing something but I still don't see the 5.x-2.x version under releases.

Yeah, I'm not sure why it isn't catching the branch from cvs to make that release. I'll see if I can dig a bit deeper to find it.

I finally ran into the same problem and the solution is somewhat obvious.

From your project's main page, click on the 'edit' tab.

Then click on the 'Releases' link/secondary tab.

You should have a selection box for choosing the 'Major version'.

Choose 2.

Save.

Ta-da!!!

Here's a link until you get it working: eventrepeat-5.x-2.x-dev.tar.gz

I've tried your suggestions and still could not get it to work. All the options seem to be set correctly, but there is still no download link and it won't show up on the project page. As it is unstable, your best bet is still to get the code through cvs if you have that option. I've contacted dww and asked him to take a look to see if I missed something obvious. Until then, our best bet is probably to concentrate on getting it stable and creating a .0 release in the hopes we'll have better results there.

In that case, I would imagine that showing a 2.x release depends on the existence of a 2.0 release (or other tag, not branch). Anyway, I've been meaning to help out with the current efforts but haven't had time. Sounds like you know how that is...

Can I recommend manually putting a link to this release on the project page in the meantime? I just happened to stumble upon this page.

Thanks to some help from dww, this version is now generating a tarball. You will have to click on the "all releases" link to get it. According to him, it won't be on the project page until it is the suggested version. We'll need to get to some of these bugs before that happens, obviously. I am hoping that this month is a bit better for me than the last few. I hope to spend some much needed time on this soon.

Well 5.x-2.x is on the front page now. So this issue is fixed.

Thanks
Robert