On 28 June 2013 09:00, Robbie Gemmell <[email protected]> wrote:
> On 26 June 2013 16:13, Robbie Gemmell <[email protected]> wrote: > > > Keith spotted earlier that any links to the wiki export no longer seem to > > work, with links 404'ing other than the index page itself at > > https://cwiki.apache.org/qpid/ > > > > The original email below would seem related, as the autoexport plugin > used > > to do the export is no longer going to be supported following a > Confluence > > upgrade and will not be coming back. Following some of the links in the > > mail (e.g on the JIRA) suggest there are some manual alternatives such > as a > > maven based build project to do the equivalent of the export plugin. > > > > All that said, going to our actual Confluence instance just now says that > > the major upgrade has actually *not* occurred yet as indicated in the > mail, > > with a banner instead saying "Upgraded to 3.5.17. Upgrade to 5.1 > delayed." > > Either way, our html export seems to be screwed currently. > > > > What would we like to do about this? > > > > Anyone else (thanks Steve!) care to chime in on this? It would be good to > get something agreed that we can then start working towards to help clear > up the current mess. > > > > > > I have said previously in the website threads that I would actually quite > > like to get rid of the HTML export and move any remaining user > > documentation of real use to the main documentation/website, deleting > most > > of what is on the wiki, and subsequently using the actual wiki (rather > than > > an export) for only the things that it is best suited to going forward. > > > > As such, I think my choice would just be to get > > https://cwiki.apache.org/qpid/ redirected to the actual Confluence wiki > > at https://cwiki.apache.org/confluence/display/qpid just now and then > > start down the path of clearing most of the existing rubbish out. > Thanks guys for moving this forward. I'm enthusiastic about improving our documentation. My view on what-should-go-where is: *- Main website:* - High-level user documentation with a marketing slant - High-level information for Qpid developers - Links to everything else - "Books", provided in HTML and PDF format: complete user-facing reference material. Generated from Docbook or Markdown content that is versioned as part of the main codebase. *- Wiki:* - Authoritative developer documentation, e.g. coding standards, high level design principles. - Transient developer information, e.g. design proposals. Should be obviously distinct from the aforementioned authoritative stuff. Most designs can be agreed on the mailing list and in Jiras, but I prefer using the wiki for occasional larger proposals so that I can include rich content such as diagrams. - NOT user documentation, even though it's quick and easy to add. I've never understood the benefit of exporting the wiki to HTML, and to be honest I don't understand exactly how the export works. If the motivation is to make our users perceive wiki content as a conventional website then this justification disappears when we take the pledge to keep user documentation out of Confluence. > > > Robbie > > > > ---------- Forwarded message ---------- > > From: gmcdonald <[email protected]> > > Date: 18 June 2013 12:56 > > Subject: IMPORTANT: Major Confluence Upgrade Coming Soon. Please review > > test instance now. > > To: [email protected], [email protected] > > > > > > [PMCs please forward to your dev list ; Incubator Mentors please forward > to > > your Podling dev list. > > Note that this message may be received twice as it will also go to > > committers@ list.] > > > > > > Hi All, > > > > If your project has a Confluence Wiki then this is an IMPORTANT > > announcement > > for you and your project. Please read this email carefully. > > > > NOTICE: The ASF Confluence instance is planned to be upgraded this > Saturday > > 22nd June 2013. Judging by the time taken to upgrade the test instance, > > please expect the service to be in a down or read only state for the > entire > > day. > > > > This email is to let you know that a test upgrade has already occurred > and > > is live for you to play with now. This gives us all an opportunity to > test > > for stability as well as any upgrade/plugin issues that might have > happened > > along the way. > > > > Our current confluence wiki is at version 3.4.9 from way back in February > > 2011 and Atlassian have released a further 45 updates along the way, > > including another 2 major versions. > > The test instance has been upgraded several times along the way, with > > database surgery, operating system and server changes along the way. > > > > There have been casualties. Most notably is the Autoexport Plugin has had > > to > > be disabled permanently as during extensive testing, this plugin stopped > > working on version 4.3. Templates and Macros are also affected with major > > changes from wiki markup to xhtml amongst other things. Some plugins > > survived with upgrades all the way whilst some have been > > decommissioned/replaced or have changed to 'paid for' versions that we > need > > to sort out licensing for. Nothing major that I can tell, but that's > where > > you lot come in with your testing of your own spaces. > > > > Please familiarise yourself with what's new in Confluence 5.1 at > > > https://confluence.atlassian.com/display/DOC/Confluence+5.1+Release+Notes > > and also take a good look around our upgraded test instance. Do not worry > > about mucking anything up on the test instance as that is what it is > there > > for. Any changes/additions made will be lost on Saturday when a new > > migration will take place. The current confluence version will remain > > online > > in a read only state until the new version is completed. > > > > A jira ticket has been raised at > > https://issues.apache.org/jira/browse/INFRA-6406 where projects can add > > comments on any issues they are having with the test instance as compared > > to > > their old site. Just problems only please, do not turn it into a how to > use > > confluence 5 thread. In addition, if there are any features that you > > currently use that do not work in the test instance, please replicate the > > feature in the current production TEST space so that I can test them all > in > > the one place along the way. (Ask if you need create page permissions to > > cwiki.apache.org/confluence/display/TEST ) > > > > It may be possible in the future to replace Autoexport by playing around > > with the API to export the pages but this is not a priority, nor is it > > supported. We warned projects long ago that the Autoexport Tool would be > > incompatible with future Confluence versions and that time has now come. > > > > Ok so, please test and report to the Jira Issue mentioned anything amiss > > with your space. Go to https://cwiki2.apache.org/confluence and have a > > play > > around. You have 3 DAYS to report anything you find. > > > > Thanks > > > > Gavin (ASF Infra) > > > > > > > > >
