0.7 / 1.0 Release discussion

[Bruce Kroeze]

I think it is time for a release discussion.

First, I think the next release should really be 1.0.  I dislike the conservative approach where open source projects are reluctant to call a release 1.0.  Why is that?  For example, everyone knows Django 0.96 is de facto 1.0.  A major release is simply a point at which the group agrees "This is the base feature set.  Any point releases are going to be backward compatible."

I submit that we have reached that point.  Yes there is work to do, a few bugs to fill in, but that shouldn't stop us from declaring the API frozen for 1.0 and releasing.

Looking at the ticket list, I only see one feature I'd like to put in (Gift Certificates), and that's in final test on my dev box.  Everything else (from my quick scan) appears to be incremental improvements or not-gonna-happen-immediately.

Discussion?

Any "must haves" I missed for 0.7/1.0?  Any real resistance to 1.0?  Silly or not, 1.0 has major psychological weight behind it.  It will cause us to get much more attention and energy into the project.

Thanks,
Bruce Kroeze
http://solidsitesolutions.com
Dynamic Designs, Optimized

[Chris Moffitt]

I agree that we should start planning for the next release.  In light of some of the discussions in the other threads and the direction we are probably going to go, it's probably a smart idea to go ahead and call it a 1.0.  Some of the major things we need to do could be backwards incompatible and time consuming so providing a clean break makes sense.

There are a few smaller things I'd like to work on and gift certificates would be handy.  Other than that, I'm not sure that there are any major features that need to make it into 1.0.

There is probably some pretty big documentation work that needs to happen.  So, any suggestions or offers of help would be much appreciated.



-Chris

[Neum]

I'd be happy to help with the documentation where I could. Let me
know how I could help.

Neum

[Peter Baumgartner]

>
> There is probably some pretty big documentation work that needs to happen.
> So, any suggestions or offers of help would be much appreciated.
>

I'd suggest starting by thoroughly documenting everything in the code
with docstrings. They can be used w/Django's admin documentation and
extrapolated to external documents down the road.

--
Pete

[Chris Moffitt]

Any "must haves" I missed for 0.7/1.0?  Any real resistance to 1.0?  Silly or not, 1.0 has major psychological weight behind it.  It will cause us to get much more attention and energy into the project.

One thing I've been thinking about adding is support for 3rd party shippers (like UPS, FedEx, etc).  I don't think it will be too tough to do so I was thinking maybe I should pick one and get it integrated before 1.0.  My thought is that once we have one done, we should be fairly stable on the API (I already know of 1 model change we'll probably need for any shipper).  Before I started working on it though, I wanted to see if anyone had already started something.  If not, I'll probably tackle UPS as my example.

Any thoughts?

-Chris

[Marcin Chojnowski]

On 31/12/2007, Chris Moffitt <ch...@moffitts.net> wrote:
> (I already know of 1 model change we'll probably need for any shipper).
> Before I started working on it though, I wanted to see if anyone had already
> started something. If not, I'll probably tackle UPS as my example.

Great idea.

Martin