Author Topic: Beta 3.2  (Read 2095 times)

BrettonWoods

  • Guest
Beta 3.2
« on: August 01, 2013, 10:48:14 pm »
Hi,

I am confused with the current beta version, are we on 3.1 or 3.2?

http://forum.zentyal.org/index.php/topic,15116.msg67313.html#msg67313


robb

  • Guest
Re: Beta 3.2
« Reply #1 on: August 01, 2013, 11:09:57 pm »
Betaversion is now called 3.1. This version will become the next stable version 3.2 in September.
Current stable version is 3.0

Have a look at the release schedule for Zentyal: http://trac.zentyal.org/wiki/ReleasePolicy

BrettonWoods

  • Guest
Re: Beta 3.2
« Reply #2 on: August 01, 2013, 11:31:39 pm »
apols was just confused by the title "Zentyal Server 3.2 Roadmap Published"

It seems to contain things that could not be in 3.1 such as Samba 4.1

Also just struggling initially to find a definitive roadmap of features.

Is this anywhere, many thanks.

BrettonWoods

  • Guest
New Zentyal 3.1-2 (final beta) installer available!
« Reply #3 on: August 05, 2013, 01:50:31 pm »
http://forum.zentyal.org/index.php/topic,17063.msg67429.html#msg67429

Hey firstly the structure of the forum always confuses me.

The Beta announcement is great but I always feel I shouldn't post in the announcement section as that should be zentyal only.

Also when we are posting bugs shouldn't there be a logical divide of version.

The confusion between versions is something that puzzles me anyway :)

I am eager to take the plunge with the final beta in a non production manner.

Initial GPO support for login/logout scripts (to be extended in next releases!)

Can I ask what GPO support is there as do you mean you can edit GPO's in zentyal for login / logout?

I would just use the M$ tools for GPO's is that what you mean but the only functionality supported are scripts?

Bretton

robb

  • Guest
Re: Beta 3.2
« Reply #4 on: August 06, 2013, 10:43:13 am »
The way to go with bugposting is always to use the bugtracker. You can file a bugreport through http://trac.zentyal.org/newticket
You can ask for solutions in the forums, but when it is clearly a bug, a bugreport is the way to go. In the report you can specify the branche and the module affected.

BrettonWoods

  • Guest
Re: Beta 3.2
« Reply #5 on: August 06, 2013, 11:12:52 am »
Many thanks for the orthogonal answer.

I presume you do not know? Anyone else?