Re: my role

> I took a look at the branches and here's how it looks to me in terms 
> of a releasing contributed plugins pack for 1.2.
>
> There are 3 relevant branches
>
> 1. HEAD - this has a few changes that I made to comments related 
> plugins.  These changes need to go into the branch that we use for the 
> plugin pack

Ah this is your domain Ted, so I let you fix this.

> 2. DEVEL - Wari and I check our licensing related changes into this 
> branch.   These changes also need to go into the plugin pack

I've checked in the licensing related changes into PYBLOSXOM_1_2. 
Hopefully I've done the right thing.

> 3. PYBLOSXOM_1_2 - Will checked in his licensing related changes and 
> bugfixes into this branch.  These changes need to go in the plugin 
> pack

Oh yeah, there was so much changes to the plugins, I'm not sure what to 
check in, so I just did licenses. You guys do need to know that I am 
only running pyblosxom 0.9 at work, and am at a loss at the differences 
in changes that are API/plugin related.

>> My understanding was that 1.2 was in maintenance mode and thus all 
>> 1.2 work would be in the PYBLOSXOM_1_2 branch and not in HEAD.  We're 
>> also working on new code for the next release of PyBlosxom.  That new 
>> code is in HEAD or any one of a dozen other branches depending on 
>> who's working on what.  After reading the last few emails, it seems 
>> we're all on different pages in regards to CVS usage.

Will, you are correct about PYBLOSXOM_1_2 being in maintenance mode. 
What I now need to know is does anyone agree on me moving HEAD back to 
a stable version (1.2)? Else we just leave it as it is.

>> I had wanted to put out a contributed plugins pack update for 
>> PyBlosxom 1.2 today, but I don't know what's going on.

I'm not sure what you mean by not knowing what's going on. If you need 
to work on 1.2, then just use PYBLOSXOM_1_2 branch, we've checked in 
the licenses over to the 1.2 branch, and Ted will port over the plugin 
fixes that used to be in HEAD over to the 1_2 branch.

>> But this CVS situation fucking sucks and I don't have time to figure 
>> out what's going on in order to do the things we need to do, like 
>> release a contributed plugins pack for PyBlosxom 1.2 with the changes 
>> that the Debian folks need and various other updates that have 
>> happened over the last week.

Yes Will, but two weeks ago we have HEAD, and there where changes to 
pyblosxom core + some bug fixes for contrib. Will the plugin work for 
pyblosxom core in HEAD, or will it work for 1.2? I for one have no idea 
what's really going on. But I do believe that partitioning/branching 
the CVS in such a way will hopefully fix the kind of headaches we have 
now.

Because we just started this, we are going to have some pain to deal 
with, but it's going to be over soon.

>> As such, I'm dropping back to being an occasional PyBlosxom 
>> contributer. I'll hang out on the mailing lists, but I'm not doing 
>> any more maintainer duties.

I tell you what, I'll maintain the CVS, making sure that the tree don't 
go astray. I will hopefully come up with some CVS guidelines, time 
permitting, but for now I do hope the developers have some idea how one 
is going about this.

BTW, since the CVS branches are still young, we can always go back to 
doing tags and just have HEAD. What say you? I am still waiting for 
answers to:

1. Whether we should go with branches
2. Stick with old ways of doing things
3. If we go branches:
   1. Should HEAD stay where it is
   2. Follow the last stable release
   3. Don't even have a DEVEL

--
Regards: Wari Wahab
Software Development Manager
Celestix Networks, Inc



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click