[RFC] version number for development release

Hi guys, I asked what the versioning should look like for the upcoming development release?! Should I name it 1.3.0 or then 1.3.1 for the stabilized version or 1.3.0rc1? Opinions and votes please! I think we have to sync more faster with our development release plans. It should be more of

Re: [RFC] version number for development release

Citando Stipe Tolj [EMAIL PROTECTED]: Hi guys, I asked what the versioning should look like for the upcoming development release?! Should I name it 1.3.0 or then 1.3.1 for the stabilized version or 1.3.0rc1? Just tag it as 1.3.0. If it's a development branch, it doesn't need to be stable.

Re: [RFC] version number for development release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I agree with Bruno. +1 from me (if I may to vote?)... On Saturday 04 January 2003 16:34, Bruno David Simões Rodrigues wrote: Citando Stipe Tolj [EMAIL PROTECTED]: Hi guys, I asked what the versioning should look like for the upcoming

Re: [RFC] version number for development release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 04 January 2003 18:08, Stipe Tolj wrote: Alexander Malysh wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I agree with Bruno. +1 from me (if I may to vote?)... as this is an open source project everyone is invited

Re: [RFC] version number for development release

Alexander Malysh wrote: It's _simple_ , I do not like rc for development release ;) now that's an opinion. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: