You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Paul Lindner <li...@inuus.com> on 2009/07/23 20:03:34 UTC
[VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Hi,
We solved 263 issues:https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310741&styleName=Html&version=12313552
There are still a couple of issues left in
JIRA:https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310741&status=1
(Note remaining 1.1-BETA1 issues will be moved to 1.1-BETA2 upon approval)
Staging repo:https://repository.apache.org/content/repositories/shindig-staging-023/
Web site:http://incubator.apache.org/shindig/
Vote open for 72 hours.
[ ] +1
[ ] +0
[ ] -1
---------------------------------------------
Sub-task
- [SHINDIG-403 <https://issues.apache.org/jira/browse/SHINDIG-403>]
- Replace usage of java.net.URI with org.apache.shindig.common.url.Url
- [SHINDIG-730 <https://issues.apache.org/jira/browse/SHINDIG-730>]
- Activity Paging
- [SHINDIG-736 <https://issues.apache.org/jira/browse/SHINDIG-736>]
- Clarify timing of callback execution in JS API
- [SHINDIG-739 <https://issues.apache.org/jira/browse/SHINDIG-739>]
- Data Pipelining
- [SHINDIG-740 <https://issues.apache.org/jira/browse/SHINDIG-740>]
- Gadgets Log
- [SHINDIG-742 <https://issues.apache.org/jira/browse/SHINDIG-742>]
- International Date Time Number Formatting
- [SHINDIG-744 <https://issues.apache.org/jira/browse/SHINDIG-744>]
- Limited Invalidation
- [SHINDIG-745 <https://issues.apache.org/jira/browse/SHINDIG-745>]
- Messaging API Changes
- [SHINDIG-747 <https://issues.apache.org/jira/browse/SHINDIG-747>]
- OAuth Popup
- [SHINDIG-752 <https://issues.apache.org/jira/browse/SHINDIG-752>]
- Proxied Content
- [SHINDIG-821 <https://issues.apache.org/jira/browse/SHINDIG-821>]
- Improve plugins version and configuration in POMs
- [SHINDIG-830 <https://issues.apache.org/jira/browse/SHINDIG-830>]
- Add shindig-common-tests to dependencyManagement and generate
sources
Bug
- [SHINDIG-158 <https://issues.apache.org/jira/browse/SHINDIG-158>]
- Reloading when using postMessage causes RPC errors
- [SHINDIG-179 <https://issues.apache.org/jira/browse/SHINDIG-179>]
- Metadata servlet does not return all possible ModulePrefs
- [SHINDIG-423 <https://issues.apache.org/jira/browse/SHINDIG-423>]
- hardcoded fields in shindig container.js
- [SHINDIG-459 <https://issues.apache.org/jira/browse/SHINDIG-459>]
- Shindig GadgetSpec returns invalid XML with UserPrefs and EnumValue
- [SHINDIG-479 <https://issues.apache.org/jira/browse/SHINDIG-479>]
- Character set detection is EXPENSIVE using ICU4J.
- [SHINDIG-575 <https://issues.apache.org/jira/browse/SHINDIG-575>]
- Dynamic height (adjustHeight) feature doesn't work reliably
- [SHINDIG-585 <https://issues.apache.org/jira/browse/SHINDIG-585>]
- OpenSocial template tests need to be automated
- [SHINDIG-593 <https://issues.apache.org/jira/browse/SHINDIG-593>]
- incoming GET requests should not have their body inspected in
handleSingleRequest during REST processing
- [SHINDIG-632 <https://issues.apache.org/jira/browse/SHINDIG-632>]
- Fix for mishandling of the <select> tag by template compiler.
- [SHINDIG-649 <https://issues.apache.org/jira/browse/SHINDIG-649>]
- OST: Fix some whitespace issues on IE, use
gadgets.util.registerOnLoadHandler when available
- [SHINDIG-654 <https://issues.apache.org/jira/browse/SHINDIG-654>]
- Injecting feature javascript into head breaks caja
- [SHINDIG-671 <https://issues.apache.org/jira/browse/SHINDIG-671>]
- setUserPref problems in gadgets.js
- [SHINDIG-689 <https://issues.apache.org/jira/browse/SHINDIG-689>]
- JavaScript error from IE during tab abjustment
- [SHINDIG-693 <https://issues.apache.org/jira/browse/SHINDIG-693>]
- Shindig's content rewriting changes @type attribute of <script> tag
- [SHINDIG-695 <https://issues.apache.org/jira/browse/SHINDIG-695>]
- HttpResponse's externalizable implementation not works on Linux/Unix
systems
- [SHINDIG-708 <https://issues.apache.org/jira/browse/SHINDIG-708>]
- Typos in gadgets.js
- [SHINDIG-715 <https://issues.apache.org/jira/browse/SHINDIG-715>]
- Legacy JSON calls replaced in gadgets.js
- [SHINDIG-718 <https://issues.apache.org/jira/browse/SHINDIG-718>]
- Building shindig from behind a proxy fails
- [SHINDIG-761 <https://issues.apache.org/jira/browse/SHINDIG-761>]
- HttpResponseBuilder.setExpirationTime() has wrong signature and
Javadoc
- [SHINDIG-763 <https://issues.apache.org/jira/browse/SHINDIG-763>]
- isAnonymous check for OAuthSecurityToken doesn't look right
- [SHINDIG-764 <https://issues.apache.org/jira/browse/SHINDIG-764>]
- opensocial model interface does not support UNSTRUCTURED
- [SHINDIG-765 <https://issues.apache.org/jira/browse/SHINDIG-765>]
- BasiHttpFetcher does not set a read timeout and connection timeout
is hardcoded to 5 seconds(not configurable)
- [SHINDIG-772 <https://issues.apache.org/jira/browse/SHINDIG-772>]
- unneccessary backport-concurrent references in shindig code
- [SHINDIG-773 <https://issues.apache.org/jira/browse/SHINDIG-773>]
- Persist ActivityDb Fails with NullPointerException
- [SHINDIG-776 <https://issues.apache.org/jira/browse/SHINDIG-776>]
- Features Javascript has lots and lots of jslint errors
- [SHINDIG-777 <https://issues.apache.org/jira/browse/SHINDIG-777>]
- Fix JsonDb for People Service
- [SHINDIG-779 <https://issues.apache.org/jira/browse/SHINDIG-779>]
- Fix JsonDb for app data service
- [SHINDIG-780 <https://issues.apache.org/jira/browse/SHINDIG-780>]
- implement requestShareApp as a gadgets.rpc callback
- [SHINDIG-787 <https://issues.apache.org/jira/browse/SHINDIG-787>]
- Name field of Person and Address should be "formatted", not
"unstructured"
- [SHINDIG-789 <https://issues.apache.org/jira/browse/SHINDIG-789>]
- Wrong SCM url in the branch and other fixes
- [SHINDIG-790 <https://issues.apache.org/jira/browse/SHINDIG-790>]
- Regex fix to ${} detection in Opensocial Templates
- [SHINDIG-791 <https://issues.apache.org/jira/browse/SHINDIG-791>]
- GadgetSpec substitution does not copy attributes
- [SHINDIG-793 <https://issues.apache.org/jira/browse/SHINDIG-793>]
- Invalid getter method is called when getter method to have one or
more args is exists
- [SHINDIG-794 <https://issues.apache.org/jira/browse/SHINDIG-794>]
- Features mistakenly copied to /features
- [SHINDIG-798 <https://issues.apache.org/jira/browse/SHINDIG-798>]
- "updated" xs:element missing from opensocial.xsd for Activity
- [SHINDIG-813 <https://issues.apache.org/jira/browse/SHINDIG-813>]
- console.log() found in JS
- [SHINDIG-815 <https://issues.apache.org/jira/browse/SHINDIG-815>]
- missing new for Exception constructor
- [SHINDIG-819 <https://issues.apache.org/jira/browse/SHINDIG-819>]
- distributionManagement in the parent POM should use the ASF servers
- [SHINDIG-824 <https://issues.apache.org/jira/browse/SHINDIG-824>]
- Samples Services are brokn by paging, build mvn -Psamples clean
install fails.
- [SHINDIG-829 <https://issues.apache.org/jira/browse/SHINDIG-829>]
- Ability to extend AbstractLargeRestfulTests and access private
fields
- [SHINDIG-834 <https://issues.apache.org/jira/browse/SHINDIG-834>]
- Relocate xstream dependency
- [SHINDIG-836 <https://issues.apache.org/jira/browse/SHINDIG-836>]
- Wrong parsing of boolean values
- [SHINDIG-839 <https://issues.apache.org/jira/browse/SHINDIG-839>]
- Argument error when MessageBundleParser::parse an error xml
- [SHINDIG-841 <https://issues.apache.org/jira/browse/SHINDIG-841>]
- JsonDbOpensocialService doesn't support startindex/count when
getActivities
- [SHINDIG-842 <https://issues.apache.org/jira/browse/SHINDIG-842>]
- DataRequestHandler confuses CREATE and UPDATE
- [SHINDIG-845 <https://issues.apache.org/jira/browse/SHINDIG-845>]
- Basic HTTP Fetcher should always set Content-Length header
- [SHINDIG-847 <https://issues.apache.org/jira/browse/SHINDIG-847>]
- Duplicate message bundle names cause IllegalArgumentExceptions
- [SHINDIG-848 <https://issues.apache.org/jira/browse/SHINDIG-848>]
- core.io/io.js does not look at the return code from the request
- [SHINDIG-849 <https://issues.apache.org/jira/browse/SHINDIG-849>]
- MakeRequestHandler should not try to do anything with the response
body if return code is != 200
- [SHINDIG-852 <https://issues.apache.org/jira/browse/SHINDIG-852>]
- Chained syntax in proxy doesn't support URLs with query arguments
- [SHINDIG-853 <https://issues.apache.org/jira/browse/SHINDIG-853>]
- userpref is not internationalize correctly
- [SHINDIG-859 <https://issues.apache.org/jira/browse/SHINDIG-859>]
- NullPointerException when locked domain verification fails
- [SHINDIG-866 <https://issues.apache.org/jira/browse/SHINDIG-866>]
- Samples project fails to build
- [SHINDIG-867 <https://issues.apache.org/jira/browse/SHINDIG-867>]
- Caja API change
- [SHINDIG-869 <https://issues.apache.org/jira/browse/SHINDIG-869>]
- Ignore SVN files in shindig-features-XXX.jar
- [SHINDIG-870 <https://issues.apache.org/jira/browse/SHINDIG-870>]
- Improve logging uses when running tests
- [SHINDIG-873 <https://issues.apache.org/jira/browse/SHINDIG-873>]
- Fixed neko test on windows
- [SHINDIG-879 <https://issues.apache.org/jira/browse/SHINDIG-879>]
- Undefined field being used. JS function not following pattern of
other functions
- [SHINDIG-885 <https://issues.apache.org/jira/browse/SHINDIG-885>]
- Incorrect totalResults calculation in PersonServiceDb and ActivityDb
- [SHINDIG-886 <https://issues.apache.org/jira/browse/SHINDIG-886>]
- Samples build fails due to removed classes still being referenced
- [SHINDIG-887 <https://issues.apache.org/jira/browse/SHINDIG-887>]
- processContent can get called twice with 'profile' as the view,
causing the gadget to be rendered twice.
- [SHINDIG-898 <https://issues.apache.org/jira/browse/SHINDIG-898>]
- Recent refactoring checkin has broken Samples java project
- [SHINDIG-900 <https://issues.apache.org/jira/browse/SHINDIG-900>]
- Malformed javascript causes the CajaContentRewriter to append
original javascript
- [SHINDIG-901 <https://issues.apache.org/jira/browse/SHINDIG-901>]
- io.js is missing OAUTH_USE_TOKEN in RequestParameters
- [SHINDIG-903 <https://issues.apache.org/jira/browse/SHINDIG-903>]
- Example html files have incorrect javascript path
- [SHINDIG-907 <https://issues.apache.org/jira/browse/SHINDIG-907>]
- Proxy servlet returns an invalid response when original response
headers contain 'Transfer-Encoding: chunked'
- [SHINDIG-908 <https://issues.apache.org/jira/browse/SHINDIG-908>]
- Latest move to protocol package has broken samples project
- [SHINDIG-909 <https://issues.apache.org/jira/browse/SHINDIG-909>]
- Fix unittests which are failed
- [SHINDIG-915 <https://issues.apache.org/jira/browse/SHINDIG-915>]
- Ampersands in attributes not handled properly by Neko HTML parser
code
- [SHINDIG-917 <https://issues.apache.org/jira/browse/SHINDIG-917>]
- Samples project fails to build
- [SHINDIG-919 <https://issues.apache.org/jira/browse/SHINDIG-919>]
- Commit of SHINDIG-918 failed to add new files
- [SHINDIG-924 <https://issues.apache.org/jira/browse/SHINDIG-924>]
- Should not allow registration of two features with the same name
- [SHINDIG-925 <https://issues.apache.org/jira/browse/SHINDIG-925>]
- Meaningless regular expression
- [SHINDIG-929 <https://issues.apache.org/jira/browse/SHINDIG-929>]
- Invalid example configuration
- [SHINDIG-930 <https://issues.apache.org/jira/browse/SHINDIG-930>]
- Unable to autoload exceptions
- [SHINDIG-931 <https://issues.apache.org/jira/browse/SHINDIG-931>]
- Sample Container example doesn't work
- [SHINDIG-932 <https://issues.apache.org/jira/browse/SHINDIG-932>]
- 400 Bad Request due to repeated header
- [SHINDIG-933 <https://issues.apache.org/jira/browse/SHINDIG-933>]
- JsonSerializer doesn't serialize dates as valid xs:date or
xs:dateTime
- [SHINDIG-934 <https://issues.apache.org/jira/browse/SHINDIG-934>]
- Gadgets without oauth tag will fail.
- [SHINDIG-937 <https://issues.apache.org/jira/browse/SHINDIG-937>]
- Legacy _IG_Prefs.getString/Array methods should return unescaped
prefs
- [SHINDIG-939 <https://issues.apache.org/jira/browse/SHINDIG-939>]
- java shindig build fails due to test failure in
CSSContentRewriterTest.java
- [SHINDIG-941 <https://issues.apache.org/jira/browse/SHINDIG-941>]
- Add xmlns attributes to <response> tags per the XSD
- [SHINDIG-951 <https://issues.apache.org/jira/browse/SHINDIG-951>]
- setFieldImpl does not handle boolean false values
- [SHINDIG-952 <https://issues.apache.org/jira/browse/SHINDIG-952>]
- Wrong phpDoc comments
- [SHINDIG-953 <https://issues.apache.org/jira/browse/SHINDIG-953>]
- CSS rewriting stripping URL for background-image and creating broken
link tags.
- [SHINDIG-956 <https://issues.apache.org/jira/browse/SHINDIG-956>]
- Substituter doesn't properly handle odd number of preceding
underscores for hangman variables
- [SHINDIG-957 <https://issues.apache.org/jira/browse/SHINDIG-957>]
- ImageRewriter can return 0-byte responses
- [SHINDIG-958 <https://issues.apache.org/jira/browse/SHINDIG-958>]
- RenderingContentRewriterTest: NPE in Gadget.sanitizeOutput
- [SHINDIG-960 <https://issues.apache.org/jira/browse/SHINDIG-960>]
- Error on removal of canonicaldb json binding in GuiceModule for data
service implementation of open social interfaces
- [SHINDIG-962 <https://issues.apache.org/jira/browse/SHINDIG-962>]
- secureToken in gadgets.js missing an expected value
- [SHINDIG-965 <https://issues.apache.org/jira/browse/SHINDIG-965>]
- JsonSerializer does not handle POJOs in JSONArrays correctly
- [SHINDIG-966 <https://issues.apache.org/jira/browse/SHINDIG-966>]
- token over-decoding
- [SHINDIG-968 <https://issues.apache.org/jira/browse/SHINDIG-968>]
- Typo in GadgetFeatureRegistryTest.java
- [SHINDIG-971 <https://issues.apache.org/jira/browse/SHINDIG-971>]
- JsonRpcServlet should set content type to json in all cases,
including gets and error cases.
- [SHINDIG-974 <https://issues.apache.org/jira/browse/SHINDIG-974>]
- OAuth body signing does not work in Shindig and the specification is
unclear
- [SHINDIG-975 <https://issues.apache.org/jira/browse/SHINDIG-975>]
- Bug while loading apps in IE
- [SHINDIG-982 <https://issues.apache.org/jira/browse/SHINDIG-982>]
- the build is broken
- [SHINDIG-983 <https://issues.apache.org/jira/browse/SHINDIG-983>]
- NekoSerializer.printStartElement() is outputting empty attributes in
a way that isn't XML compliant
- [SHINDIG-985 <https://issues.apache.org/jira/browse/SHINDIG-985>]
- BeanJsonConverter converting getters from the interface and not the
underlying injected class
- [SHINDIG-987 <https://issues.apache.org/jira/browse/SHINDIG-987>]
- NekoParser returns cryptic error messages when parsing bad html
- [SHINDIG-991 <https://issues.apache.org/jira/browse/SHINDIG-991>]
- Make ServletTestFixture abstract to avoid misuse
- [SHINDIG-993 <https://issues.apache.org/jira/browse/SHINDIG-993>]
- beanJsonConverter throws NPE when converting empty map to object
- [SHINDIG-998 <https://issues.apache.org/jira/browse/SHINDIG-998>]
- Requests for jobs/schools fields result in errors
- [SHINDIG-1000
<https://issues.apache.org/jira/browse/SHINDIG-1000>] - Add license
file and readme for Rhino js.jar in features/bin
- [SHINDIG-1001
<https://issues.apache.org/jira/browse/SHINDIG-1001>] - Pipelined data
not loaded for proxied renders for "default' view
- [SHINDIG-1006
<https://issues.apache.org/jira/browse/SHINDIG-1006>] - AuthType was
not always being saved/maintained, IgnoreCache flag not always used,
OAuth parameter Nonce not generated
- [SHINDIG-1009
<https://issues.apache.org/jira/browse/SHINDIG-1009>] - content-type
check should only be perfomed on "request" field of
multipart/form-data
- [SHINDIG-1013
<https://issues.apache.org/jira/browse/SHINDIG-1013>] -
BasicHttpFetcher is referencing the wrong response header to determine
content encoding
- [SHINDIG-1016
<https://issues.apache.org/jira/browse/SHINDIG-1016>] - Empty-string
UserPref values resolve to default values
- [SHINDIG-1017
<https://issues.apache.org/jira/browse/SHINDIG-1017>] - Fatal error
with samplecontainer
- [SHINDIG-1024
<https://issues.apache.org/jira/browse/SHINDIG-1024>] - missing file
- [SHINDIG-1025
<https://issues.apache.org/jira/browse/SHINDIG-1025>] - Fixes
canonicaldb.json file. php json_decode can't process the json filed
that doesn't have quotes.
- [SHINDIG-1026
<https://issues.apache.org/jira/browse/SHINDIG-1026>] - fix signing
fetcher warning for empty path
- [SHINDIG-1029
<https://issues.apache.org/jira/browse/SHINDIG-1029>] -
BasicHttpFetcher.java doesn't recognize java settings for proxy -
http.proxyHost, http.proxyPort
- [SHINDIG-1032
<https://issues.apache.org/jira/browse/SHINDIG-1032>] - Evaluate,
prioritize and fix findbugs issues
- [SHINDIG-1034
<https://issues.apache.org/jira/browse/SHINDIG-1034>] - fix rest entry
for cache invalidation
- [SHINDIG-1035
<https://issues.apache.org/jira/browse/SHINDIG-1035>] - makeRequest
with httpMethod=POST should automatically set Content-Type
- [SHINDIG-1037
<https://issues.apache.org/jira/browse/SHINDIG-1037>] - Use
createTextNode when creating javascript/css text node.
- [SHINDIG-1041
<https://issues.apache.org/jira/browse/SHINDIG-1041>] - add oauth
argumets support for OAuthFetcher
- [SHINDIG-1047
<https://issues.apache.org/jira/browse/SHINDIG-1047>] - Build Broken,
Javascript test issue?
- [SHINDIG-1048
<https://issues.apache.org/jira/browse/SHINDIG-1048>] -
opensocial-templates container.js has comments that, somehow, are
getting interpreted
- [SHINDIG-1054
<https://issues.apache.org/jira/browse/SHINDIG-1054>] - cannot
applying multiple fields in restful api with oauth arguments
- [SHINDIG-1058
<https://issues.apache.org/jira/browse/SHINDIG-1058>] - partuza
implementation for 0.9 message api change.
- [SHINDIG-1063
<https://issues.apache.org/jira/browse/SHINDIG-1063>] -
ContainerConfig.php regex parses out valid parts of container.js,
throws "Failed to json_decode the container configuration"
- [SHINDIG-1064
<https://issues.apache.org/jira/browse/SHINDIG-1064>] - exception when
json_decode container.js
- [SHINDIG-1067
<https://issues.apache.org/jira/browse/SHINDIG-1067>] - Return default
appId when it is not specified in the request.
- [SHINDIG-1068
<https://issues.apache.org/jira/browse/SHINDIG-1068>] - Some tests
fail when building with IBM's JVM
- [SHINDIG-1069
<https://issues.apache.org/jira/browse/SHINDIG-1069>] - Posting "="
collapses makeRequest
- [SHINDIG-1070
<https://issues.apache.org/jira/browse/SHINDIG-1070>] - MessageHander
doesn't respond to Fields
- [SHINDIG-1071
<https://issues.apache.org/jira/browse/SHINDIG-1071>] - Message Field
enumeration doesn't include 'status'
- [SHINDIG-1073
<https://issues.apache.org/jira/browse/SHINDIG-1073>] - Image resizing
bugfixes
- [SHINDIG-1074
<https://issues.apache.org/jira/browse/SHINDIG-1074>] - ifpc and nix
RPC transports are broken in non-same-origin situation
- [SHINDIG-1075
<https://issues.apache.org/jira/browse/SHINDIG-1075>] -
DefaultHandlerRegistry.getRestHandler throws an NPE for unregistered
paths
- [SHINDIG-1076
<https://issues.apache.org/jira/browse/SHINDIG-1076>] -
SocialMarkupHtmlParser breaks the document order of comments
- [SHINDIG-1079
<https://issues.apache.org/jira/browse/SHINDIG-1079>] - os:DataRequest
not working in "text/os-data" script blocks
- [SHINDIG-1082
<https://issues.apache.org/jira/browse/SHINDIG-1082>] - Logged (but
dropped) exception when data pipelining can't find a social token
- [SHINDIG-1084
<https://issues.apache.org/jira/browse/SHINDIG-1084>] - Shindig REST
returns a 500 internal server error for invalid JSON
- [SHINDIG-1087
<https://issues.apache.org/jira/browse/SHINDIG-1087>] - Removes
makeRequest post data check.
- [SHINDIG-1088
<https://issues.apache.org/jira/browse/SHINDIG-1088>] - Message api
change.
- [SHINDIG-1089
<https://issues.apache.org/jira/browse/SHINDIG-1089>] - Fix XML and
Entry part for Shindig output
- [SHINDIG-1102
<https://issues.apache.org/jira/browse/SHINDIG-1102>] -
JsLibraray.java has a bug
- [SHINDIG-1103
<https://issues.apache.org/jira/browse/SHINDIG-1103>] - The bug is
that DOMDocument->loadHtml will remove tages like </b> in script.
- [SHINDIG-1105
<https://issues.apache.org/jira/browse/SHINDIG-1105>] -
src/gadgets/oauth/BasicGadgetOAuthTokenStore.php:24: private
$OAUTH_CONFIG = "../config/oauth.json";
- [SHINDIG-1106
<https://issues.apache.org/jira/browse/SHINDIG-1106>] - ProxyHandler
fetch/fetchJson methods always returns 404 on error
- [SHINDIG-1108
<https://issues.apache.org/jira/browse/SHINDIG-1108>] - IE8 issues
with wpm RPC mechanism
- [SHINDIG-1111
<https://issues.apache.org/jira/browse/SHINDIG-1111>] - override host
name when behind a reverse proxy
- [SHINDIG-1113
<https://issues.apache.org/jira/browse/SHINDIG-1113>] - param_location
strings don't align spec
- [SHINDIG-1114
<https://issues.apache.org/jira/browse/SHINDIG-1114>] - param_location
always get parsed as default by wrong switch
- [SHINDIG-1117
<https://issues.apache.org/jira/browse/SHINDIG-1117>] - Lists returned
for JSON-RPC do not include all properties
- [SHINDIG-1119
<https://issues.apache.org/jira/browse/SHINDIG-1119>] - Signed Request
has 2 issues
- [SHINDIG-1120
<https://issues.apache.org/jira/browse/SHINDIG-1120>] - RDF parsing
fails
- [SHINDIG-1123
<https://issues.apache.org/jira/browse/SHINDIG-1123>] - makeRequest
not using preloaded data
Improvement
- [SHINDIG-222 <https://issues.apache.org/jira/browse/SHINDIG-222>]
- More respect of ASF rules
- [SHINDIG-253 <https://issues.apache.org/jira/browse/SHINDIG-253>]
- clarify GadgetFeatureRegistry locking
- [SHINDIG-308 <https://issues.apache.org/jira/browse/SHINDIG-308>]
- Always concatenate CSS files together.
- [SHINDIG-401 <https://issues.apache.org/jira/browse/SHINDIG-401>]
- Improve URI handling throughout the code base.
- [SHINDIG-580 <https://issues.apache.org/jira/browse/SHINDIG-580>]
- Authentication filter doesnt distinguish between no authentication
and invalid authentication
- [SHINDIG-634 <https://issues.apache.org/jira/browse/SHINDIG-634>]
- Updating version of Caja
- [SHINDIG-668 <https://issues.apache.org/jira/browse/SHINDIG-668>]
- Paging support for Activities
- [SHINDIG-675 <https://issues.apache.org/jira/browse/SHINDIG-675>]
- Security token does not expose the authentication mechanism used to
generate it
- [SHINDIG-678 <https://issues.apache.org/jira/browse/SHINDIG-678>]
- Autoloader chain
- [SHINDIG-687 <https://issues.apache.org/jira/browse/SHINDIG-687>]
- Small fixes to OS Templates
- [SHINDIG-700 <https://issues.apache.org/jira/browse/SHINDIG-700>]
- Upgrade to Guice 2.0
- [SHINDIG-702 <https://issues.apache.org/jira/browse/SHINDIG-702>]
- Add a new Constructor in MessageBundle.jar.
- [SHINDIG-725 <https://issues.apache.org/jira/browse/SHINDIG-725>]
- Improve POM to use correctly maven-remote-resources-plugin
- [SHINDIG-726 <https://issues.apache.org/jira/browse/SHINDIG-726>]
- Include tests jar in build
- [SHINDIG-762 <https://issues.apache.org/jira/browse/SHINDIG-762>]
- First pass at implementing DataPipelining on the client
- [SHINDIG-766 <https://issues.apache.org/jira/browse/SHINDIG-766>]
- Add HTML code for links in javadoc
- [SHINDIG-767 <https://issues.apache.org/jira/browse/SHINDIG-767>]
- PropertiesModule should be able to property files other than the
default
- [SHINDIG-774 <https://issues.apache.org/jira/browse/SHINDIG-774>]
- Upgrade to google collections 0.8
- [SHINDIG-782 <https://issues.apache.org/jira/browse/SHINDIG-782>]
- Unit tests for samples implementation of PersonService,
ActivityService and AppDataService
- [SHINDIG-785 <https://issues.apache.org/jira/browse/SHINDIG-785>]
- Fully implement samples implementation of PersonService,
ActivityService and AppDataService
- [SHINDIG-788 <https://issues.apache.org/jira/browse/SHINDIG-788>]
- Use ImmutableSet.of in DataRequestHandler
- [SHINDIG-792 <https://issues.apache.org/jira/browse/SHINDIG-792>]
- UrlParameterAuthenticationHandler is not extensible
- [SHINDIG-797 <https://issues.apache.org/jira/browse/SHINDIG-797>]
- PropertiesModule not extensible enough
- [SHINDIG-799 <https://issues.apache.org/jira/browse/SHINDIG-799>]
- Update the website content
- [SHINDIG-801 <https://issues.apache.org/jira/browse/SHINDIG-801>]
- Modify HTTP request pipeline to support composition.
- [SHINDIG-802 <https://issues.apache.org/jira/browse/SHINDIG-802>]
- Using org.apache.commons.io.IOUtils#closeQuietly()
- [SHINDIG-804 <https://issues.apache.org/jira/browse/SHINDIG-804>]
- implement toString for UserId and GroupId
- [SHINDIG-806 <https://issues.apache.org/jira/browse/SHINDIG-806>]
- Move Javascript in the features directory in a better location
- [SHINDIG-807 <https://issues.apache.org/jira/browse/SHINDIG-807>]
- Metadata to return OAuth Services
- [SHINDIG-808 <https://issues.apache.org/jira/browse/SHINDIG-808>]
- Duplicate EasyMockTestCase class
- [SHINDIG-809 <https://issues.apache.org/jira/browse/SHINDIG-809>]
- Some test classes should extends EasyMockTestCase instead of
TestCase
- [SHINDIG-812 <https://issues.apache.org/jira/browse/SHINDIG-812>]
- [PATCH] Attach gadgets.window.adjustHeight to the onresize event
- [SHINDIG-814 <https://issues.apache.org/jira/browse/SHINDIG-814>]
- Improve spec compliance of data pipelining
- [SHINDIG-820 <https://issues.apache.org/jira/browse/SHINDIG-820>]
- Make UTF-8 the default encoding for the build
- [SHINDIG-825 <https://issues.apache.org/jira/browse/SHINDIG-825>]
- tools-maven-plugin should fail if legal files are missing
- [SHINDIG-827 <https://issues.apache.org/jira/browse/SHINDIG-827>]
- Allow Maven reporting
- [SHINDIG-828 <https://issues.apache.org/jira/browse/SHINDIG-828>]
- Move all resources in a resources directory
- [SHINDIG-832 <https://issues.apache.org/jira/browse/SHINDIG-832>]
- Fix compilation warning
- [SHINDIG-833 <https://issues.apache.org/jira/browse/SHINDIG-833>]
- Improve Java code and performance
- [SHINDIG-835 <https://issues.apache.org/jira/browse/SHINDIG-835>]
- Fi x SVN properties
- [SHINDIG-838 <https://issues.apache.org/jira/browse/SHINDIG-838>]
- Improve exceptions when a file doesn't exist
- [SHINDIG-843 <https://issues.apache.org/jira/browse/SHINDIG-843>]
- Upgrade to Caja r3164
- [SHINDIG-851 <https://issues.apache.org/jira/browse/SHINDIG-851>]
- Return WWW-Authenticate headers where appropriate
- [SHINDIG-854 <https://issues.apache.org/jira/browse/SHINDIG-854>]
- OAuth miscellaneous bugs
- [SHINDIG-855 <https://issues.apache.org/jira/browse/SHINDIG-855>]
- Enum value should be checked if it is empty
- [SHINDIG-856 <https://issues.apache.org/jira/browse/SHINDIG-856>]
- Defaults to Content@type="html" when omitted
- [SHINDIG-857 <https://issues.apache.org/jira/browse/SHINDIG-857>]
- public key id param key should be xoauth_public_key
- [SHINDIG-864 <https://issues.apache.org/jira/browse/SHINDIG-864>]
- Upgrade to XStream 1.3.1
- [SHINDIG-871 <https://issues.apache.org/jira/browse/SHINDIG-871>]
- Shindig's Java build script should validate the correct Java version
- [SHINDIG-874 <https://issues.apache.org/jira/browse/SHINDIG-874>]
- Restful integration tests for samples implementation of
PersonService, ActivityService and AppDataService
- [SHINDIG-881 <https://issues.apache.org/jira/browse/SHINDIG-881>]
- Support expressions in ContainerConfig
- [SHINDIG-883 <https://issues.apache.org/jira/browse/SHINDIG-883>]
- The SecurityToken class has a getAppUrl() method. HttpGadgetContext
should use it
- [SHINDIG-888 <https://issues.apache.org/jira/browse/SHINDIG-888>]
- Reduce json output by making isOwner/isViewer implicitly false
- [SHINDIG-892 <https://issues.apache.org/jira/browse/SHINDIG-892>]
- Bump oauth java lib from core-20080621 to oauth-core-20090121
- [SHINDIG-893 <https://issues.apache.org/jira/browse/SHINDIG-893>]
- Generify REST and RPC protocol handling
- [SHINDIG-894 <https://issues.apache.org/jira/browse/SHINDIG-894>]
- Provide image rewriting support for latency improvements
- [SHINDIG-896 <https://issues.apache.org/jira/browse/SHINDIG-896>]
- Simplified content sanitizer.
- [SHINDIG-897 <https://issues.apache.org/jira/browse/SHINDIG-897>]
- Add 3-legged OAuth validation support for RESTful api
- [SHINDIG-899 <https://issues.apache.org/jira/browse/SHINDIG-899>]
- DOM based CSS rewriting and CSS sanitization
- [SHINDIG-904 <https://issues.apache.org/jira/browse/SHINDIG-904>]
- Update PersonService to help support 0.9 Spec filter options
- [SHINDIG-914 <https://issues.apache.org/jira/browse/SHINDIG-914>]
- Better logging of RpcInvocationHandler and RestInvocationHandler
exceptions in DefaultHandlerRegistry
- [SHINDIG-918 <https://issues.apache.org/jira/browse/SHINDIG-918>]
- Change to PersonHandler to allow filtering of requests - 0.9
improvement
- [SHINDIG-920 <https://issues.apache.org/jira/browse/SHINDIG-920>]
- Small improvement to Generics of FutureUtil
- [SHINDIG-921 <https://issues.apache.org/jira/browse/SHINDIG-921>]
- CacheMemcache replace dynamic connection with static?
- [SHINDIG-927 <https://issues.apache.org/jira/browse/SHINDIG-927>]
- Check for existence of config/local.php in include path
- [SHINDIG-940 <https://issues.apache.org/jira/browse/SHINDIG-940>]
- Remove apache commons logging calls in favor of JUL
- [SHINDIG-964 <https://issues.apache.org/jira/browse/SHINDIG-964>]
- Google Collections 0.9 Upgrade with Multimap Headers
- [SHINDIG-969 <https://issues.apache.org/jira/browse/SHINDIG-969>]
- Need convenience method to get all required features of a gadget.
- [SHINDIG-973 <https://issues.apache.org/jira/browse/SHINDIG-973>]
- Memcache pconnect should be optional
- [SHINDIG-979 <https://issues.apache.org/jira/browse/SHINDIG-979>]
- Default social-api bindings should not include sample code
- [SHINDIG-990 <https://issues.apache.org/jira/browse/SHINDIG-990>]
- Add executed() post operation method to HandlerExecutionListener
- [SHINDIG-994 <https://issues.apache.org/jira/browse/SHINDIG-994>]
- Add Sample implementation of OAuth authentication/authorization
- [SHINDIG-995 <https://issues.apache.org/jira/browse/SHINDIG-995>]
- Use OAuthProblemException for OAuthDataStore
- [SHINDIG-999 <https://issues.apache.org/jira/browse/SHINDIG-999>]
- prefferedUsername into included int Person
- [SHINDIG-1007
<https://issues.apache.org/jira/browse/SHINDIG-1007>] - Conditional
tags supoprt, var precedence, moving JST branch into Shindig codebase
- [SHINDIG-1015
<https://issues.apache.org/jira/browse/SHINDIG-1015>] - Allow
transitively-required locked-domain feature to enable locked-domain
- [SHINDIG-1018
<https://issues.apache.org/jira/browse/SHINDIG-1018>] -
BasicHttpFetcher hard-codes the connection timeout
- [SHINDIG-1022
<https://issues.apache.org/jira/browse/SHINDIG-1022>] - Use separate
domain names for iframes on sample container
- [SHINDIG-1023
<https://issues.apache.org/jira/browse/SHINDIG-1023>] - Find a way to
include assembly/samples modules by default when doing a release
- [SHINDIG-1027
<https://issues.apache.org/jira/browse/SHINDIG-1027>] - Address
problems with three-legged OAuth identified by Advisory 2009-1
- [SHINDIG-1031
<https://issues.apache.org/jira/browse/SHINDIG-1031>] - Improve test
coverage for shindig-common module
- [SHINDIG-1033
<https://issues.apache.org/jira/browse/SHINDIG-1033>] - Allow global
setting of forced libs
- [SHINDIG-1036
<https://issues.apache.org/jira/browse/SHINDIG-1036>] - Bring client
side templates up to latest spec
- [SHINDIG-1046
<https://issues.apache.org/jira/browse/SHINDIG-1046>] - Client-side
template bugfixes and library support improvement
- [SHINDIG-1049
<https://issues.apache.org/jira/browse/SHINDIG-1049>] -
requestSendMessage should use the RPC mechanism as similar features do
- [SHINDIG-1050
<https://issues.apache.org/jira/browse/SHINDIG-1050>] - Implement
active-relay-less transport for non-window.postMessage WebKit browsers
- [SHINDIG-1053
<https://issues.apache.org/jira/browse/SHINDIG-1053>] - rpc.js
getRelayUrl throws an exception if called for a target that is not
configured.
- [SHINDIG-1057
<https://issues.apache.org/jira/browse/SHINDIG-1057>] - [PATCH]
Samples project
- [SHINDIG-1060
<https://issues.apache.org/jira/browse/SHINDIG-1060>] - Update the FAQ
- [SHINDIG-1066
<https://issues.apache.org/jira/browse/SHINDIG-1066>] - Allow
MakeRequestHandler to be subclassed
- [SHINDIG-1078
<https://issues.apache.org/jira/browse/SHINDIG-1078>] - [patch] throw
Error("") should be used insead of throw "" in JavaScripts
- [SHINDIG-1080
<https://issues.apache.org/jira/browse/SHINDIG-1080>] - Bump shindig
to google-collections 1.0-rc2
- [SHINDIG-1081
<https://issues.apache.org/jira/browse/SHINDIG-1081>] - Allow others
to extend BlobCrypterSecurityToken
- [SHINDIG-1086
<https://issues.apache.org/jira/browse/SHINDIG-1086>] - Upgrade to
ehcache 1.6.0
- [SHINDIG-1091
<https://issues.apache.org/jira/browse/SHINDIG-1091>] - Improves open
proxy transparent and BGR image handling
- [SHINDIG-1092
<https://issues.apache.org/jira/browse/SHINDIG-1092>] - Bump java
oauth libs to 20090531
- [SHINDIG-1095
<https://issues.apache.org/jira/browse/SHINDIG-1095>] - Upgrade to
json-lib 2.2.2
- [SHINDIG-1097
<https://issues.apache.org/jira/browse/SHINDIG-1097>] - Upgrade to
juel 2.1.2
- [SHINDIG-1107
<https://issues.apache.org/jira/browse/SHINDIG-1107>] - Clean up
shindig dependencies
New Feature
- [SHINDIG-560 <https://issues.apache.org/jira/browse/SHINDIG-560>]
- Add support for @supportedFields
- [SHINDIG-629 <https://issues.apache.org/jira/browse/SHINDIG-629>]
- partial client-side code for Message support
- [SHINDIG-635 <https://issues.apache.org/jira/browse/SHINDIG-635>]
- Add a new method to SecurityToken - getContainer()
- [SHINDIG-696 <https://issues.apache.org/jira/browse/SHINDIG-696>]
- Data pipelining support for proxied gadget renders
- [SHINDIG-889 <https://issues.apache.org/jira/browse/SHINDIG-889>]
- allow multiple javascript modules to register with configuration
- [SHINDIG-923 <https://issues.apache.org/jira/browse/SHINDIG-923>]
- Implementation of OS Lite for 0.9
- [SHINDIG-1003
<https://issues.apache.org/jira/browse/SHINDIG-1003>] - Proxied image
resizing
- [SHINDIG-1008
<https://issues.apache.org/jira/browse/SHINDIG-1008>] - PHP + Caja
Integration
- [SHINDIG-1040
<https://issues.apache.org/jira/browse/SHINDIG-1040>] - php shindig
message api change for spec 0.9
- [SHINDIG-1055
<https://issues.apache.org/jira/browse/SHINDIG-1055>] - add javascript
support for opensocial.invalidateCache()
- [SHINDIG-1099
<https://issues.apache.org/jira/browse/SHINDIG-1099>] - Spec 0.9 album
php shindig implementation
- [SHINDIG-1109
<https://issues.apache.org/jira/browse/SHINDIG-1109>] - Supports
anonymous viewer in PHP Shindig
Question
- [SHINDIG-623 <https://issues.apache.org/jira/browse/SHINDIG-623>]
- Policy on copying a "snapshot" of open-source dependency into the
Shindig codebase
Task
- [SHINDIG-283 <https://issues.apache.org/jira/browse/SHINDIG-283>]
- Find a place to put documentation
- [SHINDIG-1062
<https://issues.apache.org/jira/browse/SHINDIG-1062>] - Upload Shindig
Logo
- [SHINDIG-1093
<https://issues.apache.org/jira/browse/SHINDIG-1093>] - Fix remaining
issues identified in 1.0 release process.
Test
- [SHINDIG-221 <https://issues.apache.org/jira/browse/SHINDIG-221>]
- Add an AllTests suite for running tests from Eclipse
- [SHINDIG-630 <https://issues.apache.org/jira/browse/SHINDIG-630>]
- enable JsUnit tests for non-Firefox browsers
- [SHINDIG-710 <https://issues.apache.org/jira/browse/SHINDIG-710>]
- EndToEnd test for message bundle substitution
- [SHINDIG-837 <https://issues.apache.org/jira/browse/SHINDIG-837>]
- Be sure to delete temp file on exit
- [SHINDIG-1056
<https://issues.apache.org/jira/browse/SHINDIG-1056>] -
BasicRemoteContentTest doesn't depend on static private key file
- [SHINDIG-1059
<https://issues.apache.org/jira/browse/SHINDIG-1059>] -
CacheMemcacheTest file depend on php have loaded memchache extension
- [SHINDIG-1094
<https://issues.apache.org/jira/browse/SHINDIG-1094>] - Add test code
to test activity feature is good
Wish
- [SHINDIG-669 <https://issues.apache.org/jira/browse/SHINDIG-669>]
- Add an encryptWithIV helper method
-
Re: [VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Posted by Paul Lindner <li...@inuus.com>.
Okay, looks like you're addressing some of the issues. I'll work on
figuring out why the checksums are failing.
On Sat, Jul 25, 2009 at 5:45 AM, Vincent Siveton <vs...@apache.org>wrote:
> -1 due to major issues:
> * a lot of CHECKSUM FAILED when using this repo.
> * In [1], shindig-1.1-BETA1-incubating-java.tar|zip contains war
> files. We decided to NOT distribute the war file. According that, we
> need also to update the related documentation (/README and website)
>
> Also, minor thing, I think the name should be
> shindig-1.1-beta-1-incubating (in lower case)
>
> Cheers,
>
> Vincent
>
> [1]
> https://repository.apache.org/content/repositories/shindig-staging-023/org/apache/shindig/shindig/1.1-BETA1-incubating/
>
> 2009/7/24, Paul Lindner <li...@inuus.com>:
> > Thanks Vincent, last time we had a delay in IPMC approval, hopefully this
> > won't occur this time.
> > So 48 hours to go. Can I see some +1s?
> >
> > If you
> > feel you can't approve this I would love to know what your approval
> criteria is.
> >
> > In my opinion this BETA is probably a month or two overdue and I'd
> > like to see us move
> > towards a release early / release often mindset.
> >
> > On Fri, Jul 24, 2009 at 4:14 AM, Vincent Siveton <vsiveton@apache.org
> >wrote:
> >
> >
> > > Hi,
> > >
> > > 2009/7/23 Paul Lindner <li...@inuus.com>:
> > > >> One thing that just occured to me, incubation releases have to be
> > > approved
> > > >> by the PMC (voting round on the general-incubation@apache list),
> I'm
> > > not
> > > >> sure if that also counts for beta releases, but if it does then
> weekly
> > > >> releases probably isn't the best idea.
> > > >>
> > > >
> > > > Hrm, might be an issue. Vincent, wdyt?
> > >
> > > All incubation releases *should* be approved by IPMC, alpha beta or
> > > whatever.
> > >
> > > Cheers,
> > >
> > > Vincent
> > >
> >
>
Re: [VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Posted by Vincent Siveton <vs...@apache.org>.
-1 due to major issues:
* a lot of CHECKSUM FAILED when using this repo.
* In [1], shindig-1.1-BETA1-incubating-java.tar|zip contains war
files. We decided to NOT distribute the war file. According that, we
need also to update the related documentation (/README and website)
Also, minor thing, I think the name should be
shindig-1.1-beta-1-incubating (in lower case)
Cheers,
Vincent
[1] https://repository.apache.org/content/repositories/shindig-staging-023/org/apache/shindig/shindig/1.1-BETA1-incubating/
2009/7/24, Paul Lindner <li...@inuus.com>:
> Thanks Vincent, last time we had a delay in IPMC approval, hopefully this
> won't occur this time.
> So 48 hours to go. Can I see some +1s?
>
> If you
> feel you can't approve this I would love to know what your approval criteria is.
>
> In my opinion this BETA is probably a month or two overdue and I'd
> like to see us move
> towards a release early / release often mindset.
>
> On Fri, Jul 24, 2009 at 4:14 AM, Vincent Siveton <vs...@apache.org>wrote:
>
>
> > Hi,
> >
> > 2009/7/23 Paul Lindner <li...@inuus.com>:
> > >> One thing that just occured to me, incubation releases have to be
> > approved
> > >> by the PMC (voting round on the general-incubation@apache list), I'm
> > not
> > >> sure if that also counts for beta releases, but if it does then weekly
> > >> releases probably isn't the best idea.
> > >>
> > >
> > > Hrm, might be an issue. Vincent, wdyt?
> >
> > All incubation releases *should* be approved by IPMC, alpha beta or
> > whatever.
> >
> > Cheers,
> >
> > Vincent
> >
>
Re: [VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Posted by Ian Boston <ie...@tfd.co.uk>.
+0.5
Some issues.
If you ask to release [1] the IPMC will find [2] containing jars
without the correct legal files, ask to release [3] instead.
assuming that, IIRC you will need to also notify the IPMC of the tag
which I assume is [4].
Looking at the source tar ball.
---------------------------------------------------------------
( and this might be me, but in the past openssl dgst -md5 <file>
resulted in a checksum of the file ?)
x43543-2:test ieb$ openssl dgst shindig-1.1-BETA1-incubating-
source.tar.gz.md5
MD5(shindig-1.1-BETA1-incubating-source.tar.gz.md5)=
576a39dc14bc6238146b319f8796440f
x43543-2:test ieb$ more shindig-1.1-BETA1-incubating-source.tar.gz.md5
ea7c3ae06e6d33c3a21999bb53a29660
x43543-2:test ieb$ openssl dgst -sha1 shindig-1.1-BETA1-incubating-
source.tar.gz
SHA1(shindig-1.1-BETA1-incubating-source.tar.gz)=
f45d09d1205466bf14c36e3bd5b25a5379ac4db2
x43543-2:test ieb$ more shindig-1.1-BETA1-incubating-source.tar.gz.sha1
3511990fb0cfde514bc22793bf83967f17b44517
Checksums dont *appear* to match?
-----------------------------------------------------------------
having unpacked the source tarball and pulled the tag there is one
file in the tag not in the source tarball. Looks like it should not be
in the tag.
x43543-2:test ieb$ diff -r shindig-project-1.1-BETA1-incubating
shindig-1.1-BETA1-incubating-source | grep -v .svn
Only in shindig-project-1.1-BETA1-incubating/features/bin: js.jar
x43543-2:test ieb$
----------------------------------------------------------------
Signing Key,
The PGP key does not appear to have a chain of trust. IIRC your key
needs to be signed by someone at Apache who's key is in the web of
trust (?)
----------------------------------------------------------------
I don't know if the IPMC would pick up on these things or if they are
problems, but last time sebb found these and more. I haven't looked
into the legal files yet.
IMHO, the release as it stands would not get an IPMC +1, so its
probably better to fix the problems before putting it in front of them.
Ian
[1] https://repository.apache.org/content/repositories/shindig-staging-023/
[2] https://repository.apache.org/content/repositories/shindig-staging-023/org/apache/shindig/shindig-server/1.1-BETA1-incubating/shindig-server-1.1-BETA1-incubating.war
[3] https://repository.apache.org/content/repositories/shindig-staging-023/org/apache/shindig/shindig/1.1-BETA1-incubating/
[4] http://svn.apache.org/repos/asf/incubator/shindig/tags/shindig-project-1.1-BETA1-incubating/
On 24 Jul 2009, at 22:09, Kevin Brown wrote:
> +1, ditto Adam's comments
>
> On Fri, Jul 24, 2009 at 8:32 AM, Adam Winer <aw...@google.com> wrote:
>
>> I'm +1 on releasing at this time. IMO, 1.1RC1 needs some very
>> explicit release criteria, but earlier betas merely require "we fixed
>> a lot of bugs and the product is not known to be broken".
>>
>> On Fri, Jul 24, 2009 at 6:49 AM, Paul Lindner<li...@inuus.com>
>> wrote:
>>> Thanks Vincent, last time we had a delay in IPMC approval,
>>> hopefully this
>>> won't occur this time.
>>> So 48 hours to go. Can I see some +1s?
>>>
>>> If you
>>> feel you can't approve this I would love to know what your approval
>> criteria is.
>>>
>>> In my opinion this BETA is probably a month or two overdue and I'd
>>> like to see us move
>>> towards a release early / release often mindset.
>>>
>>> On Fri, Jul 24, 2009 at 4:14 AM, Vincent Siveton
>>> <vsiveton@apache.org
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> 2009/7/23 Paul Lindner <li...@inuus.com>:
>>>>>> One thing that just occured to me, incubation releases have to be
>>>> approved
>>>>>> by the PMC (voting round on the general-incubation@apache
>>>>>> list), I'm
>>>> not
>>>>>> sure if that also counts for beta releases, but if it does then
>> weekly
>>>>>> releases probably isn't the best idea.
>>>>>>
>>>>>
>>>>> Hrm, might be an issue. Vincent, wdyt?
>>>>
>>>> All incubation releases *should* be approved by IPMC, alpha beta or
>>>> whatever.
>>>>
>>>> Cheers,
>>>>
>>>> Vincent
>>>>
>>>
>>
Re: [VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Posted by Kevin Brown <et...@google.com>.
+1, ditto Adam's comments
On Fri, Jul 24, 2009 at 8:32 AM, Adam Winer <aw...@google.com> wrote:
> I'm +1 on releasing at this time. IMO, 1.1RC1 needs some very
> explicit release criteria, but earlier betas merely require "we fixed
> a lot of bugs and the product is not known to be broken".
>
> On Fri, Jul 24, 2009 at 6:49 AM, Paul Lindner<li...@inuus.com> wrote:
> > Thanks Vincent, last time we had a delay in IPMC approval, hopefully this
> > won't occur this time.
> > So 48 hours to go. Can I see some +1s?
> >
> > If you
> > feel you can't approve this I would love to know what your approval
> criteria is.
> >
> > In my opinion this BETA is probably a month or two overdue and I'd
> > like to see us move
> > towards a release early / release often mindset.
> >
> > On Fri, Jul 24, 2009 at 4:14 AM, Vincent Siveton <vsiveton@apache.org
> >wrote:
> >
> >> Hi,
> >>
> >> 2009/7/23 Paul Lindner <li...@inuus.com>:
> >> >> One thing that just occured to me, incubation releases have to be
> >> approved
> >> >> by the PMC (voting round on the general-incubation@apache list), I'm
> >> not
> >> >> sure if that also counts for beta releases, but if it does then
> weekly
> >> >> releases probably isn't the best idea.
> >> >>
> >> >
> >> > Hrm, might be an issue. Vincent, wdyt?
> >>
> >> All incubation releases *should* be approved by IPMC, alpha beta or
> >> whatever.
> >>
> >> Cheers,
> >>
> >> Vincent
> >>
> >
>
Re: [VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Posted by Adam Winer <aw...@google.com>.
I'm +1 on releasing at this time. IMO, 1.1RC1 needs some very
explicit release criteria, but earlier betas merely require "we fixed
a lot of bugs and the product is not known to be broken".
On Fri, Jul 24, 2009 at 6:49 AM, Paul Lindner<li...@inuus.com> wrote:
> Thanks Vincent, last time we had a delay in IPMC approval, hopefully this
> won't occur this time.
> So 48 hours to go. Can I see some +1s?
>
> If you
> feel you can't approve this I would love to know what your approval criteria is.
>
> In my opinion this BETA is probably a month or two overdue and I'd
> like to see us move
> towards a release early / release often mindset.
>
> On Fri, Jul 24, 2009 at 4:14 AM, Vincent Siveton <vs...@apache.org>wrote:
>
>> Hi,
>>
>> 2009/7/23 Paul Lindner <li...@inuus.com>:
>> >> One thing that just occured to me, incubation releases have to be
>> approved
>> >> by the PMC (voting round on the general-incubation@apache list), I'm
>> not
>> >> sure if that also counts for beta releases, but if it does then weekly
>> >> releases probably isn't the best idea.
>> >>
>> >
>> > Hrm, might be an issue. Vincent, wdyt?
>>
>> All incubation releases *should* be approved by IPMC, alpha beta or
>> whatever.
>>
>> Cheers,
>>
>> Vincent
>>
>
Re: [VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Posted by Upayavira <uv...@odoko.co.uk>.
On Fri, 2009-07-24 at 06:49 -0700, Paul Lindner wrote:
> Thanks Vincent, last time we had a delay in IPMC approval, hopefully this
> won't occur this time.
> So 48 hours to go. Can I see some +1s?
Last time, we saw hassle with getting our original release checked out.
Future releases would hopefully be easier.
Ideally, after a few releases, we can get this done quickly. It may be
able to run the PPMC and the incubator PMC votes to run concurrently,
which would take us down to a 72hr period from vote start to conclusion.
Upayavira
> If you
> feel you can't approve this I would love to know what your approval criteria is.
>
> In my opinion this BETA is probably a month or two overdue and I'd
> like to see us move
> towards a release early / release often mindset.
>
> On Fri, Jul 24, 2009 at 4:14 AM, Vincent Siveton <vs...@apache.org>wrote:
>
> > Hi,
> >
> > 2009/7/23 Paul Lindner <li...@inuus.com>:
> > >> One thing that just occured to me, incubation releases have to be
> > approved
> > >> by the PMC (voting round on the general-incubation@apache list), I'm
> > not
> > >> sure if that also counts for beta releases, but if it does then weekly
> > >> releases probably isn't the best idea.
> > >>
> > >
> > > Hrm, might be an issue. Vincent, wdyt?
> >
> > All incubation releases *should* be approved by IPMC, alpha beta or
> > whatever.
> >
> > Cheers,
> >
> > Vincent
> >
Re: [VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Posted by Paul Lindner <li...@inuus.com>.
Thanks Vincent, last time we had a delay in IPMC approval, hopefully this
won't occur this time.
So 48 hours to go. Can I see some +1s?
If you
feel you can't approve this I would love to know what your approval criteria is.
In my opinion this BETA is probably a month or two overdue and I'd
like to see us move
towards a release early / release often mindset.
On Fri, Jul 24, 2009 at 4:14 AM, Vincent Siveton <vs...@apache.org>wrote:
> Hi,
>
> 2009/7/23 Paul Lindner <li...@inuus.com>:
> >> One thing that just occured to me, incubation releases have to be
> approved
> >> by the PMC (voting round on the general-incubation@apache list), I'm
> not
> >> sure if that also counts for beta releases, but if it does then weekly
> >> releases probably isn't the best idea.
> >>
> >
> > Hrm, might be an issue. Vincent, wdyt?
>
> All incubation releases *should* be approved by IPMC, alpha beta or
> whatever.
>
> Cheers,
>
> Vincent
>
Re: [VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Posted by Vincent Siveton <vs...@apache.org>.
Hi,
2009/7/23 Paul Lindner <li...@inuus.com>:
>> One thing that just occured to me, incubation releases have to be approved
>> by the PMC (voting round on the general-incubation@apache list), I'm not
>> sure if that also counts for beta releases, but if it does then weekly
>> releases probably isn't the best idea.
>>
>
> Hrm, might be an issue. Vincent, wdyt?
All incubation releases *should* be approved by IPMC, alpha beta or whatever.
Cheers,
Vincent
Re: [VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Posted by Paul Lindner <li...@inuus.com>.
On Thu, Jul 23, 2009 at 2:18 PM, Chris Chabot <ch...@google.com> wrote:
> On Thu, Jul 23, 2009 at 10:19 PM, Paul Lindner <li...@inuus.com> wrote:
>
> > In my opinion BETAs are BETAs, no expectation of complete
> > functionality. Release Candidates are expected to be feature complete.
> > Note
> > that there are plenty of Java features for 0.9 that are not there as
> well.
> > Let's schedule your fixes for the BETA2.
> >
> > In fact, I'm happy to do weekly beta releases if it moves the process
> > forward.
> >
>
> One thing that just occured to me, incubation releases have to be approved
> by the PMC (voting round on the general-incubation@apache list), I'm not
> sure if that also counts for beta releases, but if it does then weekly
> releases probably isn't the best idea.
>
Hrm, might be an issue. Vincent, wdyt?
>
> As I mentioned I'm getting pretty close to being feature complete, and
> branching / release management / etc won't give me more hours in the day to
> work on that, so from my perspective a beta 1 release before then doesn't
> help very much; If however you feel it would add something to getting java
> release ready, I'm not against that, just that I won't be able to spend to
> much time on making sure the php beta1 release actually works (other then
> the testing & feedback that's already happening on the trunk for php
> shindig).
>
There will always be another patch to apply, another fix to add. Right now
we owe it to the people that consume our code a reasonable roadmap and some
stability. Beta releases can have known issues, which your above would be
one of them.
We've got to move away from having implementers pulling snapshots from
trunk. There are 263 issues closed out. That's huge.
>
> Did anyone ever make a good overview of what needs to happen for Java
> shindig before it's 1.1 (final) ready? If we can get an impression of what
> kind of time that would take, it would be much easier to judge what should
> happen when and if decoupling (which I'm really not looking forward too
> since that opens a big can of worms) is a good idea or if we're not so far
> apart in our cycle as some might think.
>
The 0.9 issues are all in Jira. We should triage and insure that the
required issues for 0.9 are all tagged for 1.1-RC1, which should be our
first feature complete release.
Re: [VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Posted by Chris Chabot <ch...@google.com>.
On Thu, Jul 23, 2009 at 10:19 PM, Paul Lindner <li...@inuus.com> wrote:
> In my opinion BETAs are BETAs, no expectation of complete
> functionality. Release Candidates are expected to be feature complete.
> Note
> that there are plenty of Java features for 0.9 that are not there as well.
> Let's schedule your fixes for the BETA2.
>
> In fact, I'm happy to do weekly beta releases if it moves the process
> forward.
>
One thing that just occured to me, incubation releases have to be approved
by the PMC (voting round on the general-incubation@apache list), I'm not
sure if that also counts for beta releases, but if it does then weekly
releases probably isn't the best idea.
As I mentioned I'm getting pretty close to being feature complete, and
branching / release management / etc won't give me more hours in the day to
work on that, so from my perspective a beta 1 release before then doesn't
help very much; If however you feel it would add something to getting java
release ready, I'm not against that, just that I won't be able to spend to
much time on making sure the php beta1 release actually works (other then
the testing & feedback that's already happening on the trunk for php
shindig).
Did anyone ever make a good overview of what needs to happen for Java
shindig before it's 1.1 (final) ready? If we can get an impression of what
kind of time that would take, it would be much easier to judge what should
happen when and if decoupling (which I'm really not looking forward too
since that opens a big can of worms) is a good idea or if we're not so far
apart in our cycle as some might think.
Re: [VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Posted by Paul Lindner <li...@inuus.com>.
In my opinion BETAs are BETAs, no expectation of complete
functionality. Release Candidates are expected to be feature complete. Note
that there are plenty of Java features for 0.9 that are not there as well.
Let's schedule your fixes for the BETA2.
In fact, I'm happy to do weekly beta releases if it moves the process
forward.
On Thu, Jul 23, 2009 at 12:55 PM, Lane LiaBraaten <ll...@google.com>wrote:
> This sounds like a good argument for decoupling the Java and PHP releases.
>
> -Lane
>
> On Thu, Jul 23, 2009 at 12:28 PM, Chris Chabot <ch...@google.com> wrote:
>
> > Hey Paul,
> >
> > I'm still working on finishing two of large features (most noticeably
> OSML
> > osx: tags and Template Libraries), both are being actively worked on and
> > most of the todo list I mentioned last time has been resolved (along with
> > ~12 issues that weren't listed), I would really feel more comfortable
> > having
> > a feature-complete first beta release out so that the beta cycle can be
> > used
> > for bug fixing, and not for finishing the actual implementation.
> >
> > On the other hand I wouldn't want to block the cycle either if it is
> super
> > duper important for you to get a beta release out *now*, but if you could
> > wait until the end of next week before we branch for release, that would
> > help me a lot.
> >
> > So my vote is a 0
> >
> > On Thu, Jul 23, 2009 at 8:03 PM, Paul Lindner <li...@inuus.com> wrote:
> >
> > > Hi,
> > >
> > > We solved 263 issues:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310741&styleName=Html&version=12313552
> > >
> > > There are still a couple of issues left in
> > > JIRA:
> > >
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310741&status=1
> > >
> > >
> > > (Note remaining 1.1-BETA1 issues will be moved to 1.1-BETA2 upon
> > approval)
> > >
> > > Staging repo:
> > >
> https://repository.apache.org/content/repositories/shindig-staging-023/
> > >
> > > Web site:http://incubator.apache.org/shindig/
> > >
> > > Vote open for 72 hours.
> > >
> > > [ ] +1
> > > [ ] +0
> > > [ ] -1
> > >
> > >
> >
>
Re: [VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Posted by Lane LiaBraaten <ll...@google.com>.
This sounds like a good argument for decoupling the Java and PHP releases.
-Lane
On Thu, Jul 23, 2009 at 12:28 PM, Chris Chabot <ch...@google.com> wrote:
> Hey Paul,
>
> I'm still working on finishing two of large features (most noticeably OSML
> osx: tags and Template Libraries), both are being actively worked on and
> most of the todo list I mentioned last time has been resolved (along with
> ~12 issues that weren't listed), I would really feel more comfortable
> having
> a feature-complete first beta release out so that the beta cycle can be
> used
> for bug fixing, and not for finishing the actual implementation.
>
> On the other hand I wouldn't want to block the cycle either if it is super
> duper important for you to get a beta release out *now*, but if you could
> wait until the end of next week before we branch for release, that would
> help me a lot.
>
> So my vote is a 0
>
> On Thu, Jul 23, 2009 at 8:03 PM, Paul Lindner <li...@inuus.com> wrote:
>
> > Hi,
> >
> > We solved 263 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310741&styleName=Html&version=12313552
> >
> > There are still a couple of issues left in
> > JIRA:
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310741&status=1
> >
> >
> > (Note remaining 1.1-BETA1 issues will be moved to 1.1-BETA2 upon
> approval)
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/shindig-staging-023/
> >
> > Web site:http://incubator.apache.org/shindig/
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> >
>
Re: [VOTE] Release Apache Incubator Shindig version 1.1-BETA1
Posted by Chris Chabot <ch...@google.com>.
Hey Paul,
I'm still working on finishing two of large features (most noticeably OSML
osx: tags and Template Libraries), both are being actively worked on and
most of the todo list I mentioned last time has been resolved (along with
~12 issues that weren't listed), I would really feel more comfortable having
a feature-complete first beta release out so that the beta cycle can be used
for bug fixing, and not for finishing the actual implementation.
On the other hand I wouldn't want to block the cycle either if it is super
duper important for you to get a beta release out *now*, but if you could
wait until the end of next week before we branch for release, that would
help me a lot.
So my vote is a 0
On Thu, Jul 23, 2009 at 8:03 PM, Paul Lindner <li...@inuus.com> wrote:
> Hi,
>
> We solved 263 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310741&styleName=Html&version=12313552
>
> There are still a couple of issues left in
> JIRA:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310741&status=1
>
>
> (Note remaining 1.1-BETA1 issues will be moved to 1.1-BETA2 upon approval)
>
> Staging repo:
> https://repository.apache.org/content/repositories/shindig-staging-023/
>
> Web site:http://incubator.apache.org/shindig/
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>