It would help people test your code if you would develop on a DRUPAL-5 developer tag and let the packaging system provide and up-to-date tarball that people can download. For more info: http://www.angrydonuts.com/my_informal_take_on_using_the_ne

Comments

mercmobily’s picture

mercmobily commented

Hi,

Absolutely.
Thing is, I've been fixing very critical bugs up until the day before yesterday. And yes, Drigg is being used in a very, very busy production site.
Now, I realise that "releasing early" is good, but this would have been pushing it. Early, yes, but functional...

Alan is now working on a theme which will integrate perfectly well with Drigg. This is important, becuse otherwise nobody will use it. I also need a bit of a rest from Drigg. So, once Alan's done the theme (give it a week or so, maybe two), I will release the code "properly".

Bye,

Merc.

mercmobily’s picture

mercmobily commented

Hi,

Robert, are you "Merlin"?
I am a little confused by your link.

In any case, I forgot to say:

** THANK YOU **

For the offer.
The code was written in just abouf 11 weeks (simple_karma + drigg). I did my best, but I am sure there's room for improvement.

Bye!

Merc.

robertdouglass’s picture

robertdouglass commented

No, I'm not merlin - that's Earl Miles. I use that link as a quick reference whenever I want to remind myself of how to do releases for the D5 cycle. I think the DRUPAL-5 developer release is a good idea no matter what stage you're at... it is for developers anyway, so nobody expects perfection yet. You can make a DRUPAL_5--1-0-BETA1 later, or even DRUPAL-5--1-0 if you want, and that's an official release, but the developer release just gets the tarball packaged so that you don't exclude people who don't use cvs.

mercmobily’s picture

mercmobily commented

Hi,

OK thanks for the link. I actually stopped the -dev release for simple_karma because I couldn't quite get how it worked with CVS, branching, tagging, etc.

I will try and get it right for Drigg :-D

Merc.

robertdouglass’s picture

robertdouglass commented

you probably want to develop on the DRUPAL-5 branch instead of on HEAD. From Merlin's site:

Now, I’m ready to create a branch because I’m about to update my module to Drupal 5: cvs tag -b DRUPAL-5 which I must immediately follow with cvs update -r DRUPAL-5 or I’ll have created a branch that I’m not using.

So all new changes go into DRUPAL-5. HEAD is as good as useless. Some people use it to be the next branch, whatever it will eventually be. For example, if you decided that you had to rewrite Drigg for D5, and that everything must change, you could use HEAD while still maintaining the DRUPAL-5 branch. Eventually you'd tag the new HEAD code DRUPAL-5--2 and then develop on that.

Or, if you want to upgrade to DRUPAL-6, you could develop on HEAD until it is ready and then tag it DRUPAL-6.

Either way, what HEAD means is up to each developer and I never trust HEAD. It's always good to have a developer branch that gets packaged by the release system.

mercmobily’s picture

mercmobily commented

Hi,

Simple_karma will be obsolete soon. I have rewritten it using the VotingAPIs, which is a _much_ better solution.

Drigg will also be based on the new modules (simple_karma will be split in three different modules).

I will keep you posted.

Bye,

Merc.

mercmobily’s picture

mercmobily commented
Version: » 5.x-1.x-dev
Status: Active » Fixed

Hi,

OK, done.
One question: at this point the HEAD is obsolete. Right now, in head I put a big far warning file, and killed the .module files so that right now HEAD is not functional.

Is this the right way to go?

Anyhow, closing this issue since a DRUPAL-5 branch now exists!

Merc.

mercmobily’s picture

mercmobily commented
Status: Fixed » Closed (fixed)