Bug 36055 - Release notes for UCS 4
Release notes for UCS 4
Status: CLOSED FIXED
Product: UCS manual
Classification: Unclassified
Component: Release Notes
unspecified
Other Linux
: P5 normal (vote)
: UCS 4.0
Assigned To: Stefan Gohmann
Alexander Kläser
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-10-06 14:26 CEST by Stefan Gohmann
Modified: 2015-04-01 13:49 CEST (History)
0 users

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Gohmann univentionstaff 2014-10-06 14:26:24 CEST
The release notes for UCS 4 should be created.
Comment 1 Stefan Gohmann univentionstaff 2014-11-07 22:24:38 CET
Profil-based installation will be available later: Bug #35537
Comment 3 Alexander Kläser univentionstaff 2014-11-15 09:11:58 CET
I made some minor stylistic adaptations and copied the updated text for Piwik from the manual.

What I found confusing is the usage of MDB. I added the sentence that LDAP will not be updated automatically to MDB. But what is necessary to do in order to change the backend? Simply setting the UCR variable and resarting LDAP? This should be said somewhere.

The long lists of Bugs for the installer and the update to Debhelber9/Python 2.7 look IMHO way too long and thus too important. Not sure whether this can be changed easily, however, it's no real blocker.

Maybe the very detailed information from Bug 31907 should go into an SDB?

r55837.
Comment 4 Stefan Gohmann univentionstaff 2014-11-15 17:35:32 CET
(In reply to Alexander Kläser from comment #3)
> I made some minor stylistic adaptations and copied the updated text for
> Piwik from the manual.

OK

> What I found confusing is the usage of MDB. I added the sentence that LDAP
> will not be updated automatically to MDB. But what is necessary to do in
> order to change the backend? Simply setting the UCR variable and resarting
> LDAP? This should be said somewhere.

Yes, that's part of the performance guide. I added the reference to the performance guide in the changelog entry. But I removed your sentence from the highlights. The highlights should only give an overview, no instructions.

> The long lists of Bugs for the installer and the update to Debhelber9/Python
> 2.7 look IMHO way too long and thus too important. Not sure whether this can
> be changed easily, however, it's no real blocker.
> 
> Maybe the very detailed information from Bug 31907 should go into an SDB?

We are planning more changes in the password handling. Let's wait and see ...
 
> r55837.

OK, very good!
Comment 5 Stefan Gohmann univentionstaff 2014-11-15 17:37:08 CET
(In reply to Stefan Gohmann from comment #4)
> > What I found confusing is the usage of MDB. I added the sentence that LDAP
> > will not be updated automatically to MDB. But what is necessary to do in
> > order to change the backend? Simply setting the UCR variable and resarting
> > LDAP? This should be said somewhere.
> 
> Yes, that's part of the performance guide. I added the reference to the
> performance guide in the changelog entry. But I removed your sentence from
> the highlights. The highlights should only give an overview, no instructions.

r55844
Comment 6 Alexander Kläser univentionstaff 2014-11-17 13:09:33 CET
(In reply to Stefan Gohmann from comment #5)
> (In reply to Stefan Gohmann from comment #4)
> > > What I found confusing is the usage of MDB. I added the sentence that LDAP
> > > will not be updated automatically to MDB. But what is necessary to do in
> > > order to change the backend? Simply setting the UCR variable and resarting
> > > LDAP? This should be said somewhere.
> > 
> > Yes, that's part of the performance guide. I added the reference to the
> > performance guide in the changelog entry. But I removed your sentence from
> > the highlights. The highlights should only give an overview, no instructions.
> 
> r55844

OK.