+1000000 for a github where we can submit code changes that can be integrated! We have like 5 modules
which only fix bugs for certain shop versions, just because a bug takes several versions until it really gets fixed
(because devs have to write it by theirselves and not only test our patches)
--

mit freundlichen Grüßen
Alexander Kludt


__________________________
Phone: 09283-5925453
Fax: 09283-592671
Skype: kingschnulli
Email: [email protected]
Website: www.aggrosoft.de

__________________________
Aggrosoft it intelligence GbR
Tannstrasse 12
95111 Rehau
GERMANY

Sitz Rehau, Amtsgericht Hof
Steuernummer: 223/165/54508
Ust.-Id. Nr. gemäß § 27 a Umsatzsteuergesetz: DE260722773

___________________________
Diese Nachricht ist nur für den Empfänger () bestimmt, sollten
Sie nicht der Empfänger sein löschen Sie diese Nachricht
umgehend und geben Sie uns bitte per Email ([email protected]) Bescheid
über den fälschlichen Erhalt.





Dave J. Holloway
16. Juli 2012 16:25

Hi OXIDians,

Now and again, I program something / write a module to fix a bug and
would like to suggest my changes so that they can be considered for
integration in the OXID-Core / next OXID-Release.

Currently, there is only the opportunity to do this via email / the
forum / the bugtracker etc. (correct me if I am wrong), where I can post
and hope that someone reads/understands and integrates whatever I post.
This doesn't seem to be a terribly efficient workflow and, from what I
can see, there haven't been many notable contributions from the
community since the introduction of CE except for Joscha's downloadable
products in 4.6 (again, correct me if I'm wrong).

So, my question:

Is there, or will there be in the future, the possibility to check out
OXID-CE using a distributed VCS like GIT or HG? I personally think it
would be great for the community if something like this existed, as it
would allow the following workflow:


1) OXID offers a read-only clonable repository e.g.
http://git.oxid-esales.com/

2) A 3rd-party programmer checks out the repository, makes a new branch
for his bugfix.

3) The bugfix is tested by the programmer.

4) Once finished, the programmer posts either a request to pull to
dev-general, stating the public address to his GIT-Clone, i.e.
http://git.my-pretend-company.com/oxid and his bugfix branch name, or
sends an e-mail formatted patch directly to the list.

5) Anyone on the group can pull and test his changes / make comments.

6) The OXID-Devs recieve his message and pull his changes into their
working copies.

7) The changes get tested / tidied-up / unit-tested / put through
OXID-QA etc. etc.

8) Changes get integrated in the next release.

9) OXID Devs are happy, because they don't have to fix the bug themselves.

All of this could be done without needing external hosters such as
GitHub/BitBucket and changes would only be integrated if the original
author agrees to dual-license his/her code (so that it can be used in
CE/PE/EE etc.).


Any thoughts, advantages/disadvantages?


Regards

Dave

_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

Reply via email to