On Thursday, March 6, 2003, at 07:33 AM, pero wrote:


Sounds good. Are there any schedules or a release plan for
1.3.1 1.3.2 and 1.4?

By next monday evening (GMT) I'd like to have 1.3.1 release, 1.3.2rc1 and 1.4rc1 out the door.



 Will 1.5 be the one that may break
backwards compatibility?

Gosh, I hope not.


Will the Map-Support go into 1.4?


We can discuss that. I think that it should go into 1.5, because 1.4 should be 1.3 with improvements to introspection stuff, and adds a few other features. No reason to delay it further.


A whole bunch of questions, I know :)


Not that many :)


Meanwhile a +1 for me.


great!


Peter

Here's what I think we should do to get code out and
contributions in :

1) I'll branch the 1.3.1rc2 tag on the 1.3 branch and  to do a 1.3.1
release.  I think it's important to release that as-is, pre
the patches
from Dan.

2) the recent commits on 1.3.1rc2 will go as a 1.3.2, to RC
and get it
out because Dan committed those for a reason, and I'm sure he needs a
release of it.

3) the current head will become 1.4rc1 and move that as our primary
release target to get a v1.4 out there.

4) patches go into head, which will be 1.5-dev

--
Geir Magnusson Jr                                   203-956-2604(w)
Adeptra, Inc.                                       203-434-2093(m)
[EMAIL PROTECTED]                                   203-247-1713(m)


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


--
Geir Magnusson Jr                                   203-956-2604(w)
Adeptra, Inc.                                       203-434-2093(m)
[EMAIL PROTECTED]                                   203-247-1713(m)


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to