Re: [Avogadro-devel] Avogadro 2 release number simplification/jump

[Geoffrey Hutchison]

> I assume it won't get to there, but it makes sense to plan for it.
..
> GNOME for example starts with X.90 from their release candidates I
> think.

I agree 100% with starting from 1.90, which I think indicates "not quite 2.0" 
nicely. I once made a 1.100 release for Open Babel, I don't think anyone was 
"up in arms."

I also would like to think that we can get to "2.0" within 10 releases, 
considering we have several people trying to make an active push.

Let's make sure we keep this updated, though:
http://wiki.openchemistry.org/Avogadro_Roadmap

-Geoff
--
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
___
Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

Re: [Avogadro-devel] Avogadro 2 release number simplification/jump

[Marcus D. Hanwell]

On Wed, May 11, 2016 at 3:49 PM, Michael Banck  wrote:
> On Wed, May 11, 2016 at 03:43:19PM -0400, Marcus D. Hanwell wrote:
>> So I had one or two queries recently that made me realize I should
>> have done a better job on less ambiguous version numbering for
>> Avogadro 2 releases. I would like to make the next Avogadro 2 release
>> 1.90, and then after that 1.91, 1.92, 1.93, etc until we feel good
>> with sticking a 2.0 release out.
>
> What's the plan after 1.99?
>
> I assume it won't get to there, but it makes sense to plan for it.
> Calling it 1.100 wouldn't be a problem in my opinion, but if you don't
> like it now, maybe 1.90 isn't the best starting point.

I am fine with 1.100, but hope not to get there. I think it gives us a
good amount of space, I can start at 80 if people have feelings either
way. I am fine going up to 1.1000, but sincerely doubt we need that
many release numbers.

Marcus

--
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
___
Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

Re: [Avogadro-devel] Avogadro 2 release number simplification/jump

[Michael Banck]

On Wed, May 11, 2016 at 03:43:19PM -0400, Marcus D. Hanwell wrote:
> So I had one or two queries recently that made me realize I should
> have done a better job on less ambiguous version numbering for
> Avogadro 2 releases. I would like to make the next Avogadro 2 release
> 1.90, and then after that 1.91, 1.92, 1.93, etc until we feel good
> with sticking a 2.0 release out.

What's the plan after 1.99?

I assume it won't get to there, but it makes sense to plan for it.
Calling it 1.100 wouldn't be a problem in my opinion, but if you don't
like it now, maybe 1.90 isn't the best starting point.

GNOME for example starts with X.90 from their release candidates I
think.


Michael

--
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
___
Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/avogadro-devel

[Avogadro-devel] Avogadro 2 release number simplification/jump

[Marcus D. Hanwell]

Hi,

So I had one or two queries recently that made me realize I should
have done a better job on less ambiguous version numbering for
Avogadro 2 releases. I would like to make the next Avogadro 2 release
1.90, and then after that 1.91, 1.92, 1.93, etc until we feel good
with sticking a 2.0 release out.

This avoids repeating previous Avogadro release numbers, such as
0.8.0, 0.9.0, etc. It is also in line with several other projects that
use .90+ for releases before the next major version increment, and it
makes it clear that there are API changes in each release. Not much to
be done about previous releases.

I hope with our Google Summer of Code students, and general energy
around landing features we can get a few good releases out over the
summer. I would like to promote Avogadro 2 as a tool, and achieve
parity where features/polish are missing.

Thanks,

Marcus

--
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
___
Avogadro-devel mailing list
Avogadro-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/avogadro-devel