[Owncloud] Releases and stuff

[Thomas Müller]

Hi Tanghus,
hi community,

thanks a lot for taking the time to write this email and sum it all up!
I - more or less - have not much to add and fully agree with you.

Regarding the release cycle I'd like to propose a less time driven approach for OC5.
Afaik we have a lot of issues with sharing within OC4 and MTGap was rewritting the sharing
mechanisms in order to solve all these issues.

If I got MTGap right he will merge his changes to master by the end of this month.
We shall focus on testing this functionality to the bone as far as possible (from my point of view 
unit tests are very welcome to ensure the functionality over time).

Do we have some kind of wiki/doc/blog what ever to see which scenarios the new api shall handle (and which not?)?
I would have liked to see some concept paper on that in advance, but well .......

I'd propose to release OC5 after we are confident that the stuff is working.
And finally let's get back to the old habit of releasing RCs with a public testing phase of a week or so.
In case it takes a bunch of RCs - who cares? Linus released RC7 for Linux 3.5 recently ;-)

Gentlemen (ladies - is there any?) - it has been a preasure to worl with you in the past month and I'm looking 
forward to the next coming years and I'm looking forward to meet you on the next dev meeting.

Take care,

Tom aka DeepDiver



Am Mittwoch, dem 18.07.2012 um 2:00 schrieb Thomas Tanghus:
> Since a release is supposed to be somewhere in the not so distant future, I 
> would like to bring up the subject of how this is to be handled. It is no big 
> secret that the 4.0 release gave us some bad cred, maybe not so much on the 
> corporate side (which I'm blissfully ignorant of), but definitely amongst 
> other FLOSS developers.
> 
> It's quite possible that I have missed some messages or posts, even though I 
> try to follow what's going on, but soon we're a month into the next 3ish month 
> release schedule, and we should really have an overview of what's supposed to 
> be in that release - and not as the odd blog post, but as a plan you can refer 
> to and revise when needed.
> 
> It's not that I don't enjoy the opportunities and freedom to learn you guys 
> have given me to pick up when the Contacts app needed a maintainer. It came at 
> a time much needed for me personally to get up from a deep abyss and try to do 
> something constructive again, but now I have also come to the point where I 
> feel deep pride in the whole ownCloud project, and would be sad if we should 
> get another cycle of picking up the pieces of great things that just needed 
> the final touches before they were released.
> 
> I have told some of you how my situation is: I burned out seriously a decade 
> ago with consequences I don't want to describe here, so I'm in no position to 
> take more responsibilities than i have already given myself.
> 
> So, I don't want to mention the usual stuff about us missing HCI specialists, 
> designers, translators or writers; IMHO we're actually doing pretty good there 
> and I hear very few complaints in those areas yet (wink, wink JanC ;) ), what 
> I really think we need now is:
> 
> - A dedicated sysadm.
> 
> - A release dude.
> 
> If we could fill out those positions the poor sods in them would very quickly 
> give us an overview of what other responsibilities needs to be delegated.
> 
> Oh, and another time, please remind me not to write long mails when I have 
> decided Tuesday is weekend ;)
> 
> -- 
> Med venlig hilsen / Best Regards
> 
> Thomas Tanghus
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud