<div dir="ltr">Hi Frank,<div><br></div><div>thanks for the explanation. Makes sense :+1: </div><div><br></div><div>Have a nice weekend.</div><div><br></div><div>Morris</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
2013/10/5 Frank Karlitschek <span dir="ltr"><<a href="mailto:frank@owncloud.org" target="_blank">frank@owncloud.org</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yes. That's an option. But there are 2 problems with that.<br>
<br>
1. We have a ton of bugs to fix for ownCloud 6. If we branch now than we have to do this in two places (or three if stable5 backporting is needed.) This is unnecessary work.<br>
<br>
2. I really want to motivate people with helping to stabilize and bugfix ownCloud 6. If we open up master for feature development now than no one will care about the next stable release and all the users with bugs. We have over 700 open issues for core alone at the moment. We have to bring this significantly down before the ownCloud 6 release and before we start to work on ownCloud 7 features.<br>
<br>
I hope that makes sense.<br>
<span class="HOEnZb"><font color="#888888"><br>
Frank<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
On 05.10.2013, at 11:29, Morris Jobke <<a href="mailto:morris.jobke@gmail.com">morris.jobke@gmail.com</a>> wrote:<br>
<br>
> Hi Frank,<br>
><br>
> my thought about the release management was the following:<br>
><br>
> If the feature freeze is in action an new stable branch is splitted of. So nobody can merge new features by accident. Pending pull request haven't to be stalled and can merged into master, because the new stable branch is already there. And if it's a fix it has to be backported in the usual way (mentioning you and ask if this is a backport critical fix - cherry pick the stuff and just put in on top of the stable6 branch). How were ready to merge pull request (that includes features not fixes) handled in previous releases?<br>
><br>
> Sorry for my question - I just want to learn best practises :)<br>
><br>
> Morris<br>
><br>
><br>
> 2013/10/5 Frank Karlitschek <<a href="mailto:frank@owncloud.org">frank@owncloud.org</a>><br>
> Hi Morris,<br>
><br>
> we are now in feature freeze. This means that no more feature commits are allowed from now on.<br>
> This also means that the real fun part begins now which is testing and bugfixing during the alpha/beta/RC cycle. :-)<br>
><br>
> We are branching a stable6 branch when we are very near the ownCloud 6 final release. In the meantime everyone should concentrate on fixing and polishing the code in master as much as possible.<br>
><br>
> Let me know if you have more questions :-)<br>
><br>
> Frank<br>
><br>
><br>
> On 04.10.2013, at 23:52, Morris Jobke <<a href="mailto:morris.jobke@gmail.com">morris.jobke@gmail.com</a>> wrote:<br>
><br>
> > Hi Frank,<br>
> ><br>
> > Is there now a stable6 branch, or how is this handled?<br>
> ><br>
> > Best regards,<br>
> > Morris<br>
> ><br>
> ><br>
> > 2013/9/18 Frank Karlitschek <<a href="mailto:frank@owncloud.org">frank@owncloud.org</a>><br>
> > Hi guys,<br>
> ><br>
> > unfortunately we are running late with some features especially the improved public API. We are making great progress bu we also need time to port the apps. Because of that we are moving the feature freeze by 2 week.<br>
> ><br>
> ><br>
> > The new schedule is:<br>
> ><br>
> > Oct. 4th Feature freeze. All new features has to be merged by then. Please submit your pull requests as soon as possible so that the reviewers have time to review and to give you feedback. If you are working on bigger features please inform me as soon as possible.<br>
> ><br>
> > Oct. 7th Release ownCloud 6 alpha 1<br>
> ><br>
> > Oct. 14th Release ownCloud 6 alpha 2<br>
> ><br>
> > Oct. 21th Release ownCloud 6 beta 1 Only important bugfixes are allowed from now on.<br>
> ><br>
> > Oct. 28th Release ownCloud 6 RC 1 Only showstopper bugfixes are allowed from now on.<br>
> ><br>
> > Nov. 5th Release ownCloud 6 final.<br>
> ><br>
> ><br>
> > I hope that works for everyone.<br>
> ><br>
> ><br>
> > Frank<br>
> ><br>
> ><br>
> > On 25.08.2013, at 13:40, Frank Karlitschek <<a href="mailto:frank@owncloud.org">frank@owncloud.org</a>> wrote:<br>
> ><br>
> > > Hi guys,<br>
> > ><br>
> > > it is time to plan the ownCloud 6 release schedule. We are already late with this release because we spend quite some time for QA of ownCloud 5. This has to and will be better this time.<br>
> > ><br>
> > > The plan is:<br>
> > ><br>
> > > Sep. 20th Feature freeze. All new features has to be merged by then. Please submit your pull requests as soon as possible so that the reviewers have time to review and to give you feedback. If you are working on bigger features please inform me as soon as possible.<br>
> > ><br>
> > > Sep. 23th Release ownCloud 6 alpha 1<br>
> > ><br>
> > > Sep. 30th Release ownCloud 6 alpha 2<br>
> > ><br>
> > > Oct. 7th Release ownCloud 6 beta 1 Only important bugfixes are allowed from now on.<br>
> > ><br>
> > > Oct. 14th Release ownCloud 6 RC 1 Only showstopper bugfixes are allowed from now on.<br>
> > ><br>
> > > Oct. 22th Release ownCloud 6 final.<br>
> > ><br>
> > > The final release date might be moved depending on the quality that we reached until then.<br>
> > ><br>
> > > Let me know if you have any questions.<br>
> > ><br>
> > ><br>
> > > Frank<br>
> ><br>
> > _______________________________________________<br>
> > Owncloud mailing list<br>
> > <a href="mailto:Owncloud@kde.org">Owncloud@kde.org</a><br>
> > <a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>
> ><br>
> > _______________________________________________<br>
> > Owncloud mailing list<br>
> > <a href="mailto:Owncloud@kde.org">Owncloud@kde.org</a><br>
> > <a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>
><br>
> _______________________________________________<br>
> Owncloud mailing list<br>
> <a href="mailto:Owncloud@kde.org">Owncloud@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>
><br>
> _______________________________________________<br>
> Owncloud mailing list<br>
> <a href="mailto:Owncloud@kde.org">Owncloud@kde.org</a><br>
> <a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>
<br>
_______________________________________________<br>
Owncloud mailing list<br>
<a href="mailto:Owncloud@kde.org">Owncloud@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/owncloud" target="_blank">https://mail.kde.org/mailman/listinfo/owncloud</a><br>
</div></div></blockquote></div><br></div>