Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
#97 2014-09-22 08:25:47
- candyman
- Member
- From: Italy
- Registered: 2006-08-08
- Posts: 684
Re: Situation report for Textpattern 4.6 and beyond
I’ve discovered gaekwad’s TXP demo site and tryed out the 4.6 dev.
Apparently itss similar to current 4.5 with a more clean/user friendly admin interface.
Anyway it seems almost finished and I don’t see any major improvements (media management and so on) from TXP 4.5.x.
So, if can I ask, what is the release problem?
Must we wait for some brand new features or are there problems or other kind (plugin compatibility and so on)?
Just to know, TXP 4.5.7 is already excellent for my needs.
Last edited by candyman (2014-09-22 08:30:02)
Offline
Re: Situation report for Textpattern 4.6 and beyond
There is no release problem, we are just working on several different pieces of the system, none of which are ready for release as yet.
For example my admin side UI changes are being worked on independently of the core, and will only be rolled in once I’m happy with them, and they are stable enough.
In terms of codebase changes version 4.6 probably has the most extensive revisions in Textpattern’s history, even if some of those are not immediately apparent to end users at this point of in time.
Offline
Re: Situation report for Textpattern 4.6 and beyond
Hello core team !
Some news about Textpattern 4.6 ?
Offline
#100 2015-02-14 11:15:40
Re: Situation report for Textpattern 4.6 and beyond
Yeah, would be great to get some insights into the developing process. A new blog post might be a good idea. Even if there are no big news, it’s always nice to hear from the developers.
“HaHa. Your medium is dying.” –Nelson Muntz, Springfield.
Offline
#101 2015-04-28 21:01:39
Re: Situation report for Textpattern 4.6 and beyond
I just spent a long time searching the forum on how to contribute. It’s not very clear – at least for me.
There’s a Github repository. Ok.
I forked it and cloned my fork. Ok.
Then I tried the readme file, it describes installation for the end-user. Then the contributing file, which gives short instructions.
I didn’t find any practical information, such as
- who can contribute (anyone, I guess)
- and how:
- is it as simple as “clone, chose an issue, make your changes, submit a pull request”?
- are there issues to address first?
- if I’m about to work on one of them, do I have to inform someone (who? how?) or even ask for permission?
A simple but explicit guide is missing and my feeling is that it can prevent people from daring to contribute.
Last edited by CeBe (2015-04-29 06:24:14)
Offline
#102 2015-04-29 03:53:59
Offline
#103 2015-04-29 06:39:24
Re: Situation report for Textpattern 4.6 and beyond
wet wrote #290277:
I’ve added few bits there.
Yes :) Thank you! (Of course I forked before cloning, I edited my previous message)
Help with translations is a good point.
So here comes another question: is it really necessary to create a new branch? Fork+pull request seems sufficient and easier to manage, or do I miss something?
Offline
#104 2015-04-29 08:00:09
Re: Situation report for Textpattern 4.6 and beyond
You can just fork and pull if patch is fairly minor. A new branch is suitable for more extensive changes.
Offline
#105 2015-05-01 10:11:25
Re: Situation report for Textpattern 4.6 and beyond
philwareham wrote #290283:
You can just fork and pull if patch is fairly minor. A new branch is suitable for more extensive changes.
I may be picky (sorry…): what criteria determine what is “fairly minor”, or “more extensive”?
A good practice may be to:
- look into the issue if it is identified as minor or not, or even if it is clearly mentioned to create a new branch
- if not (or if in doubt), create locally a new branch, and merge (or rebase?) if it finally happens to be a minor change.
I don’t feel very comfortable yet with git, I hope I haven’t written foolishness.
Offline
#106 2015-05-01 11:02:37
Re: Situation report for Textpattern 4.6 and beyond
I’d say if it’s up to a dozen lines or so of a bug fix or changes to docs such as README then there is no real need to create a branch for that. New features or larger patches then create a branch.
Maybe we should clarify it somehow in the CONTRIBUTING file.
Offline
#107 2015-05-09 16:31:46
Re: Situation report for Textpattern 4.6 and beyond
I’m new to Git (and Github). What caught me by surprise is that when you create a branch, do some edits and then issue a pull request, commits you do after the pull request on that same branch also become part of the pull request.
Offline