Hi, 2010/2/11 Jean-Peer Lorenz <peer....@gmx.net>: > Hi, > > in order to document the schedule feature I had a deeper look into it > and discovered some issues I want to discuss: The currently implemented > scheduling doesn't work properly and is quite confusing/messy. > > I've fixed some obvious bugs related to this so far: > > * I moved the 'max. incremental backups in days' from the time tab/page > to the general page since this is not related to scheduling at all.
Can you give me a screenshot of what the general page became? I was thinking of moving settings to that page, but I was scared that I would become cluttered. BTW, be careful about this bug: https://bugs.launchpad.net/nssbackup/+bug/364833 . > * I disabled the scheduling for non-default profiles since they can > overwrite schedule settings made in the default profile and this can be > very confusing. Good point! > * I fixed some issues with updating of the cron services. > Very well ! I knew that in some cases it wasn't working. > These changes are not pushed upstream so far. > The schedule feature is indeed messy. I didn't really take the time to review it correctly. I am happy that you could review it and simplify it. > > What I intend to do for the series 0.2 is to simplify the schedule UI > even more: > > * I suggest to remove the *precise* settings for > hourly/daily/weekly/monthly backups completely from the UI. I think we > should keep only the *simple* settings and the custom setting. The > reason is that precise scheduling is always loaded as a custom setting > (when opening such configuration again) and this is hard to fix in > series 0.2. For average users a simple setting on a > hourly/daily/weekly/monthly base would be sufficient and experienced > users (assuming they know what a cronline is) can still define their own > custom setting. There are better ways that should be implemented > (crontab) for later releases and it is not necessary to spend too much > effort to fix this in 0.2 since it keeps a hack and lacks support for > non-root users. > I agree on the not so big difference between custom and precise. Removing precise will simplify a lot the code. > * Moreover, I suggest to simplify the general backup settings on the > main page. The current implementation is buggy and misleading. My idea > is to remove the radio button for 'Manual backups only' completely and > to keep only the choices for 'recommended' and 'custom' backups. I think > this is much clearer than it is now. The problem that remains is that > for non-root users we cannot set up daily backups as a recommended > setting in 0.2. So, either we also modify the description for > 'recommended settings' on the main page for non-root users or remove it > completely. > > In general: > * For release 0.2 we should provide a simple but working application as > fast as possible and then implement new features like scheduling for > root/non-root users in 0.3. This means, we should not try to fix every > aspect in 0.2 rather making it working well (even if some features a > missing or get cut) and then go on with the development of the project > (I really want to see the notification working in a release - this would > be a huge improvement in usability ;-) > Agree. I didn't want to take that decision because I moved to RC. But we can rip off buggy features and release. Then move them in 0.3. -- Oumar Aziz OUATTARA _______________________________________________ Mailing list: https://launchpad.net/~nssbackup-team Post to : nssbackup-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~nssbackup-team More help : https://help.launchpad.net/ListHelp
