Closed (fixed)
Project:
Scheduler
Version:
master
Component:
Documentation
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
2 Jul 2013 at 09:16 UTC
Updated:
13 Nov 2014 at 08:16 UTC
Jump to comment: Most recent
This is not a list of requests for enhancements, it is simply a way to record all the issues which are likely to make it into 7.x-1.2
Having this list will (a) make it easier not to miss patches and (b) will provide the data for the new release page when it happens.
Comments
Comment #0.0
jonathan1055 commentedconverted to list and added titles
Comment #0.1
jonathan1055 commentedAdded descriptions, ready for copy and paste later
Comment #0.2
jonathan1055 commentedAdded #1319410
Comment #1
jonathan1055 commentedAdded Rules Integration.
Comment #2
rickmanelius commentedHi jonathan1055! Thanks for this. As soon as all of the "needs review" issues turn RBTC I'll get them in place for people to review and test on the dev branch. If everything is good after 1-2 weeks, we'll release 1.2.
Comment #2.0
rickmanelius commentedAdded Rules and Translation issues
Comment #2.1
jonathan1055 commentedAdded lightweight cron message control
Comment #2.2
jonathan1055 commentedAdded 1804508 - whitespace in formats
Comment #2.3
jonathan1055 commentedAdded 2015415 links in watchdog
Comment #2.4
jonathan1055 commentedAdded 1182450 Sync date fields
Comment #3
jonathan1055 commentedAdded the form pane issue. This is looking good. Just need to get the Rules Integration patch and the Log translatable patch tested now.
There are also three more issues up for review which could well make it into 1.2 if we get testing on them:
#1069668: Default time with user override
#1198788: Editing a published node with "Publishing date/time is required" forces users to set a new "Publish on" date/time
#1566024: Coding Standards and Coder Review
Comment #4
rickmanelius commentedHi Jonathan. If the issues in #3 can get to RBTC by the time the items in the current issue summary are set, then absolutely. Otherwise it might make sense to cut a new release and push to 7.x-1.3 depending on how close they are to ready.
Comment #4.0
rickmanelius commentedAdded 1334780 declare node pane
Comment #5
jonathan1055 commentedI added #1566024: Coding Standards and Coder Review into the summary because I do not think we should release 1.2 without that.
I have also added #1069668: Default time with user override as this issue is fully tested, just needs the patch to be corrected, then I'll mark it RTBC.
#1819074: Allow publish_on dates in the past is nearly ready too.
Jonathan
Comment #5.0
jonathan1055 commentedAdded coding standards and past dates
Comment #5.1
jonathan1055 commentedAdded #1069668: Default time with user override. Issues placed in numerical order
Comment #6
jonathan1055 commentedAdded fieldset config options #1203958: Options to set Scheduler as a fieldset and change the weight
Comment #7
jonathan1055 commentedRemoved Rules as that is not committed yet.
Comment #8
pfrenssenAdded #2115479: Only create cron output html when run from admin form..
Comment #9
jonathan1055 commentedAdded #1198788: Editing a published node with "Publishing date/time is required" forces users to set a new "Publish on" date/time
Comment #10
jonathan1055 commentedAdded #2123223: Improve the configuration page text and add links
Comment #11
jonathan1055 commentedAdded #2123103: Allow more popup formats
Comment #12
jonathan1055 commentedAdded #2011692: Prevent cron errors when scheduled nodes no longer exist and #2128195: Remove redundant database updates
Comment #13
jonathan1055 commentedAdded #1614880: Scheduler shouldn't require a date when clicking the "Delete" button and #2143249: Remove legacy cache_clear_all() in cron
Comment #14
jonathan1055 commentedAdded #1979460: Allow other modules to prevent scheduled nodes from being published / unpublished
Comment #15
jonathan1055 commentedAdded #773510: Integration with Rules module - that is a very powerful addition to Scheduler. Thanks to everyone who contributed.
Comment #16
pfrenssenAdded #2110983: Improve UI functionality for scheduled nodes list. Now there is only #1182450: i18n support - Synchronize scheduled dates in translated nodes left of our list of issues on the project page :) I'm looking forward to making a new release soon, there are lots of really nice improvements.
Comment #17
rickmanelius commentedThat's quite a list. Great job jonathan1055 and pfrenssen!
Comment #18
jkingsnorth commentedA lovely Christmas present.
Comment #19
pfrenssenAdded #2054777: Customizable minute increments for timepicker options.
Comment #20
pfrenssenAdded #2146907: Only show config items when scheduling is enabled.
Comment #21
pfrenssenAdded #2141413: Secure the lightweight cron run page.
Comment #22
pfrenssenGreat news, all our release targets are in! It's time to prepare a new release :)
Next week I have taken a full week off to work on Drupal 8. If possible it would be great if we could release early next week. If any problems arise I will have plenty of time to follow up on it.
What do you guys think?
Comment #23
jonathan1055 commentedFabulous. Yes everything we set for 7.x-1.2 is done. Great effort, thank you. There are no issues still at 'Needs Review' and only two at 'Needs Work' and two active issues listed as 'Bug Report', but these can wait so yes release 1.2 as soon as you like.
Should the old 7.x-1.0-rc1, rc2 and rc3 be removed from the list of releases?
Comment #24
pfrenssenI have tagged the release but I cannot create the release node because of #2132327: Can't create release: git repository tag appears in repo browser, but not vcs tables.
Comment #25
jonathan1055 commentedOK thanks for the info. I am watching that issue too.
Comment #26
jonathan1055 commentedThere has been some good work on #2125405: Not all commits showing up and the missing commits for Scheduler are now being shown at https://drupal.org/node/3292/commits
So hopefully it wont be too long until we can get the 1.2 release which is tagged actually released. Now that I am a maintainer I could try it myself. But maybe I should wait until the -dev release date catches up to the latest commit date of 2nd Jan.
Jonathan
Comment #27
pfrenssenAwesome! I was able to make the new release: https://drupal.org/node/2183869. It should be packaged and become available as a download within 24 hours.
Sorry Jonathan, I was more than willing to give you the honour of making the release, but I saw #2132327: Can't create release: git repository tag appears in repo browser, but not vcs tables pop up green at the top of my queue and went straight to the release page to see if the tag showed up. I was very excited when it did and posted the release straight away. I just saw your post afterwards :-/
Comment #28
pfrenssenIt's live already!
Comment #29
jonathan1055 commentedNo problem Pieter! There will be more releases for me to try. Finally we are up and running with 1.2
Comment #31
jonathan1055 commentedIssues and changes for the next release: #2255165: Enhancements for 7.x-1.3
Comment #32
jonathan1055 commented